What's actually changed: building software with AI when it feels overwhelming
23 attendees from 8 groups hosting
Details
What's actually changed: building software with AI when everyone feels overwhelmed
AI is changing faster than almost anyone can track. Not the people using AI every day, not the people paying for it, not the people deciding whether to use it at all, and not the people building the architectures. The volume of news is unmanageable, partly because a lot of it is now being written by the AIs themselves. Half of this talk is about what deserves your attention. The other half is Bob.
Software engineering used to have a guy named Bob. Bob's job was to look at what you were doing, ask why, and tell you to slow the hell down. Bob read the spec before the code, the code before the commit, the commit before the deploy. Bob was annoying. Bob was correct. I miss Bob.
Vibe coding does not have Bob.
I tried to get him back into the room by creating four tools. Duplo is Bob creating the spec from whatever reference material you have. McLoop is Bob running the build while you sleep, with discipline about what gets committed. Orchestra is grumpy Bob fighting LLM slop by putting multiple models in specific roles, because any single LLM can fail spectacularly and Bob does not like that. Vroom is Bob reading what shipped and asking what should have been done differently.
Short live demo of Bob. Where Bob came from. Where Bob breaks. Bring questions, and bring the kind of skepticism the field used to have before it fired Bob.


