or subscribe with
Join 15,000+ readers for one email each week.
Digests » 320
Some tools have an opinion about how you should do your job. We're pretty sure you're the expert. With Airtable, you can coordinate and customize every aspect of your internal apps in minutes, not days. Flexible bug tracking, on-duty schedules, team standups, and so much more. Try Airtable today!
this week's favorite
The challenge: in the fewest resources possible, render meaningful text.
The title for this blog post is a direct reference to Latency Numbers Every Programmer Should Know. There are several versions of those numbers available now, and I could not find the original author with certainty. Some people attribute the original numbers to Jeff Dean.
When I catch a bug before release I’m usually glad, because I’ve narrowly averted ruining someone’s experience or eating their data. Today I found a bug that I wish I hadn’t caught, a bug that I wish I’d released into the wild to witness in its full glory. I found this bug in my digital card game Ring of Worlds, and I’ll tell you its story.
Sometimes you just want to know how fast you code can go, without benchmarking it. Sometimes you have benchmarked it and want to know how close you are to the maximum speed. Often you just need to know what the current limiting factor is, to guide your optimization decisions.
This is a cynical, clinical collection of things I learnt in 30 years working with software development. Again, some things are really cynical, others are long observations on different jobs.