Everything I learned about concurrency and reliability I learned at the Waffle House
đź”— a linked post to
youtu.be »
—
originally shared here on
A friend recommended this video to me while I was out with Covid a few months back and I just got to watch it.
Now I get to recommend it to you!
If you are a nerd for process, you will love this. Just one small fact to entice you to watch this: did you know Waffle House employs their own meteorological staff?
Most companies don’t get it. Most people don’t get it. To them, problems are a sign of failure. They think that the default state is perfection. They believe that if we just worked hard enough — planned hard enough then there wouldn’t be any problems. The only reason we fall from that perfect state is that someone, somewhere screwed up.
But that’s not reality. The default state for our reality is chaos. It is ruin. It is entropy and erosion and human nature. We build things to make a better world, and yeah, part of that is people failing. People fail all the time. That sucks, but you’re not going to change it. So you might as well do a good job living with it.
This is really what we all need to cope with. The times we live in are chaotic, filled with uncertainty, fear, and a sense of impending doom. So much so that even our children are suffering at historic rates.
But as I deal with my own struggles to make sense of things, I continue to fall back on accepting that we've always lived in a world that is rife with turmoil. All we can do is go along for the ride, appreciate what we have, and be grateful for those who we can lean on to help navigate it together.
đź”— a linked post to
moretothat.com »
—
originally shared here on
Anytime you try to control or reverse disorder, you introduce tension. This is true on a sociological level, where any attempt to organize people inevitably leads to rebellion. But more relevantly, it’s also true at the individual level, and is particularly poignant in our desire to control time.
This same thought (trying to control disorder) has been going through my head a lot lately, but I’ve only ever applied it to political discourse or workplace drama. I’ve never once thought to apply it to time.
Burnout is often associated with working too much, but the real reason it happens is because you have defined yourself by what you produce. It’s not just the exertion of energy spent during your working hours, but the exertion of thought spent during the time you’re not working. It lives in the moment where you’re physically with your family, but mentally planning out what you need to do next. Or when you keep looking at the time when you should just be enjoying lunch.
Again, as a recovering entrepreneur, I’m only now becoming aware of how awful my compulsive need to check in on my team had become.
I’m striving in 2023 to better utilize time as an ally, and to build back the healthy habits that I’ve surrendered in the name of maximum productivity and profitability. Those habits include things I actually used to do (5K run or 2.5mi walk every morning, journaling) and things I keep telling myself I want to do (yoga, biking, playing with my kids, dating my wife).
One extremely common phenomenon when discussing issues surrounding blockchain-based technologies is that proponents will often switch between discussing the theoretical implementations of these ecosystems and discussing the ecosystems we have today as it suits their argument.
For example, if you bring up the question of whether the major centralized exchanges could each decide based on instructions from an oppressive government to freeze exchange of tokens belonging to a dissident, you’ll be told that that’s no problem in their theoretical world where a Bitcoin is a Bitcoin and if an exchange won’t accept yours, you can easily find an exchange that will.
But then if you bring up the question of how these ecosystems will handle someone who decides they want to make an NFT out of child sexual abuse material, they will usually point to solutions predicated on the enormously centralized nature of NFT marketplaces that we’ve ended up with in practice: delist the NFT from OpenSea or a handful of other exchanges so that the vast majority of people trading NFTs never see it, and maybe send a takedown request if there is a centralized service like AWS that is hosting the actual file.
I wanted to link to this article because I find it applicable on two levels.
First, if you take it at face value, there are a ton of great points (like the one I quoted above) which illustrate the often hypocritical problems associated with a blockchain-powered world.
But what’s more interesting to me is how many of these arguments can apply to any of our broader systems at large. Politics, capitalism, globalism, religion… the list could go on and on, and all entries on that list could be tried against the spirit of all the arguments in this post.
What I like about blockchain? It’s the next evolution of building a just and equitable system for all. It’s just funny to me how we can analyze that system in real time to point out the ancient flaws that were unintentionally baked into it.
You can scoff at linking the rise of Trump to income inequality alone. And you should. These things are always layers of complexity deep. But it’s a key part of what drives people to think, “I don’t live in the world I expected. That pisses me off. So screw this. And screw you! I’m going to fight for something totally different, because this – whatever it is – isn’t working.”
Take that mentality and raise it to the power of Facebook, Instagram, and cable news – where people are more keenly aware of how other people live than ever before.
A compelling theory of how we got to where we are (economically-speaking), and a great reminder that no matter how much we think we’re better than [insert subgroup here], we’re all basically the same.
The best science writers learn that science is not a procession of facts and breakthroughs, but an erratic stumble toward gradually diminished uncertainty; that peer-reviewed publications are not gospel and even prestigious journals are polluted by nonsense; and that the scientific endeavor is plagued by all-too-human failings such as hubris.
All of these qualities should have been invaluable in the midst of a global calamity, where clear explanations were needed, misinformation was rife, and answers were in high demand but short supply.
Much of what this article discusses is how I’ve felt over the last couple of years.
If you like living at the intersection of reality, people, and discovery, then you’ll also like this piece.
đź”— a linked post to
cardus.ca »
—
originally shared here on
Ursula Franklin wrote, “Central to any new technology is the concept of justice.”
We can commit to developing the technologies and building out new infrastructural systems that are flexible and sustainable, but we have the same urgency and unparalleled opportunity to transform our ultrastructure, the social systems that surround and shape them.
Every human being has a body with similar needs, embedded in the material world at a specific place in the landscape. This requires a different relationship with each other, one in which we acknowledge and act on how we are connected to each other through our bodies in the landscapes where we find ourselves.
We need to have a conception of infrastructural citizenship that includes a responsibility to look after each other, in perpetuity.
And with that, we can begin to transform our technological systems into systems of compassion, care, and resource-sharing at all scales, from the individual level, through the level of cities and nations, all the way up to the global.
đź”— a linked post to
paulgraham.com »
—
originally shared here on
For example, I had avoided working for big companies. But if you'd asked why, I'd have said it was because they were bogus, or bureaucratic. Or just yuck. I never understood how much of my dislike of big companies was due to the fact that you win by hacking bad tests.
I've always considered curiosity to be my biggest asset, using it to really understand how things worked.
I never put two-and-two together, though, that the reason I wanted to understand how things worked was to "win" at it.
Paul Graham's theory here is just one revelation after another for me.
Here is another juicy nugget:
Instead of looking at all the different kinds of work people do and thinking of them vaguely as more or less appealing, you can now ask a very specific question that will sort them in an interesting way: to what extent do you win at this kind of work by hacking bad tests?
If you engage engineers, you don’t know what you are going to get. You may be unlucky and get nothing. Or their solution may be so outlandish that it is hard to compare with other competing solutions. On average, though, what you get will be more valuable than the gains produced by some tedious restructuring enshrined in a fat PowerPoint deck.