Friday, 27th October 2017
I’ve heard managers and teams mandating 100% code coverage for applications. That’s a really bad idea. The problem is that you get diminishing returns on our tests as the coverage increases much beyond 70% (I made that number up… no science there). Why is that? Well, when you strive for 100% all the time, you find yourself spending time testing things that really don’t need to be tested. Things that really have no logic in them at all (so any bugs could be caught by ESLint and Flow). Maintaining tests like this actually really slow you and your team down.
Implementing Stripe-like Idempotency Keys in Postgres (via) Having clients send “idempotency keys” with API requests in order to be able to safely retry them if something’s goes wrong is a really neat trick for making transactional APIs more robust. Here Brandur Leach talks implementation strategies.
In the Bay Area, we have a collection of fiefdoms. Villages are parading as cities, addressing problems myopically. For example, Brisbane (a city of 5,000 people between San Francisco and SFO) is currently blocking a large housing development for local reasons. It’s NIMBY-ism on a broad scale – a regional tragedy of the commons.
Late night dining near Great American Music Hall
Tommy’s Joynt is a couple of blocks away and is a San Francisco institution—great comfort food, inexpensive, crammed with personality and open late.
[... 40 words]