Live data from Hacker News

What Claude Code's Source Revealed About AI Engineering Culture

techtrenches.dev

61–65 of 65 posts

Re: What Claude Code's Source Revealed About AI Engineering Culture

#61
post #6

Obviously they were legit vibing it. AI coding is like having a team of 100 interns. It’s incredibly powerful but you need to keep it under control or you’re gonna have a bad day. Write documentation describing the specs , the APIs, the protocols, and the customer stories. Specify that everything must be divided with clear separations of concerns, interfaces, and state objects. Any single file should have a clearly d…

It depends on the kind of software you are programming. If you are programming regular commercial software (office applications, web apps, games) with customers tolerating occasional bug and lot of pressure deliver fast, you can gain lot from Claude. Facebook motto: Move fast and break things If you are programming software for industrial applications, critical software, most of the time you spend is not on writing s…

Something maybe worth thinking about.

If you are relying on understanding every single line of code, then maybe you should examine your modularity and testing norms. I don’t know about you, but the next day, I can’t realistically claim to actively hold an understanding of every line of code I wrote the day before. But AI can review 10Kloc and hold it in context with flawless retrieval. I cannot do that.

If you have the right structural framework and don’t approach it as a crutch but rather an amplifier, you can actually improve code quality and documentation while multiplying productivity, and you also don’t get cognitive atrophy out of the deal.

Also, previously unrealistic testing jigs are now trivial to implement, so I can test my code way beyond the point where I would have shipped it before.

AI , like people, makes mistakes. But using AI enables you to pivot to building the infrastructure that assures that no mistakes can escape the lab. That becomes your entire focus, instead of being a burdensome and usually neglected operational overhead.

It’s definitely easy, even tempting, to “hold it wrong” though.

Re: What Claude Code's Source Revealed About AI Engineering Culture

#63
the "it worked despite being bad code" argument proves too much. plenty of bad codebases succeeded for reasons unrelated to their quality such as first mover, distribution, pricing. correlation isn't causation, and survivorship bias is real. the 3K-line function didn't make Claude Code win, the model and the timing did.

the more honest version of golly_ned's point upthread is narrower: in the very early days of a new category, shipping beats quality because nothing is proven yet. that's actually true. it's not true as a general principle, and it's definitely not true for the 99% of projects that aren't racing to define a new market.

Re: What Claude Code's Source Revealed About AI Engineering Culture

#65

I came away with a very different conclusion, which is that the fact that such “bad” software can be so resoundingly successful for a business, yet be so odious to experienced human reviewers, means that it was the right engineering choice to go fast, rather than “do things right” by emphasizing code quality. What good would it truly be if a 3K line function is split into 8 modules? It’ll be neater and more comprehen…

I think your "winner takes all, first mover wins" premise is wrong, even if it may be what Anthropic believe. Their mission has certainly shifted from "save the world from AI" to "push AI onto the world ASAP, because we've got an IPO coming up".

In reality the coding market, which is really the biggest success story for frontier AI (because code it is uniquely suited for LLMs and RL) is rapidly headed for, if not already arrived at, commodification, with each release from any of the US big 3 heralded as best yet, and the Chinese models like DeepSeek, Kimi, Qwen, GLM maybe no more than 6 months behind.

As far as code quality and level of bugs, certainly Claude Code has been hugely successful despite that, for two reasons.

1) It's a revolutionary product, and people are willing to accept a high level of bugs because of that.

2) The product is an LLM, itself an inherently flawed and unreliable technology, but one that people have got used to. The fact that the agent/harness, as well as the LLM itself, is unreliable and regresses from release to release doesn't much change the vibe

The quality of code produced by Claude Code, at least the way it has been used to write itself, would be a complete non-starter for any business where reliability is important. Maybe best suited for things like consumer web apps where the cost of product failure, or version regression, is just an annoyed customer rather than a lawsuit.

Post reply on HN