Writing
📝 You Can't Change Your Boss
📝 First Aid Kits: Bleeding Control & Tourniquets
🔗 Recommendations When Using LLM-backed Generative AI Systems for FOSS Contributions (#)
Several recommendations for LLM usage in the context of open source.
“The long term goal of software freedom is to eliminate the harm of proprietary technology. While we work toward that greater goal, we should seek to mitigate the harms that we cannot immediately eliminate. These recommendations aim to abate the damage of these systems, and also consider how these tools might counter-intuitively help us advance FOSS.”
📝 This isn't a post about eating meat
💡TIL: My Immich Setup
Notes (mostly for myself but maybe useful to others?) on how I set up Immich for storing/archiving photos.
🔗 A beginner's guide to improving your digital security (#)
Absolutely fantastic guide — all the impactful stuff, none of the nonsense.
📝 How I'm voting in the 2026 DSF Board Elections
📝 Working in Between Public and Private
🔗 Writing a risk scenario (#)
A risk scenario is a fictional but plausible event that could harm your organization. Writing one well improves communication with others…
🔗 FACETS - Avalanche.org (#)
“FACETS is an acronym presented by Ian McCammon to describe a set of 6 heuristic traps that were common in his study of recreational accidents.”
🔗 This World of Ours (James Mickens) (#)
I was reminded of this classic paper in the threat modeling literature canon. Hilarious and also insightful — worth a read if you haven’t seen it before.
📝 Two Scenario Threat Modeling
A trap that many people fall into when trying to threat modeling or risk planning is a fear of being incomplete that leads them to not even try. People think, “there are so many possible things that could go wrong, so many potential risks. It’s going to be such a huge effort to enumerate all possible scenarios, and I don’t have time, so I guess I can’t do threat modeling.” That is, threat modeling seems so big, so hairy, that people believe it’s too complex to tackle.
This just isn’t true! Some planning is always better than no planning. In fact, you can get a surprising amount of value out of a very simple and fast technique: imagine a couple of scenarios – just two! – and game out what you could do to mitigate them.
📝 Comfort Scores: A risk mitigation tool for pre-trip briefings
🔗 Using AI to build a tactical shooter (#)
Via RC’s AI article, a fascinating recording of someone programming a game almost entirely by prompting Claude by voice. This feels truly “futuristic” to me. Sure it’s clunky at times, but damn if this isn’t closer to the Star Trek computer than I ever thought I’d see in my lifetime.
🔗 Developing our position on AI - Blog - Recurse Center (#)
Detailed, nuanced, and well-thought-out. Tons of great and insightful quotes from RC alums. And their conclusion is, I think, perfect:
You should use AI-powered tools to complement or increase your agency, not replace it.
📝 What if We Thought About Risk Decisions Differently?
📝 Ultralight Heresies
🔗 Evan Reese - Custom OnShape features (#)
A bunch of really useful custom features for OnShape
💡TIL: 3d printed parts have different strength characteristics than conventionally-manufactured parts
An interesting 3d printing lesson about how the physical characteristics of printed parts differ from other manufacturing:
I needed to replace a rubber hydraulic hose retention strap on my tractor. The part’s $40 + shipping – ludicrous for a 6x2" strip of rubber – so perfect to try to replicate. I have some TPU filament that’s of similar flexibility, let’s go.
For V1, I just replicated the geometry exactly - including, without thinking about it, some little relief holes around the main hose holes: