
I Don't Write Code. I Lead an AI Team That Does.
Let me be honest with you I'm an engineer with over 11 years of experience. I've shipped reservation systems, PWAs, FiveM game servers, and electronic health record apps. I design architecture, define data flows, and make product decisions every day. But I don't write the code myself. My AI team does. This isn't a confession. It's a workflow β and I think it's the future of solo engineering. Meet the team My setup is simple. I use Claude Opus for everything, in two modes: π§ Me β product design, system architecture, UX decisions π Claude Opus (chat) β turns my rough ideas into detailed spec docs and implementation instructions π» Claude Code (Opus) β reads the spec and actually builds it, file by file π Me again β review, test, iterate One model. Two roles. Zero context switching between different AI tools. Why "teammate" β not "tool" Most developers talk about AI like it's a fancy autocomplete. I don't see it that way. I gave my AI a name. I treat its outputs like a colleague's pull req
Continue reading on Dev.to Webdev
Opens in a new tab

