all posts tagged 'digital gardening'

Habit experiment â„–2: Self-directed study


đź”— a linked post to seanvoisen.com » — originally shared here on

By many peoples’ standards, I don’t actually actually own a lot of books. But, of the books I do own, I’ve probably read only about 70% of them. And of that 70%, I can’t even admit to reading each book in its entirety. This is intentional. I like cultivating a “home library,” which I believe must include an inventory of unread books awaiting future serendipitous re-discovery. I’m not alone in this. In Reading Well, Simon Sarris describes a similar personal philosophy:

You should buy books on a whim, whenever possible, enough that you start to forget about them. You shouldn’t know the whole contents of your own shelves. If you create a home library it should act as one: It is there for you to discover and rediscover, to get lost in.

For me, it’s a library, but for music.

I was thinking today about how I feel like I’m in a rut with my music library. I’ve spent an hour or two every day for weeks now cultivating my collection of music that has followed me for decades.

And I’m tired. All that weeding is hard work, even if it’s “just” carefully adding ID3 tags and the highest album art you can possibly find for each piece of music you have.

But the payoff is that I have an amazing garden, a well curated selection of tunes that provide answers to many of the questions I ask that can’t be specifically answered by books.

I also enjoy the Whim concept that Sean describes here. As I’m finding my attention being drawn away from the music (or, if I find my attention is drawn back into the music in a non-harmonious way), I pull it from the garden.

After all: if an album was meant to fit into my life somehow, it’ll find its way back in there.

Continue to the full article


Things I Made Today While (Digital) Gardening and Vibe Coding

originally shared here on

I'm beginning the slow process of turning this blog into a digital garden, and on the whole, I'm working on cleaning up the digital messes that have been accumulating for decades.

Over the past year, I spent time almost every day going through my Plex library and my drives which contain nearly every saved file since I've used a computer and deciding what to do with them.

This process has had many fits and starts, which feels correct. In my day job, I don't get many "fits and starts" because I'm being paid to understand a task and deliver it. Pruning a digital garden gives me a chance to be a rookie again, where I can take steps in a direction and learn from my mistakes.

I figured it might be interesting to the IndieWeb to see some ways I'm pruning and using AI to seriously help me.


Previewing Winamp Skins

I have a handful of .wsz files on my drives, and at first glance, I could not remember what a .wsz file even did.

I asked Claude and it helpfully told me that they were Winamp skin files, which were essentially .zip files with a different extension, so I was able to dig around inside to see what they were.

Winamp skins contained a handful of .bmp files that used image spriting, a technique commonly used by devs to optimize memory usage. It's clever, but clever things are often inscrutable twenty years later.

So at first, I went to Claude and asked it to write me an app that took in a .wsz file and showed me what the overall theme looked like. Honestly? Not completely terrible results here for 3 minutes of vibe coding1:

Janky but passable display of a Winamp skin

It turned out that the themes I had on my machine were already represented in the Winamp Skin Museum, so thank god "Darth Maul vs. Ash Ketchem" is still being appreciated here in 2025.


Tagging moods for my favorite albums

I've been working on a way to display my music library on my site, and the basic layout I've been vibe coding for the past few days is here:

Screenshot of current layout for music library

You can see the live version of it here. It's kinda neat.

But as you can see on the screenshot, I show a list of an album's genres and styles and moods.

I am not extremely picky about these, but many of them are missing from services like MusicBrainz, so I decided to use Claude and ChatGPT to help me fill in the blanks.

I've got another 30 or so to go, but the page looks a lot better with something in there. I think I'll use this layout to help me consolidate or improve the tags later, which I guess makes it a win for having this layout in the first place.

Another improvement I'd like to make to this is being able to browse by mood. I'd love to have an interface where I am prompted about my general feeling at the moment and have it surface albums to complement that vibe.


  1. I define "vibe coding" as using an LLM to write almost all the code for a project with extremely minimal adjustments on my end. Sometimes, I feel like it's wasteful to vibe code "string change"-sized adjustments, so I will often make those changes in a text editor and, if I need to vibe code something larger, I provide the current file in its entirety and say "here is the most recent version of my code, you can forget anything you've written so far" so it can free up that out-of-date info from its context window.