Does that 30% increase include extra review time? I’m finding that my small team is producing a lot more code, but I’m also spending way more time reviewing, correcting stupid LLMisms, and keeping complexity in check. The last point is the one that concerns me the most because I just can’t keep up and complexity is starting to balloon.
Yeah, I’m fighting the same problem. Way too much to review, not enough time to do it, and I feel like Lucy at the chocolate factory trying to stop the ballooning complexity of certain code bases… but it doesn’t seem to matter.
Sure, developers might be 30% more productive… in the sense that they are producing more literal lines of code in a shorter period of time. But… is that good?
I can’t say I’m seeing a net benefit at this point on the small team I lead.
Yes. They are rebalancing to more review/orchestration then writing code. That is measurable in story points over the last 8 months that we have been using AI heavily.
The trick (and I’m not saying I have it solved but I work hard on this with some success) is making sure the AI doesn’t bloat the documentation to the point where it can’t be understood. Unambiguous diagrams and meta languages are easier to understand and validate for correctness by developers and AI alike. The more we rely on the ambiguous natural language to explain everything, the less understandable it is to anyone.
Thanks! That’s really helpful. I’ll have to keep pushing back on the team to make sure they get better at their own review instead of just dumping it all on me. I still think it’s important to have an understanding of the system, and more review will help.
Does that 30% increase include extra review time? I’m finding that my small team is producing a lot more code, but I’m also spending way more time reviewing, correcting stupid LLMisms, and keeping complexity in check. The last point is the one that concerns me the most because I just can’t keep up and complexity is starting to balloon.
Yeah, I’m fighting the same problem. Way too much to review, not enough time to do it, and I feel like Lucy at the chocolate factory trying to stop the ballooning complexity of certain code bases… but it doesn’t seem to matter.
Sure, developers might be 30% more productive… in the sense that they are producing more literal lines of code in a shorter period of time. But… is that good?
I can’t say I’m seeing a net benefit at this point on the small team I lead.
Yes. They are rebalancing to more review/orchestration then writing code. That is measurable in story points over the last 8 months that we have been using AI heavily.
The trick (and I’m not saying I have it solved but I work hard on this with some success) is making sure the AI doesn’t bloat the documentation to the point where it can’t be understood. Unambiguous diagrams and meta languages are easier to understand and validate for correctness by developers and AI alike. The more we rely on the ambiguous natural language to explain everything, the less understandable it is to anyone.
Thanks! That’s really helpful. I’ll have to keep pushing back on the team to make sure they get better at their own review instead of just dumping it all on me. I still think it’s important to have an understanding of the system, and more review will help.