-
The thing about DNS is that you’ve got one chance to get it right, otherwise your SOL for a good 15-20 minutes.
-
After almost 3 years to the day since buying it, my roll of cling wrap ran out. Took a lot less time to go through than my last roll of cling wrap. It was only 90 metres though, so that sort of tracks.
-
Getting software ready for go-live is a bit like landing a plane. Get what you have ready to go early, and once you’re done, just land it. Final approach is not the time to say “hey, what would be cool is if you can get this thing done too.”
-
I’m always at a loss of how best to represent a small number of items with a large number of properties in an SQL database. Tables feel great when the number of rows is dramatically larger than the number of columns. But when it’s the other way around, when you have one or two rows in a table with 30 columns, it feels strange. As if it’s out of balance.
I do wonder if some of these alternatives could work better:
- Having one DB table contain the items and another containing the item properties. This second table will only have four columns:
id,item_id,property, andvalue. - Storing the properties in a JSON column or similar.
These will probably work well for items with dynamic properties, or when only a subset have values at any one time. It would also be viable if one wouldn’t need to select on these properties, as querying this information would be a pain (although doable). Would it also work if the items don’t have dynamic properties? It’ll probably reduce the number of migrations involved.
This is probably just a me problem, and I should just write the table “naturally,” with one column per property. It’s not like the database cares.
- Having one DB table contain the items and another containing the item properties. This second table will only have four columns:
-
Sometimes a TIL (today I learnt) should really be classified as a WTTMT (wish they told me this).
-
For anyone else trying to use ESBuild with a build script, just note that attempting to run the build script using ESBuild will not work. Instead, you need to run it with Node:
# Wrong $ esbuild ./build-script.mjs # Right $ node ./build-script.mjs -
There’s lots to like about MIDI as a standard. The connectors are good (cables are plugs, instruments are sockets) and the protocol is easy to understand: 2-3 byte messages with support for vendor extensions. It’s not perfect (16 channels is a little limiting) but for a standard, it’s pretty good.
-
Don’t wish plumbing issues on my worst enemy (washing machine hose sprung a leak and needed to be replaced). 🥵
-
What percentage of the population would know about Linux? 10%? 15%? Smaller? Either way, seemed notable hearing someone in public say “Linux emulator” at the cafe.
-
Really enjoyed the latest episode of Revolution.Social with Anil Dash. A great discussion around ethics of using AI. Can recommend listening to it. 🎙️
-
It’s amusing (if it wasn’t so disappointing) to see all the layout bugs that still persist in Safari for macOS when you’re switching and closing tabs. Reminds me old-school CRTs with dodgy deflecting coils.
-
🦆 Dialogue
LLM Auto-complete Is…
Duck: You writing code? Author: Documentation. Duck: And you're using an… Author: IDE? Yes, I am. Duck: Do you have that… Author: LLM-powered auto complete? I do, yes. And it's fine, although it does seem like the IDE's… Duck: Always trying to finish your sentences? Author: Yes. It can be quite… Duck: Bothersome? Yeah, I can't imagine how that must feel. 😛 Continue reading →
-
The Grand Prix is a lot of things: noisy, disruptive, expensive. But I wouldn’t call it “the fabric of our community.” 👎
-
When I found out Current was going to ship this week, I postponed making a video preview of my own RSS reader because it would feel like I was interfering with Current’s release.
I don’t know, mate. Some of us here on Android are hanging out for relief from what is a decades long drought of good RSS readers. Times are getting desperate, and I can hear the siren song of coding agents.
-
Ooh, one of the escalators on Southern Cross platform 9-10 has been refurbished. Very nice. We’re 1/3 of the way done.
-
It’s kind of strange to hear the same PA voice make different announcements on different tram classes. Happy to say that doors will open on the left for E-class trams, but not A-class.
-
Does anyone else have this much trouble getting out and meeting people? Is it just a matter of practice? Is it just me that usually comes home feeling like a fool? Ugh!
-
No, I tell you what it is. It all feels a little too anonymous, at least for me. Having a smaller gathering where you all know each other will probably be better for me.
Or maybe something with a little more structure. Where you’re given a role, rather than ask to come up with one yourself. 🤔
-
Coming to the realisation that in order to get the most out of a boardgames social gathering, you really need to have played a lot of boardgames, something I haven’t really done. And I’m not sure I like boardgames enough to develop this. Which makes me wonder if this is worth keeping up.
-
I do wonder how familiar my fellow developers are with descriptors like “snake_case”, “camelCase,” or “kebab-case.” Been trying to negotiate with someone over a data format and they used one themselves, but didn’t understand another. Maybe I should’ve used Pascal case (which I’m unfamiliar with).
-
This week’s earworm is Axiom Verge OST. 🎵
Well I say it’s this week’s earworm but the truth is that I wanted to listen to it today, and I keep forgetting the name of this album. I’ll remember that I posted about it here, though.
-
I remember. OS/2 may be gone, but it’s not forgotten. 🙂
-
I think the idea of video for podcasts may have some promise, but not if you’re simply grafting video on the existing podcasting experience and show format. On the phone, you’re fighting against people watching short-form video delivered by an algorithm. Attempting to go head-to-head with the TikToks of the world is a loosing battle, and I can’t see it work well with the feed-based approach of traditional podcasts (unless you like spending all your time making short-form videos).
No, what wins in the traditional podcasting ecosystem is deep para-social relationships with those putting out a decent show on a regular basis. That’s why I think the shows that’ll do well here are ones I can watch on my TV. Shorter that audio-only podcast episode (I’ve got stuff to do) yet long enough to make it seem worth it to me, that rely more on that visual element (interviews are fine, but what am I getting watching you instead of just listening), and that require my full attention. Imagine YouTube if all they had were subscriptions.
-
It’s interesting hearing about Apple planning a video-based “podcasting” service with support for HLS. It may seem like podcasting is all video now, since everyone with a show is publishing on YouTube. But I suspect that a lot of those playing a podcast on YouTube aren’t even looking at the video: they’re treating it as an audio player. They’re only using YouTube to gain discovery from the algorithm, since it’s so difficult to get this within the open podcasting ecosystem. So what would they gain from Apple’s offering that they’re not getting already?
