An introduction on how to measure and improve your engineering organization’s performance using delivery metrics.
Something to remember when embarking on a journey to improve large and complex systems of humans and technology: small changes can make big a difference and afterwards nobody will really remember how bad things were.
A nice interview with Gergely Orosz about building engineering teams.
Looking at some Discord first organizations this describes how they could play out and how much potential is there if you want to put some effort in it.
“The technology is not the hard part. It’s already invented, but we have to pay ourselves to install it fast. So, again, that’s an economic question, and it doesn’t work in capitalism. We have the means right now to arrange for everybody alive today to have adequate food, water, shelter, clothing, education, and healthcare, within the biosphere’s carrying capacity.”
A market of some sort may always exist, because we need to trade, but it could be so sharply regulated that it could exist on what economists call the margin, suitable for the toys, but not for the necessities of life, which should all be public utilities and part of a job guarantee and a living wage.
KSR talking about the fight ahead.
Once you’ve worked with post-commit reviews, I promise you will not want to go back to the PR way of working again.
I had some people from the Greens explain to me how the SUV was not so bad after all (as my intuition told me). Turns out my intuition was right.
Most of my discussions with data scientists have revolved around exactly this point (usually to serious pushback): that they need to be end-to-end to deliver value in an organization.
A super thorough and correct guide how to manage senior engineers which is more or less how I would like to be managed.
It looks like Cards Against Humanity is over and I can’t say that I’m sad about that.