Live data from Hacker News

A few random notes from Claude coding quite a bit last few weeks

twitter.com

281–290 of 870 posts

Re: A few random notes from Claude coding quite a bit last few weeks

#282

Slopacolypse. I am bracing for 2026 as the year of the slopacolypse across all of github, substack, arxiv, X/instagram, and generally all digital media. Did he coin the term "slopacolypse" ? It's a useful one.

I prefer slopocalypse.

Re: A few random notes from Claude coding quite a bit last few weeks

#283
post #257

> Atrophy. I've already noticed that I am slowly starting to atrophy my ability to write code manually... > Largely due to all the little mostly syntactic details involved in programming, you can review code just fine even if you struggle to write it. Until you struggle to review it as well. Simple exercise to prove it - ask LLM to write a function in familiar programming language, but in the area you didn't invest l…

People would struggle to review code in a completely unfamiliar domain or part of the stack even before LLMs.

That’s why you need to write code to learn it.

No-one has ever learned skill just by reading/observing

Re: A few random notes from Claude coding quite a bit last few weeks

#284

Earlier quoted context omitted.

okay how about the Francis Scott Key Bridge? https://marylandmatters.org/2025/11/17/key-bridge-replacemen...

You will get a different bridge. With very different technology. Same as "I can't repair my grandfather clock cheaply". In general, there are several things that are true for bridges that aren't true for most technology: * Technology has massively improved, but most people are not realizing that. (E.g. the Bay Bridge cost significantly more than the previous version, but that's because we'd like to not fall down agai…

> But sure, the cost of "one bridge, please" has gone up over time.

Even if you adjust for inflation?

Re: A few random notes from Claude coding quite a bit last few weeks

#285
post #86

Earlier quoted context omitted.

But how can you be a responsible builder if you don't have trust in the LLMs doing the "right thing"? Suppose you're the head of a software team where you've picked up the best candidates for a given project, in that scenario I can see how one is able to trust the team members to orchestrate the implementation of your ideas and intentions, with you not being intimately familiar with the details. Can we place the same…

You don't simply put a body in a seat and get software. There are entire systems enabling this trust: college, resume, samples, referral, interviews, tests and CI, monitoring, mentoring, and performance feedback. And accountability can still exist? Is the engineer that created or reviewed a Pull Request using Claude Code less accountable then one that used PICO?

Of course he is - because he invested so much less.

Re: A few random notes from Claude coding quite a bit last few weeks

#286

> Coding workflow. Given the latest lift in LLM coding capability, like many others I rapidly went from about 80% manual+autocomplete coding and 20% agents in November to 80% agent coding and 20% edits+touchups in December Anyone wondering what exactly is he actually building? What? Where? > The mistakes have changed a lot - they are not simple syntax errors anymore, they are subtle conceptual errors that a slightly…

Lots of very scared, angry developers in these comment sections recently...

This is extremely reductive and incredibly dismissive of everything they wrote above.

Re: A few random notes from Claude coding quite a bit last few weeks

#288
post #195

> It's so interesting to watch an agent relentlessly work at something. They never get tired, they never get demoralized, they just keep going and trying things where a person would have given up long ago to fight another day. It's a "feel the AGI" moment to watch it struggle with something for a long time just to come out victorious 30 minutes later. Somewhere, there are GPUs/NPUs running hot. You send all the neces…

This quote stuck out to me as well, for a slightly different reason. The “tenacity” referenced here has been, in my opinion, the key ingredient in the secret sauce of a successful career in tech, at least in these past 20 years. Every industry job has its intricacies, but for every engineer who earned their pay with novel work on a new protocol, framework, or paradigm, there were 10 or more providing value by putting…

There is an old saying back home: an idiot never tires, only sweats.

Claude isn't tenacious. It is an idiot that never stops digging because it lacks the meta cognition to ask 'hey, is there a better way to do this?'. Chain of thought's whole raison d'etre was so the model could get out of the local minima it pushed itself in. The issue is that after a year it still falls into slightly deeper local minima.

This is fine when a human is in the loop. It isn't what you want when you have a thousand idiots each doing a depth first search on what the limit of your credit card is.

Re: A few random notes from Claude coding quite a bit last few weeks

#289
post #272

People who just let the agent code for them, how big of a codebase are you working on? How complex (i.e. is it a codebase that junior programmers could write and maintain)?

rust compiler and redox operating system with modified Qemu for Mac Vulcan metal pipeline ... probably not junior stuff you might think I'm kidding but Search redox on github, you will find that project and the anonymous contributions

I am curious. What do you want us to see in that github repo?

Re: A few random notes from Claude coding quite a bit last few weeks

#290

Earlier quoted context omitted.

What I have enjoyed about programming is being able to get the computer to do exactly what I want. The possibilities are bounded by only what I can conceive in my mind. I feel like with AI that can happen faster.

> get the computer to do exactly what I want. > with AI that can happen faster. well, not exactly that.

For simple things it can. But then for more complex things that's where I step it
Post reply on HN