Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
11–19 of 19 posts
Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#12Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#13Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#14Also funny to hear reactions when I'm grepping code for a function in front of someone and I hear "wow you look for code I would just ask Gemini" topkek
Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#15Here are some real examples from our projects in 2025 at SIROC (for context: we are a 18 people venture studio; 140+ projects completed): * A task estimated at 4 hours → solved with one well specified prompt * A 20 hour engineering effort → executed in about 3 hours * A 3 month project → delivered in 1 month These are clearly best case scenarios. They are not the norm, yet. But they demonstrate what is possible. We h…
Right now, Claude is getting trained by hundreds of thousands of programmers showing it how to ask the right architecture + PM questions.
They're just patterns, like anything else in our industry, and most of them are pretty standard patterns.
Like when I think back on 20 years of software architecture and BA work, I've done the same thing over and over. I must have implemented 4 PO systems, 3 different custom chat systems, SMS systems for reminders, monthly summary emails, etc.
Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#16I was on a greenfield project late last year with a team that was very enthusiastic about coding agents. I would personally call it a failure, and the project is quietly being wound down after only a few months. It went in a few stages: At first, it proceeded very quickly. Using agents, the team were able to generate a lot of code very fast, and so they were checking off requirements at an amazing pace. PRs were rubb…
Various possibilities I suppose - I could just be overly skeptical, or failures might be kept on the down low, or perhaps most likely: many companies haven't actually reached the point where the hidden tech debt of using these things comes full circle.
Having been through it, what's your current impression of the success stories when you come across them?
Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#17I was on a greenfield project late last year with a team that was very enthusiastic about coding agents. I would personally call it a failure, and the project is quietly being wound down after only a few months. It went in a few stages: At first, it proceeded very quickly. Using agents, the team were able to generate a lot of code very fast, and so they were checking off requirements at an amazing pace. PRs were rubb…
I'd expect this kind of outcome to be common for anything complex, but there seem to be more claims of success stories than horror stories. Various possibilities I suppose - I could just be overly skeptical, or failures might be kept on the down low, or perhaps most likely: many companies haven't actually reached the point where the hidden tech debt of using these things comes full circle. Having been through it, wha…
Several different engineering teams from different parts of the company had to come together for this, and the overall architecture was modular, so there was a lot of complexity before we had to start integrating. We have some company-wide standards and conventions, but they don't cover everything. To work on the code, you might need to know module A does something one way and module B does it in a different way because different teams were involved. That was implicit in how human engineers worked on it, and so it wasn't explicitly explained to the coding agents.
The project was in the life sciences space, and the quality of code in the training data has to be worse than something like a B2B SaaS app. A lot of code in the domain is written by scientists, not software engineers, and only needs to work long enough to publish the paper. So any code an LLM writes is going to look like that by default unless an engineer is paying attention.
I don't know that either of those would be insurmountable if the company were willing to burn more tokens, but I'd guess it's an order of magnitude more than we spent already.
There are politics as well. There have been other changes in the company, and it seems like the current leadership wants to free up resources to work on completely different things, so there's no will to throw more tokens at untangling the mess.
I don't disbelieve the success stories, but I think most of them are either at the level of following already successful patterns instead of doing much novel, or from companies with much bigger budgets for inference. If Anthropic burns a bunch of money to make a C compiler, they can make it back from increased investor hype, but most companies are not in that position.
Re: Ask HN: Has your whole engineering team gone big into AI coding? How's it going?
#18We (12+ people on the team) see more LOC and faster first drafts, but also more review work. PRs look done early, but often hide shallow thinking or edge cases. Velocity goes up on paper. Review fatigue goes up too.
The best teams treat AI like a junior dev with infinite energy. Great for boilerplate and refactors, but you still need ownership. Otherwise you just ship bugs faster, which is not great honestly.
Wdyt?