Mid to large size teams can accrue dependencies like a katamari and then they’ll be wondering why their node_modules has become unworkably big. That is only one reason to adopt a quick RFC process for engineering decisions that have the potential to affect a bunch of people.
Reading Shopify’s approach to keeping their merchant’s secure at their humongous scale seems to come down to the radical standardization of everything. People think this is boring (it isn’t) but it has tons of benefits beyond just security.
One good example with an open sourced tool over at Slack of how they’ve implemented their Security Development Lifecycle to enable their developers to move forward confidently.
For most managers these responses should come naturally, but still good to reflect on how to deal positively with employees giving notice.
We do our own flavor of attachment parenting and this is still one of my favorite pieces about motherhood.
The manifesto to choose boring technology in order to be able to solve interesting problems is something to (re-)read regularly until you’ve internalized it.
A nice rundown of Good Strategy/Bad Strategy as recounted by Russell Davies to Anna Schipman.
Cloudflare is setting a high bar for post-mortem writing but if you want to get started with this, the only parts you really need are: What went wrong & What are we doing about it.
For the more abstract work, it makes it a lot easier for other people to ‘read your mind’ and for you to delegate if you share as much context as possible as Anna Shipman describes here.
Something that bears pointing out regularly: “Plus, contrary to popular belief, agile practices were not invented by the Agile movement. They predate it by many decades.”