Saw a posting this past week on SSD drive failures. They're blaming a lot of it on 'over-logging' -- too much writing trivial, unnecessary data to logs. I imagine it gets worse when realtime data like OpenTelemetry get involved.
Until I saw that, never thought there was such a thing as 'too much logging.' Wonder if there are any ways around it, other than putting logs on spinny disks.
I mainly use it to create boilerplate (like adding a new REST API endpoint), or where I'm experimenting in a standalone project and am not sure how to do something (odd WebGL shaders), or when creating basic unit tests.
But letting it write, or rewrite existing code is very risky. It confidently makes mistakes, and rewrites entire sections of working code, which then breaks. It often goes into a "doom loop" making the same mistakes over and over. And if you tell it something it did was wrong and it should revert, it may not go back to exactly where you were. That's where frequently snapshotting your working code into git is essential, and being able to reset multiple files back to a known state will save your butt.
Just yesterday, I had an idea for a WebGL experiment. Told it to add a panel to an existing testing app I run locally. It did and after a few iterations, got it working. But three other panels stopped working, because it decided to completely change some unrelated upstream declarations. Took 2x time to put everything back to where it was.
Another thing to consider is that every X units of time, you'll want to go back and hand edit the generated material to clean up sloppy code. For example, inefficient data structures, duplicate functions in separate sections, unnecessarily verbose and obvious comments, etc. Also, better if using mature tech (with lots of training examples) vs. a new library or language.
If just starting out, I would not trust AI or vibe coding. Build things by hand and learn the fundamentals. There are no shortcuts. These things may look like super tools, but they give you a false sense of confidence. Get the slightest bit complex, and they fall apart and you will not know why.
Mainly using Cursor. Better results with Claude vs other LLMs, but still not perfect. Paid versions of both. Have also tried Cline with local codegen through Llama and Qwen. Not as good. Claude Code looks decent, but the open-ended cost is too scary for indie devs, unless you work for a company with deep pockets.
Have used Jekyll, Hugo, and Docusaurus to generate static sites, and Wordpress and Ghost for blogs.
A few things to think about:
Where do you plan to host and how much is the monthly budget?
How much traffic do you expect to get?
Will the content be static or updated often (i.e. landing page site vs. blog).
Will more than one person be updating the site?
How technical is the person/people updating the site? Are they OK with using terminal and command-lines, or GUI and point and click.
Will there be 'member-only' features, i.e. things that require users creating an account and logging in?
Will you need to offer a way for people to get in touch? Like, contact pages, email, etc.
Will there be a need for public to post and answer questions (i.e. a forum).
Will you need future support for things like newsletters, shopping carts, etc.
If one-person, technical, static, I'd go with Jekyll and Github pages, or Jekyll/Hugo/Docusaurus on Cloudflare pages. They all have templates. But you need to know how to setup github repos and tools. Cost is $0 to operate, other than annual fee for custom DNS domain name.
If more than one person, non-technical, or dynamic, then hosted Wordpress or Ghost. Budget for DNS name and ~20-50 dollars or euros/month (plus or minus, depending on features and traffic). There are free versions of these, but they slap ads all over them.
You can self-host all these, but it's much easier to have someone else deal with traffic spikes.
If you need community forums or a way for users to communicate with each other, then none of the above.
You can search around for "Bluetooth speaker call recorder." They pair with any device over Bluetooth and act as both passthru as well as recorder. There also used to be ones that worked as wired headsets. No apps needed.
However, be aware you need to be in a location that allows two-party consent-free recording.
The hardest part about getting Linux installed on a Lenovo was getting rid of Windows and its death-grip on the bootloader and the TPM.
Also, a few things, like drivers for keyboard backlight and fingerprint scanner never got working. If you just want to experiment and play, could always try Linux under VMWare Workstation (free for personal use) or boot off a thumbdrive.
It actually is pretty incredible. You get paid to draw boxes with icons, and arrows connecting them.