Vibe coding.
Spec engineering.
Agentic workflows.
Loop engineering.
Graphs.
The names keep changing because the models keep changing.
Practices have a half-life. Architecture shouldn't.
Paul Stack
@stack72
Infra Coder with a militant interest in DevOps and Systems Thinking. Speaks with a funny accent. **Evangelist of Life**. DAF
- The conversations I've been having with engineering leaders keep coming back to the same three objections to AI * Output * Cost * Risk I don't think the problem is the objections. I think it's how we're thinking about them. New post:
- The @NatWest_Help experience with mortgage management is absolutely horrendus - it almost makes me want tomswitch away from them for making things this hard. Zero thought given to an experience
- Every engineer has copy-pasted from Stack Overflow, pulled in NPM packages they never audited, shipped codegen they never read. Nobody called it slop. Then an agent wrote the code. The standard didn't change. The author did.
- Every previous platform shift (Cloud, IaC, Containers...) , teams moved in the same direction at different speeds. With AI, they're moving in opposite directions. I wrote about why I think engineering is starting to split.
