This is such a weak take to read while I have Claude Code running in the background creating a new database migration for a feature we're building
The key difference is that I can context switch. Once the AI has context and is doing its thing, I can move on to another task that's not working in the same area or project. I can post on HN. I can catch up on my Slack inbounds, or my email.
Having two tasks running at once nets a small but nice improvement in velocity. Having any tasks running while I'm doing other things effectively doubles my output.
The one I use creates the migrations, locally, for free and deterministically in about 30 seconds.
But you pay a subscription to run a stack of software in anothers people computer.
btw wtf is raw postgres?
Since you asked, the level I've chosen for this project is Go and PostgreSQL via pq. There's a single level of indirection to wrap the database access in case we need to switch from Postgres for any reason, but otherwise the app interfaces directly with the database. Migrations are simple SQL files that are run as necessary as the server starts up.
This will all run on a dedicated server that is already doing other stuff. That's the full "stack" as it were.
I think a lot of people are massively underestimating how much knowledge and skill is needed in software engineering beyond typing code into a text editor.
If your field of software engineering is so simple that you can survive on code snippets stolen from other people, great. Please do not generalize that.
I think even if we ever reach actual AGI (in the far far future), we'll still want low level meatbags around to blame :-P