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.

You're losing if you're handing your brain over to LLMs right now, because companies would prefer to hire someone with more up-to-date coding skills, even if they then force them to use LLMs. So the winning move is to resist using LLMs for as long as possible.

Stop fanboying the industry's attempted commodification of your work, and get back to the basics.

But what happens if you need to manually update a record?

I do look a little younger than 32, due to a healthy lifestyle and religious use of sunscreen but I have a beard and moustache. It's a little insane that I was instantly banned with no way to move forward.

https://github.com/js-temporal/temporal-polyfill

Therefore, birthdays are not bound by timezone at all.