Software History

The code behind the biggest crowdfunded project ever was supposed to eliminate the need to trust humans. But humans are tough to take out of the equation.

When a developer 'unpublished' his work from the NPM JavaScript package registry, it broke dependencies for many other projects -- and highlighted the fragility of the open source ecosystem

Things to commit just before leaving your job · GitHub

Xerox scanners/photocopiers randomly alter numbers in scanned documents Please see the “condensed time line” section (the next one) for a time line of how the Xerox saga unfolded. It for example depicts that I did not push the thing to the public right away, but gave Xerox a lot of time before I did so.

not to oversimplify: first you have to flatten the rock and put lightning inside it— ben 🚀 cobalt core! (@daisyowl) March 15, 2017

On September 9, 1947, a team of computer scientists reported the world’s first computer bug—a moth trapped in their computer at Harvard University.

I thought you had it.

Funny names for funny functions.

Late last year I released posuto, a package presenting Japanese postal code data in an easy-to-use format. It's based on data released by Japan Post, which is infamous for being widely used but hard to parse.

500'000€ Prize for Compressing Human Knowledge by Marcus Hutter

(Photo Credit: baxiabhishek via flickflu.com) Is anyone else having a slow email problem? Seriously, Rodney? You’re kidding right? No. I sent Bill an email 45 minutes ago and it’s still not there. What’s the deal? Last week I talked about the Message Recall feature as the Ultimate Save Your Job Feature, And Why It Took […]

This crate fn noret() -> ! { loop { } } pub fn test_noret() -> () { noret() } when compiled without optimization (rustc --crate-type rlib --emit asm), produces _ZN4test5noret17hecd4eea31d87a4...

32b for MS-Dos, n/a at The Party 2001

This is the story of the hardest thing I've ever debugged, from Crash Bandicoot 1.