korrents
Nelson Elhage

What Nelson Elhage thinks about software quality

@nelson-elhage · 19 positions · On ppll ↗

Software engineer who writes the blog Made of Bugs about performance, debugging and understanding computer systems. Previously worked at Anthropic on interpretability, at Stripe on Sorbet, and at Ksplice.

Nelson Elhage did not write this page.

We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.

2 dated positions, 2025 to 2026, in their own words. Our reading of what Nelson Elhage has said — not written or endorsed by them.

2 positions so far — this page is not yet offered to search engines.

  1. writing programs in this style makes it much easier to write correct and safe concurrent code

    ↗From error-handling to structured concurrencyblog.nelhage.com 2nd of 2 in this piece

  2. 12 months earlier
  3. However, with so many different software projects out there, each moving so rapidly and depending on and being used by so many other projects, it becomes practically-inevitable that some regressions "like that one" happen, almost constantly.

    ↗Performance of the Python 3.14 tail-call interpreterblog.nelhage.com 2nd of 3 in this piece