







Programmers are always talking about broken builds: "The build is broken", "I broke the build" etc. However, the real problem is that the ...
Balancing “If it ain’t broke, don’t fix it” vs. “Release early and often”
Every organization faces a war between two schools of thought, with “If it ain’t broke, don’t fix it” on one side and “release early and often” on the other. This blog post looks for a way for enterprise consumers to embrace fast-paced changes in the software industry.

Architectural mismatch: why reuse is so hard
Why isn't there more progress toward building systems from existing parts? One answer is that the assumptions of the parts about their intended environment are implicit and either don't match the actual environment or conflict with those of other parts. The authors explore these problems in the context of their own experience with a compositional approach.<>
Designing for failure
Nobody starts a free-software project hoping that it will fail, so it is a rare project indeed [...]
Vibe Coding Failures: Documented AI Code Incidents
A curated directory of real-world incidents where AI-generated code failed in production.

How software engineering is changing: a tale of two eras
We invited readers to write about how building software changed, in an essay challenge. Many of you took part, and today we’re sharing the winning piece from a strong set of entries

“We should be more ambitious with the software we build”
One year as an AI Engineer: The 5 biggest misconceptions about LLM reliability I've encountered
535 votes, 59 comments. After spending a year building evaluation frameworks and debugging production LLM systems, I've noticed the same…
‘AI fatigue’ is settling in as companies’ proofs of concept increasingly fail. Here’s how to prevent it | Fortune
Along with the excitement about the possibilities of generative AI is a great deal of pressure for leaders and employees participating in projects.

Code Is Cheap Now. Software Isn’t.
The barrier to entry for building software has collapsed. The barrier to building something that matters hasn’t moved an inch.
Where Did Software Go Wrong? | Jesse Li
Software is broken, but it's not because of NPM, startups, AI, or venture capitalists. A deep dive into how we think about and produce code, and how our software systems reflect the manic state of the modern world.

Mahax on Twitter / X
Head of Claude Code, Boris Cherny:"You're not supposed to write code anymore. You're supposed to build a graph that writes itself."In 30 minutes he breaks down how engineers at Anthropic build graphs that write the code, catch the bugs, and ships.Most engineers build… https://t.co/I3b2Rt2ul3 pic.twitter.com/UCPTCr1Sl7— Mahax (@Mahaximus_) September 7, 2026
Hey! I'm Isaac
I like building tools, breaking workflows, and putting them back together better.

daniel: "I don't think we need 10x developers to build great things. I think we need 10x teams – groups of people who care about the same problem, who iterate together, and who make each other better" 🤍
daniel roe
wrote a few words on why I think @npmx.dev might be going places