You edit it manually.

That's it. There are no shortcuts to good prose, except perhaps paying a ghost writer.

An LLM may be able to synthesise results well each time, but there will be quite a difference between a synopsis written by an LLM and someone whose job it is to write synopses of books.

Huge difference in quality, and considering the clientele, they are willing to pay for that quality.

That is the biggest rock in the bucket. Smaller rocks include social media use, diet, exercise, whether the person is in a toxic home environment, mental health, or has children.

I have ADHD and I often struggle with having the energy to do anything outside of work. So I try to optimise my life to give me the most energy that I can have. I eat really healthy; high protein, high fibre, low saturated fat. I try to keep my social media use low, using ScreenZen. I meditate. I do resistance exercise a few times a week.

But even still, I find that my mind is exhausted part of a way through a workday, usually by 14:00-15:00. Maybe that's because I'm a software engineer.

I don't know how to fix it. But I'd really appreciate an extra day a week off, even at the cost of some remuneration. I love my work, but I don't want it to feel like it's the only thing I have going.

There's no way to defend against it. You can just copy and paste text from an LLM into the reply box.

Technology is neither good nor bag; nor is it neutral. If you can't think of any reasons people may be critical of AI, given the amount of layoffs, then you're not very imaginative or informed.

I'm only 5 years into this career, and I'm going to work manually and absorb as much knowledge as possible while I'm still able to do it. Yes, that means manually doing shit-kicker work. If AI does get so good that I need to use it, as you say, then I'll be running it locally on a version I can master and build tooling for.

They are overoptimising for the simplest part of writing the application; the beginning. They've half-implemented an actual database, with none of the safety features. There are a lot of potential headaches that this article has avoided talking about; perhaps because they haven't experienced them yet.

See: https://danluu.com/file-consistency/

What happens when you need to start expanding the scope of this feature? Joining users on profiles, or users on orgs?

Ask yourself: how many shops have seriously written an application backed by files and stuck with it over the long-run? The answer is likely very few. Therefore, this is likely doubling up the work required.

There is a reason people reach for a database first. I'd strongly encourage anyone to avoid doing stuff like this.