ok so I've had two NUC servers for a bit over 2000 days now, so lets do some calculations vs "just run it in the cloud" it's 2x NUC6i3SYK, with 128 GB crappy SSDs, and 32 GB of RAM. We'll use 1 April 2017 as the start date (based on when amazon said they delivered them to me)

Hardware cost was $1126.82

omg the ducks are very obliging today doubleduck

this new DHH post really underscores how incredibly important it is to powerful people to undermine any sort of analysis that sees problems as systemic it is important enough to DHH that people don't say "hey little things are part of big things" that this whole thing has to happen

to him that is "extremely high-stakes"

(the full text is in world.hey.com/dhh/let-it-all…, search for paragraph starting "So connecting this to")

oh man there’s a drive in clinic of JJ in the area today...should I cancel my upcoming moderna and do that? I don’t really feel like I have a good sense of the “who does it help / who does it harm” so probably should do nothing?

yesterday came across the words for how I feel about most of the hobbies I do - sometimes people ask "what are you going to do with xyz" and like

I'm not going to _do_ anything - the joy is in the learning about things I'm not amassing the pizzaboxes in order to _do_ anything in particular with them, I just want to learn about them

I'm not doing Ham Radio so I can contact anyone in particular or whatever, I just want to learn about it

ownership & responsibility of software has a neat property that makes it similar to the "memory hierarchy": you get higher throughput if you can efficiently manage communications latency if a project / technology / whatever is in a single team's domain, it's like everything fitting in to L1 cache - FAST. AS. HELL.

if your team is super lucky and firing on all cylinders, you can get to the "all in registers" world and it's dopeeeeeeeee

What your "most senior" engineers work on, how well they communicate about it, and what visible expectations there are of them is such a crystal clear window in to your org's values Values aren't made by mission statements - they're written in the sweat and mayhem of what _actually happens_. Trust is built based on proven track records, not leaps of faith.

one reason I've love being an SRE is because you get to talk to lots of people! Listen to their problems *and* the things they're excited about! Help find balance in human problems surfaced as technical ones. I think it's one of the most *socially* focused of tech roles. Historically, that hasn't been the case: the nerds with root access that you phone when things are really crap are:

* grumpy
* condescending
* want you to go away
* think you're messing up their perfect world
* why aren't we using BSD

and that's some BS!