Live data from Hacker News

I built a production app in a week by managing a swarm of 20 AI agents

zachwills.net

31–40 of 61 posts

Re: I built a production app in a week by managing a swarm of 20 AI agents

#31
post #14

There's a lot of disagreement about what "agent" means. As far as I can tell it is the same as AI chat, but with a really long response time.

I have not seen discrepancy in what "agent" means in the AI space. At the top is generally a chat model. Underneath are tools for (i.e.) working with files, MCP servers for more complex actions, and even more models for specialized tasks. It takes longer because there is more going on under the hood

Re: I built a production app in a week by managing a swarm of 20 AI agents

#33
post #17

Earlier quoted context omitted.

Ask yourself what happens when Claude releases Claude Code 2.0, which just uses AI to self-manage the swarms from a simpler prompt.

You would do the same thing with less work. Progress! If only, though; I find it easy to stump even the best model on brownfield code bases.

Yea, generally I think humans just move farther to the right. Higher leverage. Work on the stuff only you can work on.

Re: I built a production app in a week by managing a swarm of 20 AI agents

#34

[flagged]

I take a lot of pride in my work -- I am still proud of the post, even if some don't like it. Different flavors exist for a reason. I don't hide the fact that I use Wispr Flow, dictate my thoughts, and let AI clean it up, and edit from there. That is the most efficient way to do what I'm doing and juggle what I'm juggling.

Maybe you should contribute some of your ideas vs. bashing others who do?

Re: I built a production app in a week by managing a swarm of 20 AI agents

#35
post #14

There's a lot of disagreement about what "agent" means. As far as I can tell it is the same as AI chat, but with a really long response time.

I have not seen discrepancy in what "agent" means in the AI space. At the top is generally a chat model. Underneath are tools for (i.e.) working with files, MCP servers for more complex actions, and even more models for specialized tasks. It takes longer because there is more going on under the hood

Yep, agreed with you that agent generally means an LLM with access to tools it knows how to use (like MCPs) that can go relatively far/deep with guidance (minimal or otherwise).

Re: I built a production app in a week by managing a swarm of 20 AI agents

#36

No mention of what was actually built? Also, I have no desire to micromanage a bunch of robots. I rather build things.

There is a similar difference between management track and those that have no interest with humans.

I've primarily stayed working with one, but sometimes two, to first understand how to manage one, more like a pair-programming setup, but also see if they can be used more like a managed developer. They still do too many dumb things to let them loose, I have my doubts this will change without significant change to the underlying models.

Also, you need to spend the time to read what they wrote and check not just for correctness and test passing, but is this even the right approach. They misinterpret the question or task, even when spelled out painful detail. They lose their focus or get caught in loops.They love to write everything from scratch instead of using the helper packages sitting right there. It's like the bell curve flattened out, they are equally impressive as they are astonishingly moronic, context dependent (pun intended)

Re: I built a production app in a week by managing a swarm of 20 AI agents

#37
If anyone has links to maintaining a vibe coded (meaning you trust the LLM to some level as opposed to giving it a thorough review) product over a long period of time I’d love to see that! As is it’s always like this - lines of code, test coverage %, # of commits, etc. Metrics higher ups and others who don’t really know how to measure quality software love to point too. The only metric that’s reliable is the code, but that’s not often shared for projects done this way. And when they are, they don’t live up to the hype.

I’m not claiming vibe coded projects don’t have a place. I’m skeptical that using English prompts can build a maintainable code base as well as using a programming language.

Re: I built a production app in a week by managing a swarm of 20 AI agents

#38

> And, to be clear, when I say production ready I mean it had good test coverage, CI/CD, includes auth, background jobs, and integrates LLMs and other 3rd party APIs. I’d consider it a respectable alpha version of the product. So does any template off GitHub? When you run the Laravel Installer, you got pretty much all of these for free (sans LLM) And within a normal work week, you can have a valid prototype with an a…

You're 100% right; there are ways to move quickly without using AI to write the code. I also agree with you that you need to know what you're doing. If you're a total newbie you likely won't get as far using Laravel or something like that vs. a veteran who's been there & done that before.

> You're 100% right;

This is a serious question, I'm not being snarky - do you run your comments through AI before posting them here?

Re: I built a production app in a week by managing a swarm of 20 AI agents

#39

No mention of what was actually built? Also, I have no desire to micromanage a bunch of robots. I rather build things.

> Also, I have no desire to micromanage a bunch of robots. I rather build things.

I gotta say, nearly every thing I've built both at work and at home ends up being another tool I have to end up micro-managing to some degree or another.

Re: I built a production app in a week by managing a swarm of 20 AI agents

#40

It's funny how things have evolved. The modern tech stack is so inefficient at providing solutions that people grab and hold on to code gen as some kind of magic machine. We have gone from pragmatic, fast and stable foundation systems that could be extended by some small snippets of code (Drupal), RAD systems (Delphi, Visual Basic) where you could drop some components and some lines of code on a form to create functi…

Thanks for sharing your perspective. I don't agree that code generated by AI will be easily distinguishable from code generated by hand; I think it depends on who is authoring. Also, for what it's worth, if it achieves the business goals, is stable and performant, does it matter?

I see where you're coming from. Some code may stick, and some generated code actually looks decent. There is a lot of coffee-fueled code that will never see the light of day again as well. It's just that there has been an inflation in code. Almost like the quantity has a positive quality all on its own, when that should be a negative ("Look at this 50k code app made in 1 day"). I think the next generation of code generators should be penalized for writing verbose code. Hopefully they'll ease the burden of maintaining systems instead of adding to it. My experience is that once a code base gets a certain size, agents start to lose the big picture - and often repeats themselves. Adding similar but not quite the same code. Less code will probably help here too. Still. If it works, it works. It's the next phase after the system's first steps I worry about (extending and maintaining).
Post reply on HN