🤖🕋 Full disclosure: I wrote this post with Claude. I wrote it, Claude cleaned it up. I added to it. I iterated and what you’re about to read (I hope) is the result. I want to be clear, because this is not how I usually write on this blog. The choice was deliberate because I needed a post that was at once an experiment and something meaningful (and to be perfectly honest, I didn’t have time to write something this long at this juncture.) It’s an experiment around two ideas: building in public with an open changelog, and what happens to a long post when it moves from Micro.blog to Bluesky.


🖇️🏗️ Building in Plain Sight …

… and the Plumbing Behind It

As I have written before - my 🖇️ philpin.com domain has been firmly planted in the ‘Cobblers Shoes’ category for too long. What we build for others is (if I dare say it myself) is pretty clever stuff - but so busy doing that for others - no time to make it happen here. Nuts right? So a couple of months ago started to plan the porting process and then three weeks ago (ish) went live with a presence that is totally unfinished - but was already a substantial improvement on what was there - and so ‘publish and be damned’ - embracing the concept of ‘building in plain sight’, something that at a philosophical level, I fully agree with. (If a space like this is not forever changing and evolving, then IMHO - the plot has most definitely been lost) To do this - behind the scenes - we (like most developers) log every change to the domain every tweak, fix and rethink. That’s normal. It’s what developers do. BUT The record sits in ‘dev’, where only the people building the thing ever see it.

So we opened it up.

There is now a public 🖇️ change-log. Every (meaningful) entry from dev gets published, numbered and dated, under one name: Building in Plain Sight. ‘25’ explained why. ‘26’ added a live character count to the writing desk, a change you will never see … not going to detail them all here. If you have interest, you can visit the link.

Alongside the numbered entries is a second voice:** Between Commits**. Those are the notes on why something changed, what it was meant to fix and what I got wrong. The commits are what changed. Between Commits is the thinking.

Why bother? Because most organisations show you the finished building and hide the scaffolding. The scaffolding is where you learn something. If I’m going to talk about systems of engagement, I should probably run one. A change-log nobody reads is a system of record. One you can follow, question and argue with is a start on the system of engagement that I have been writing about for a while now.

Now the plumbing, because it’s the interesting bit.

The change-log has its own RSS feed and micro.blog reads that feed fine. It shows up in the timeline, so if you follow me on micro.blog you’re seeing the entries as they land. (They land when I say so - because what arrives needs to be meaningful to people reading - so lets not bother with trivia.

BUT - as of today, they are not imported to my blog - so nothing is syndicated to my other spaces.

I think what happens is that Micro.blog sees a Philpin.com source, and treats it as my own blog and refuses to import it to ‘stop any duplication’. I understand the logic - and can see how to add the feed separately - but still wrestling in my mind as to whether that is what I want.

I like the split. The change-log is for the people who chose to follow along, here, in the place where people actually talk back. It doesn’t need to go out to everyone everywhere. Not every signal needs amplifying. Some just need to be where the right people can hear them. #StillThinking.

The second experiment.

While I’m poking at the pipes, this post is auto-syndicated to a few places - including Bluesky. It’s long on purpose because I want to see what happens when a substantial post moves from one network to another and specifically because @manton has just enabled auto threading on long untitled posts, which is a cool idea - but as we all know (including Manton - judging by his posts and comments) the devil is in the detail … does it come through as a thread, get cut down to a title and a link, or turn into something else? Same words, different place, and probably a different shape when it arrives.

In my mind, this is also connected somehow into @dave Weiner’s Bon Bon - which is totally different - except in my mind - it isn’t.

More to come.