• Learnt lots of fascinating things about how servers are catalogued in data centres today.

    I learnt that when racks are advertised as “24U”, for example, that “U” refers to “unit”. Saying a device is a 2U means it takes up two units of vertical space. Something taking up “half a rack” means that it’s half the width of a unit, and there’s space to mount two of them across.

    I also learnt that when numbering rack units, you start from the bottom, give that unit the number 1, and literally/metaphorically go up from there.

    Finally, I learnt that the above is pretty much the only thing that’s standard about cataloguing server locations. There’s no standard for numbering devices going across the rack, and apart from floor numbers, room numbers, and maybe aisle and rack numbers — assigned by the data centre itself — you’re on your own to come up with your own standard for the rest.

    So there’s plenty of opportunities for those keen to set internal standards for the organisations they work in. 😄

  • Got asked to come up with a way of representing some data today. Before diving into a design, I thought of finding out whether a standard existed. I couldn’t find one, and when I asked those in the know, they confirmed that no such standard exists. That’s good news! No chance of an accidental 927.

  • I got spam via Product Hunt today. First time as well. Completely forget I had an account there, until someone thought it would be a good idea to follow me while shilling their AI company.

    Censored screenshot of a follower notification from Product Hunt
    Yeah, ****. You would like me to post an uncensored screenshot of your follow, complete with company name, on my blog. 😎
  • A bit more retro gaming this evening. Tonight, some Paganitzu, Part 1, or “Pagan” as I tended to call it, since that was the command to invoke it on the DOS prompt.

    A screenshot of the Wayback Machine, showing the first level of Panganitzu Pt. 1 running in DosBox running in a browser
  • I don’t use Ghost, but I did sign up for it once, so I’m still getting the newsletters. And the latest one has got some interesting stuff. I’m not planning to employ someone for my “writing business” but I did find the list of recommended links to be pretty good.

  • One thing I’ll miss with hosting my own code is the ability to spin up a Codespace for a repository directly within GitHub. It won’t be difficult to setup a Code Server instance myself — I can do it in Pikapods — but keeping that separation between repositories was a nice feature. Ah well.

  • On the Easy Pit To Fall Into

    From Matt Bircher’s latest post on Birchtree: One of the hard parts about sharing one’s opinions online like I do is that it’s very easy to fall into the trap of mostly complaining about things. This is something I also think about. While I haven’t done anything scientific to know what my ratio of posting about things I like vs. things I don’t, I feel like I’m getting the balance better. Continue reading →

  • 🔗 Marquee Element Tester

    Test your browsers compatability of the Marquee element. No spoilers about whether it worked in mine. 😀

    Via Scripting Notes.

  • I knew it was a mistake to choose to eat breakfast outside. 🌧️

  • I’ve got a large writing task to do at work, so I’m trying out iA Writer. And I probably shouldn’t have because I know how expensive it is, and yet I think I’m growing to like it. It’s actually a really nice Markdown editor.

    At first my developer brain resisted, saying “Ah, pish posh! Just use any old text editor you already have.” And if it was just a readme file or something, I’d probably turn to either Nova or GoLand1 to do this. But I already know that this task is going to involve a fair bit of writing, and I think the editor iA Writer uses would works better for this. It’s just feels better designed for prose: slightly larger font (although the default was way too large, and I had to reduce it), better line spacing, and handling line wraps in a nicer way than code editors.

    I’ve got other writing tasks I need to do, so maybe it’s worth it in the end.


    1. Obsidian would’ve been another option, but I’m hoping to keep this writing in a separate Git repository, away from my standard notes file. ↩︎

  • Vivaldi decided it had enough this week and crashed, about 15 minutes ago. Not yet, Vivaldi! We still have a few more hours left in the day.

    Vivaldi crashing also reminds me of working with someone back when Firefox used to restore your tabs only when it crashed. If you were to restart it gracefully, it’ll always begin with a clean slate: one tab, showing your configured home screen. So what this guy did was force quit Firefox at the end of every work day, before he shut his laptop down, so he can restore his tabs the next day. We were saying to him that when he leaves for another job, he should quit Firefox gracefully, thereby putting to rest all the tabs he had opened. I can’t remember if he actually did that when he left.

  • Oof! This week has been something else. 😮‍💨 One more day to go.

  • Bit of a breakthrough with a project I’m on at work today. Amazing how quickly you can go from having absolutely nothing working, to having it work for the first time, to everyone expecting it to work reliably from that point on. It took probably an hour for us to experience all three phases.

  • Backpacker on the tram. 🐶

    A black schnauzer travelling in a backpack on a crowded tram. A Myki reader is to the right of the frame.
  • Dealing with a reporting task at the moment, and all the shortcuts I’ve made over the course of working on this system are coming back to bite me. But it’s easy to say that I wouldn’t have made them that if I were to do it all again. If faced with the same level of knowledge and time pressure as I had back then, I probably would take those shortcuts again. I guess the only think I can hope for is to recognise future shortcuts as what they are, and try to avoid them if I can.

  • A Tour Of My New Self-Hosted Code Setup

    While working on the draft for this post, a quote from Seinfield came to mind which I thought was a quite apt description of this little project: Breaking up is knocking over a Coke machine. You can’t do it in one push. You gotta rock it back and forth a few times and then it goes over. I’ve been thinking about “breaking up” with Github on and off for a while now. Continue reading →

  • Work offered us a very… American style lunch today. First time I had bacon with my pancakes. Honestly, not as bad as I was expecting.

    A plate with pancakes, bacon, whipped cream, drissled with maple syrup, with a side of Ceaser salad and egg. Wooden knife and fork on the right.
  • 👨‍💻 New post on Moan-routine over at Coding Bits: Zerolog’s API Mistake

  • Zerolog’s API Mistake

    I’ll be honest, I was expecting a lot more moan-routine posts than I’ve written to date. Guess I’ve been in a positive mood. That is, until I started using Zerolog again this morning. Zerolog is a Go logging package that we use at work. It’s pretty successful, and all in all a good logger. But they made a fundamental mistake in their API which trips me up from time to time: they’re not consistent with their return types. Continue reading →

  • Got a long post written that I wanted to publish today. But I need to add the audio narration to it, and my voice is just not working this evening. So I’m going to have to hold it for a bit longer. A shame, but if a day late means a better overall post, it might be worth it in the end.

  • The gym has discovered they have a heater, which is immensely welcomed, because wearing shorts and a T-shirt in weather that’s barely 16°C is not fun (and this is the warmest it’s been in weeks). 🥶

  • 🔗 On the origins of DS_store

    An interesting tale on how .DS_Store — a regular in Git ignore files everywhere — got its name.

    Via @Burk within the Hemispheric Views Discord.

  • Woke up with this tune in my head this morning. Managed to record it before I forgot it, then I added some accompaniments. I’ve called it Prophet, after the synth. It’s a decent start but I’m not sure how to continue it from this point on.

  • Woke up with this tune in my head this morning. Managed to record it before I forgot it, then I added some accompaniments. I’ve called it Prophet, after the synth. It’s a decent start but I’m not sure how to continue it from this point on.

  • Added the final pieces of my self-hosted Forgejo instance this morning: a MacOS runner, and daily backups. I think we’re finally ready to start using it for current projects now.