Here’s how a lot of people build software right now: think up a spec, hand it to a fleet of agents, say “build this” and go to bed. In the morning it’s “hey everybody, look what I made.” And it does look great. It looks like MailChimp. But does it actually work? I know the answer firsthand, because every time I use the thing I made, I find something else that needs tweaking.
Businesses used to handle this with a fleet of testers and a tightly scoped MVP. These days features are so easy to add that we just drop them in and end up with a pile of things nobody has tested. We can do better, but only if we keep the mindset that we’re still senior programmers making software.
So this module is about process. We’ll weave in GitHub, build epics and add a flavor of Scrum so there’s a real project record and we know what the agents did. We’re still building Flatbed, and at the end we’ll add acceptance testing that follows our stories like a real user would. If you want to play along, grab the Flatbed app and go all the way back to the beginning, because I’m resetting the instructions and the orchestration right here.
