jfgreen

@jfgreen.bsky.social

He / Him. Trying to convince computers to do useful and interesting things. Making and listening to bleeps, bloops, breaks and bass.

Cancelled Spotify after 14 years and rediscovered my 2005 iPod Classic with Lee "Scratch" Perry tracks streaming never had. Now I'm buying records on Bandcamp with my old subscription money. Music sounds better and I actually own it! // cc @jfgreen.bsky.social www.jimgumbley.com/blog/why-i-l...

Why I Left Spotify in 2025

After fourteen years as a loyal Spotify customer, I finally cancelled my subscription. Here's why the platform's algorithmic direction no longer matches my simple, self-curated listening style.

jimgumbley.com

Shoutout to the Core Audio devs who decided that AudioToolbox should return the error code 'wht?' when encountering an unspecified error. A perfect blend of whimsy and pragmatism that lives on in MacOS to this day.

Screen shot from the site osstatus.com showing information about two MacOS Core Audio error codes kAudioFileStreamError_UnspecifiedError and kAudioFileUnspecifiedError. Mysteriously, neither of these codes have a description, but both of them are encoded by the byte sequence which in ascii spells out 'wht?'

I have printed copies of some of my very first attempts at programming circa 2007ish. We have a direct insight into my thought process as I commented _every single_ line of code. On global variables? “This variable needs to be global because it is very important”.

Swapping gym sets with my wife whilst simultaneously alternating responsibility for toddler entertainment is the kind of physical-mental discombobulation that chess boxing athletes must experience.

Relying on half recalled fragments of a compilers class to write a parser for a markdown-like language has been interesting. The good news: I have finally internalised what “context sensitive grammar” means. The less good news: Markup turns out to be really, truly, painfully context sensitive

Idle thought: it’s drilled into it us that code is read far more than it’s written, but I never see anyone talk about how code is run far more than it’s read. It feels like there’s a blog post there for the taking. Open with that framing and then start talking about things like uv, bun, biome, etc

Love how Tranceparty just straight up reclaimed this piece of abandoned corporate iconography. Look at this happy little guy, skipping merrily here and there as he shares his sweet trumpeting with the world. Really puts you in the mood to dance.

Bild

Delightfully unrepentant behaviour from the British public in the face of being denied footpath access. 1) Golf course erects a misleading sign implying you cant use the public footpath. 2) Sign is drawn over with footpath reference. 3) Sign is repeatedly thrown aside. 4) Golf course relents.

Sign placed in the middle of a footpath. It has a large arrow directing walkers to turn left and text that reads “Please use the permissive path to join up with Duchess Walk that leads to Knole House and crosses the Golf Course in less dangerous areas. Knole Park Golf Club”. Someone has graffitied over the sign with another arrow directing people down the path and added text that reads: Public footpath SU18”Same sign but it has now been extracted from the ground and thrown to one side of the footpath. A new, less intimidating sign placed to one side of the path reads: “Warning. Danger. Golf course ahead. Golfers playing from the left. Please stay on the footpath”

Another incredible moment for Linux Audio. Just discovered that recording via pipewire on my studio PC is introducing a several millisecond delay between left and right channels. Thank you Linux for making sure all my painstakingly recorded vinyl rips are sounding e-x-t-r-a w-i-d-e.

Hello Bluesky As an intro post I thought it would be nice to list some of my interests. In no particular order: Audiodev / Systems programming / Rust Music production / Tape machines / Synthesisers / Gameboys / Chiptune / Breakbeats / Jungle / DnB Nature / Maps / Weird footpaths / Cats