Big Steinway from first row
Haydn, Zappa, Wolpe, Oswald, Medtner, Rachmaninoff
Even though I know to expect this, there’s always a
Marc-André Hamelin moment that catches me out. Years ago, for instance, a pedaled downward gliss with every note enunciated, waves stacking so precisely as to sound electronic. Tonight’s moment was in the Etude-Tableau.
Donkey face upright
Donkey face on my shoulder
We were not formally introduced, but my style of scratching passed muster. Being assigned the task of carrying the weight of a donkey’s head for a few minutes is a privilege.
snac is Unixy enough for me to enjoy my occasional dealings with my self-hosted instance. Not skaware, but not a big pile of stuff either.
Wooden bench facing birds, trees, partly frozen river, bridge
Today’s walk.
Why yes, those hostnames *are* products from the Precious Roy Shopping Network, thank you so much for noticing my naming scheme!
Last time I had a NAS it was “bottomless-pool” — perfect, no notes, would love to reuse it — but this 2006 Mac Pro has had its name for 20 years.
Debian 13 etc
Obligatory fastfetch
Please reboot the system, they said
Live-upgraded MacPro1,1 NAS to OMV 8. Reboot failed. Of course I forgot something about 32-bit UEFI grub2.
Booted 8’s ISO without any special grub flags. (On this box, whoa.) Easy repair.
These were my final big questions. I now trust this system with my data. Blog post soon.
fastfetch output
Today’s #pkgsrc hacking:
1. Get fastfetch and all of its dependencies building on Mac OS 10.9 #MavericksForever
2. Include pkgsrc in the package report
It’s hard to fix something because it’s easy to break something else?
That’s your clue: refactor first.
(Special case of the general KFB wisdom “First make the change easy, then make the easy change.”)
#Refactoring #ExtremeProgramming #XPLives
Mac boot picker shows NetBSD logo and text label
fastfetch output
Macmini6,2 #netbsd
Periodic reminder: if you’re intrigued by a job posting touting #ExtremeProgramming, maybe it’s what it claims to be. I hope so. But maybe not.
Hit up your network before applying. If you’re reading this, I’m in your network.
Periodic reminder: if you’re intrigued by a job posting touting #ExtremeProgramming, maybe it’s what it claims to be. I hope so. But maybe not.
Hit up your network before applying. If you’re reading this, I’m in your network.
If #EngineeringLeadership doesn’t believe neurospicy folks can strengthen a team, they’re simply wrong. Maybe they’ll learn.
But if a supposed #ExtremeProgramming expert doesn’t grok this, such remarkably deep failure of understanding indicates ignorance AND profound obstinacy.
Turns out it doesn’t matter how wide-eyed and well-intentioned your imaginings are if your boss is determined to not appreciate you.
If you don’t know how to care for people and don’t care to learn, by definition — no matter how convincingly you write, speak, and code — you are not an #ExtremeProgramming expert. And when you take a power position and try to enact XP among humans, we can see you’re a charlatan.
If you don’t know how to care for people and don’t care to learn, by definition — no matter how convincingly you write, speak, and code — you are not an #ExtremeProgramming expert. And when you take a power position and try to enact XP among humans, we can see you’re a charlatan.
2018 Mac mini was already being weird. Then macOS Tahoe dropped support. Usually I'd want NetBSD. But the only option was Linux, and it's pretty darn okay.
Here's my setup: schmonz.com/2025/11/12/s...
(Writing... muscles... loosening.)
#macos #linux #netbsd
Got some slack time? Pick a risk to reduce.
Got no slack time? Defer something, then pick a cost to reduce.
#ContinuousImprovement
#SenderRewritingScheme with #notqmail via #pkgsrc:
echo srs.dom.ain > control/srs_domain
echo "$SECRET" > control/srs_secrets
echo srs.dom.ain >> control/rcpthosts
echo srs.dom.ain:srs >> control/virtualdomains
echo "| srsfilter" > alias/.qmail-srs-default
+ MX for srs.dom.ain
#qmail lacks #TLS. #notqmail doesn't include it either (yet!). But if you install from #pkgsrc…
# chown qmaild:nofiles control/servercert.pem
# chmod 640 control/servercert.pem
# ln -s control/servercert.pem control/clientcert.pem
# update_tmprsadh
# /etc/rc.d/qmail restart
🔐
For our next trick with #notqmail from #pkgsrc:
Want to SMTP-reject SPF failures when the source domain specifies explicit-fail?
1. Add SPP_SPF_RESULT_FAIL="E550 spf_smtp_msg" to
control/tcprules/smtp
2. Run "/etc/rc.d/qmailsmtpd cdb"
3. There is no 3rd thing, is that clear?
Another neat trick with #notqmail from #pkgsrc:
The default SMTP configuration rejects nonexistent recipients.
(qmail famously accepts all recipients for its domains even when those recipients don't exist, and then has to queue totally avoidable bounce messages. But you won't.)
Another #notqmail from #pkgsrc trick:
To enable #greylisting, simply uncomment "greylisting-spp-wrapper" in control/smtpplugins. That’s it.
(Add any exempt recipient addresses to control/greylist/exemptrcpts, or entire recipient domains to control/greylist/exemptrcpthosts.)
# mkdir -p control/domainkeys/dom.ain # chown -R qmailr control/domainkeys # cd control/domainkeys/dom.ain # openssl genrsa -out default 1024 # chmod 640 default # openssl rsa -in default \ -pubout -out default.pub
Running #notqmail via qmail-run from #pkgsrc? Cool. Add #DKIM signing like so, then publish a TXT record with your `default` policy. Done!
Most practical experts don’t write a book. Distinct tasks, incentives, skills.
For the same reasons, some published authors are better at describing than at enacting.
Maybe an author really knows, in context, under stress, how to *do* the thing. Maybe not.
#ExtremeProgramming
Unfortunately, even if the person following these steps loves #ExtremeProgramming (and is widely held to be expert in it), they’re no less destructive.
Unfortunately, even if the person following these steps loves #ExtremeProgramming (and is widely held to be expert in it), they’re no less destructive.
Hate #ExtremeProgramming and want others to hate it?
1. Become Director of Engineering
2. Tell org and stakeholders that XP will fix longstanding problems
3. Regularly interfere with devs’ learning
4. Design projects to delay ROI
5. Find scapegoats
Maybe they’ll blame #XP.
Dahlia
Also: not a success, at least not in his eyes. I've had a much easier time making appreciable progress when working with folks in power positions who don't imagine themselves to be XP experts.
