Quick personal note before I get back to it.

Quick personal note before I get back to it.

I'm ill. Properly ill. Six months of 18 hour days running two jobs in parallel will do that to ya.

But here's what I want to say while I'm lying here in a hospital bed tonight — because the discourse around AI coding is starting to genuinely irritate me really really badly…

AI-assisted development is not easy. It's different. And if you're building something real — not a vibe-coded demo, an actual product — it might be harder.

Think about what "building" actually means:

→ CI/CD pipelines that don't embarrass you
→ pytest suites that catch things before your users do
→ Bare metal server provisioning
→ API design that makes architectural sense, not just "it works"
→ Security that isn't bolted on as an afterthought
→ A web server and backend that hold together under load
→ Graph databases that model your domain correctly
→ Then testing and debugging after every single PR

I aint even mentioned upfront ideation (mine started in 2018 BTW), and the stuff you will need to learn to create and push code (vibe or not) properly. And then subsequently push that into an actually delivery architecture that can be passed as a stable production system.

And you're doing all of this while prompting, reviewing, correcting, re-prompting, and catching the confident mistakes an LLM makes at 2am when you're already running on fumes.

There will be different kinds of AI developers. Some will build toys. Some will build products.

The ones building products know exactly what I'm talking about.

Anyone who thinks shipping something real is easy — with or without AI — hasn't done it.

Rest. Then back to it. I was just not eating enougth greens, fuk1n clearly

Peace out peeps 🤟

scottg