🔖 Engineering Manager
A ton of links on Engineering Management
A ton of links on Engineering Management
Description of simulating a CPU in code in order to actually understand one, albeit a fairly simple one. A modern CPU? Or a system on a chip? Can't even imagine the complexity.
So I suppose someone should simulate one in order to understand it :-)
Book reviews of Ursula Le Guin's "The Disposed" and "The Dawn of Everything" by David Graeber and David Wengrow
Memory pressure forced me to clear out (save elsewhere) a bunch of browser tabs today, and while doing so I accidentally unpinned and closed belong.io, Andy Baio's (@andybaio@xoxo.zone) months-gone link aggregator. Elon Musk is unforgivable for so so many things, but belong.io used to get me through my commute every single day. I miss it.
I'd been keeping it pinned, in the same that I still have reminders to clean the cage/hutch of pets gone for a decade; my own little GNU clack to keep the memories alive.
A really nice example of an About Page and some other slash pages for a personal site
I found useful as a primer on CRDT in general
High level views on how owning your own data works across multiple devices.
An examination of the idea of owning and controlling the data produced and used by the software that you use, rather than giving it to cloud services.
Suggestions for common pages you might like to see on a personal website.
Lots of neat little features to make a blog really shine. Some of them are obvious, like RSS feeds. Others are more appropriate to blogs more honed in on longer, focused pieces. Some of them are just QOL.
It's more accurate to call it a bunch of software engineering advice, as most of it is about engineering practices, particularly on large, team-based projects.
An analysis of complex systems, how they can (and do) fail, and how to manage their failure and their operation.
Advice on being braver as a programmer. This is actually good advice for anything where you can't really do any damage be screwing up,
A call to action for (re-)building a web designed for humans, not for capitalism
A look at how (I assume some parts of) Google does design documents for their projects
High level summary of the concepts discussed in Database Internals by Alex Petrov and Designing Data-Intensive Applications by Martin Kleppmann
Tips on communicating progress via updates to people who are interested or need to know
Incomplete walkthrough on building your own database