This is interesting to hear, but I don't understand how this workflow actually works. I don't need 10 parallel agents making 50-100 PRs a week, I need 1 agent that successfully solves the most important problem. I don't understand how you can generate requirements quicky enough to have 10 parallel agents chewing away at meaningful work. I don't understand how you can have any meaningful supervising role over 10 thing…
My initial response to reading this post was "wow, I think I'd rather just write the code". I also remain a bit skeptical because, if all of this really worked (and I mean over a long time and scaling to meet a range of business requirements), even if it's not how I personally want to write code, shouldn't we be seeing a ton of 1 person startups? I see Bay area startups pushing 996 and requiring living in the Bay are…
> shouldn't we be seeing a ton of 1 person startups?
Here's the dirty secret: 1 person AI coding enabled startups don't want their customers to know that they are 1 engineer AI coding startups so they do not expose it or share that info. There is still a lot of negative sentiment associated with this.I know 3 such founders; none would advertise to their customers the extent of their AI usage. There is also a consideration that if they advertise their 1 eng status and success, it might attract other competitors or the customers might think they can do it themselves (maybe possible, but not for 95% of them since some tech know how is still required) or customers would see it as a business risk.
All 3 have blown me away with what they are doing. All 3 have real, paying customers. (They occasionally reach out for some higher order architecture questions)