1/
Implementation used to be the bottleneck. Not anymore.
Over the past few months I built an autonomous software delivery platform. Several enterprise projects now run on it in production.
Here's one ticket's journey 👇
1
30
4/
It's not "developers with AI assistants, but faster". Speed, consistency and output quality are in a different league.
And capacity is a setting. Need more? Move the slider. No hiring, no onboarding, no headaches when it's time to scale down.
1
3
Pushing for better prompts will get you only so far.
Using planning mode also.
Do cross-model verification ditto.
Only using AI agents in real technical excellence workflows might get you to really autonomous automatic programming system.
#GenAI
32
You will not be replaced by AI (yet!) — as long as you still bring real value to the table.
Coding is (almost) solved by AI. But what else do you bring? 👇
1
9
AI is an incredibly powerful multiplier.
But it still needs skilled humans to:
- Define the right problems
- Design robust systems
- Validate quality
- Make smart trade-offs
The winners won’t be the fastest coders. They’ll be the best system thinkers and AI drivers.
1
6
As it was the case with any technological breakthrough. Democratization creates demand.
Karpathy just told us engineering job demand is still rising. Contrary to the narratives. That cheaper engineering creates more demand, not less.
The guy who helped co-found OpenAI.
And today, OpenAI announces they're nearly doubling their org from 4,500 to 8,000.
Coincidence?
9
Programmers have raged against abstractions for 70+ years:
• 1950s: “Compilers can’t beat hand-optimized assembly. Real coders write assembler!”
• 1980s: “OOP?Just C plus overhead & leaky abstractions”
• 2020s: “LLMs hallucinate buggy code & make us obsolete”
Denial again?
1
1
38
We need to understand that no automation needs to be error-free. It is enough to be better than humans… and repeatable.
11
Spoon-feeding Claude every single requirement is getting old fast. Prompts are ephemeral — stuff gets lost, no persistence.
So I switched to user-defined markdown tasks/stories in a specs/ folder. 1/5
1
14
Downside: code is becoming almost impossible to change manually.
The retroactive/fragile test suite (yep, rookie mistake we talked about) makes refactors scary — one tiny tweak breaks tons of tests that weren't even well-written to begin with.
5/6
1
21
Claude can fix them, but relying on it for every edit is annoying as hell.
Next: polish the console UI to make it actually pleasant to use, then do a major architecture overhaul.
Repo still updating live: github.com/bojanspasic/board…
6/6
1
19

