The conversation

Lessons learnedExperience excerpt · English

So I agree with you and disagree: I'm turning a corner on these tools, but I absolutely could not …

… So I agree with you and disagree: I'm turning a corner on these tools, but I absolutely could not just let rip and trust it to do anything correctly. Moreover, I could not be less impressed by the MCPs written by people in my company. The bare tool by itself is better, though maybe that says more about my company than the tools.

Original discussionLessons for Agentic Coding: What should we do when code is cheap?237 source comments · at import
2

What was this responding to?

Parent context · original excerpt

SP

A lot of people down on AI in this thread, but I'm watching the industry slip over the line of trust with these latest frontier models. GPT 5.5 is the first model good enough for me to just let rip. Every jira ticket I see now has acceptance criteria, reproduction steps, and detailed information about why the ticket exists. Every commit message now matches the repo style, and has detailed information about what's contained in the commit. Every MR now has detailed information about what's being merged. Every code base in the teams around me now has 70 to 90%+ code coverage. Every line of code now comes with best practices baked in, helpful comments, and optimized hot paths. I regularly ship four features at a time now across multiple projects. The MCP has now automated away all of the drudgery of programming, from summarizing emails, to generating confluence documentation, to generating s…

Full original

Community replies 0

No community replies yet. Add your perspective.

Replies from the source 2

Direct replies available in this import. Original-language excerpts.

AR

> Could I have written it without Claude? Yes, definitely. But I was able to produce the code in a few days while having a fever of 100-102, which I definitely couldn't have done on my own. While I admire your strength in attempting it, this just adds one more brick to the wall of precedents that "what's stopping you from just sending one prompt, it'll just take 30 seconds and you can do it in bed!" You could sum it up into a simple equation as Features Shipped = Features/Hour * Developer Hours Developer hours has remained a constant, and F/H has gone up. I am of the opinion that the ideal is the inverse.

Full original
RE

I think this is the way. Human-machine co-design worked great for me so far. Hell, even the test writing alone is great, because I can have more confidence in my code. And test writing was mostly drudgery. On the other hand, you _must_ have a good mental model of the thing in your head else this will not work. And it's much easier to believe you have it and not really have it if you don't engage with the codebase.

Full original
Continue on Hacker News

Respect different perspectives. Share concrete experiences.

Sign in to post, reply, repost, and quote.