macaw.social
06 Nov 2022This post serves as cross-proof that I’m @arrdem@macaw.social in the fediverse.
This post serves as cross-proof that I’m @arrdem@macaw.social in the fediverse.
Ah dotfiles.
Love ‘em or hate ‘em we’ve got to live with ‘em.
While Rob Pike has words about Unix hidden files, we (almost all) work on computers and with software whose behavior is determined in large part by hidden files in our home directories.
There’s probably a .bashrc
or .zshrc
and a whole .ssh/
and .config/
directories kicking around on your workstation full of stuff that matters a fair bit to your day-to-day and standing up a new work machine is probably a wasted day of trying to remember homebrew incantations and source software.
For the last decade I’ve chased and wrestled with the ideal of “simple” software, but I’ve come to see it as a false summit and want to spend some ink on why in the hope that it can lead to a better understanding of simplicity and more intelligent conversations about complexity.
If you’ve spent any time around a traditional workshop or machine shop, you’ve probably seen signs about how safety is everyone’s responsibility and about keeping the shared space clean. In an environment with sparks, unrated flammables left around are a risk. In an environment with rotating tools like lathes loose clothing that can wrap or snag and pull can lead to injury. Less extreme examples like sweeping up the shop and keeping the fridge clean all fill different parts of the same shared obligation to the other users of a space.
Techdebt tornado, adj.; pejorative
One who successfully delivers changes with limited or counterproductive regard for architecture.
One who produces work, especially feature work, at the cost of existing architecture and without developing a successor architecture.
This blog post is a review and musing on a talk of the same title “The Thirty Million Line Problem” (2015) (~1h lecture + 40m q&a).
Previously, I talked about some limitations of building RPi clusters generally.
A while ago I got it into my head to put a Raspberry Pi cluster together.
I’ve been doing a lot of reflecting lately on the last project I shipped - what went well, and what didn’t. A while back I tweeted out some halfbaked thoughts. One of which was a reflection that while the entire engineering organization beyond my team was using a tremendously powerful toolset, we still got bogged down.