4 Comments
User's avatar
Alessandro Buonpane's avatar

Thank you for this informative article! Could you elaborate on this?

“The right interface between two components is a well-structured data artifact, not a function call. Clean data lets agents compose systems without being told how.”

Daniel Andrade's avatar

Amazing write-up! Love how companies are improving and shifting the way to work with AI

Pawel Jozefiak's avatar

The shift from developer coding time to agent enablement is exactly what happened to me. Spent months writing scripts. Now I spend mornings reviewing what my agent built overnight.

The counterintuitive part: the less I code directly, the more productive the system gets. My time goes into defining better constraints, writing clearer configs, and building verification loops.

The agents-not-engineers framing is right but incomplete. Someone still has to teach the agent what good looks like. That's the new skill - not coding, but curating.

Documented this exact workflow shift: https://thoughts.jock.pl/p/my-ai-agent-works-night-shifts-builds

Matthew Walster's avatar

This has to be one of the most insane posts I've ever read. They are surely being left with incredibly unmaintainable, undebuggable, and untrustworthy code that will be practically impossible to recover from. Surely you can't be serious in promoting this methodology as "best practice"?