-
Really enjoyed Ben Thompson’s daily update about his experience vibe-coding an app. It touches on many of the feelings I have with vibe-coding, such as still needing to exercise basic software development skills to make something good. You may not be typing in lines of code, but you’re still responsible for driving the agent to build something you want. So you’re still on the hook for things like domain or architecture design. That can’t be completely offloaded to AI, nor should you want to. Oh, and UI design. I can attest how bad the current agents are at UI design.
-
Ooh, this is a nice feature of Micro.blog. You can add pages that can hang off the URL of other pages, like a child page. As far as I can tell, it’s just a matter of including the parent path in the URL. I don’t know if you need the parent page. Having one works for me so I didn’t check.
-
Trying out MonoLisa as recommended by Matt Birchler. First impressions: not bad. Looks good in Zed, although it’s a little wider than what I’m used to. I should try it in Terminal. It might look better in a more native app.
-
The name I use for one of my test accounts is “Shouting Loudly.” Why? 🤷 I may had something about speaking softly on my mind at the time. Wish I wrote the reason down somewhere. And yes, I have been asked why I named it that.
-
Prior to dawn.
-
I probably should stop listening to music or podcasts while working on my Godot game. I really need to hear the game’s lack of a soundscape, so I can start filling it.
-
I sometimes marvel at the effort that goes into some graffiti “projects”. Just the scale of some of them, like a single word that’s three people high and takes up most of the back wall of a building. Things that involve a ladder, basically.
-
In fact, I may need to get a new mouse too. The parrots liked chewing the mouse wheel, damaging the rubber cover, and now it doesn’t spin as freely as it did.
-
I had to stop using the Keychron keyboard. It was becoming unreliable: key presses were not being registered, or duplicates events were being emitted. I’ll go back to my Microsoft Sculpt as soon as I get batteries for it.
Follow up
Okay, it looks like restoring factory settings helped. The keys seem to be functional again, at least after a few hours. I can’t for the life of me understand why this would be necessary. But hey, looks like it is.
-
Blogger Archetype Quiz: My Written-in Answers
Blogger reflects on their personal preferences and habits related to blogging and outdoor activities while questioning their archetype. Continue reading →
-
Happy winter solstice from Canberra Airport, where it’s the darkest 4:59 you’ll experience all year.
-
Is It Time For Another Coffee?
Because apparently I had an hour to kill and $54.00 USD burning in my pocket. And because I just read a post about a real coffee tracker and thought it’d be fun making this to suit my sensibilities. 😁
-
Ankur Sethi post about how nobody clicks share buttons on a website. This tracks with my experience: in all my years visiting websites, I can count on one hand how often I clicked those share buttons that appear beside a post. I won’t spoil what people do instead, but I image you can guess.
-
It’s said that “home is where the heart is.” That might be true, but I find that home where the routines are. Where you can rely on the familiar.
-
Finished reading: Don’t Call It Art 10 Ways to Create Like a Kid Again by Austin Kleon 📚
Lots of thought provoking points. Thoroughly enjoyed it.
-
It’s not a proper trip to Canberra without a visit to Tuggeranong. Went to my favourite cafe and walked around the lake, this time in a clockwise direction. Was a lovely morning for it.
-
Was craving a curry a little this evening. Fortunately I stumbled upon a Japanese restaurant called Ikko on the way to where I was planning to go (always look around corners). They do a pretty decent Karaage chicken curry, which I thoroughly enjoyed.
-
TIL that if a Stripe subscription is associated with a test clock, it won’t be returned in a List Subscription call. Not sure if it’s because the clock is set in the future, or it’s just the presence of the clock itself. Retrieving the subscription by ID seems to work, though.
-
If a podcast ends, and it had a subscription plan offering extra content which ended alongside it, should that extra content be made public? Contemplating this while seeing my Downstream subscription get cancelled due to the show finishing up.
My vote is “yes” but that’s easy for me to say.
-
I do wonder if the broader Go community would adopt the new UUID package. It’s purely additive so it’s not like they need to, but the strength of any one library package depends on how many people use it. There’s a lot of network effects involved. I definitely will make use of it, but if database client don’t, it will be quite disappointing.
I feel like they would though. There is some precedent of Go developers adopting new language features, such as threading
context.Contextcalls throughout the call graph. So my hopes are high. -
Go 1.27 RC 1 just dropped. It looks like a bumper release. New JSON package, new UUID package, AND generic support added to methods. Looking forward to this going gold.
-
Really enjoyed My Dinner With Skinner, a take on the “steamed hams” skit from The Simpsons but filmed as as a feature length film (well, a 45 minute film). 📺
-
With the introduction of coding agents in more workflows, it’s interesting seeing where the bottlenecks are starting to reform. So far I see two: code reviews, and deployments. Naturally more code per unit time means more code to review. It seems like more and more of my day are just responding to these requests for reviews. Uninteresting work, but still quite necessary, I suppose.
This was expected, but what I didn’t expect was the pressure placed on the size of deployments. More services are being touched, since doing so is cheaper. In my personal experience, this is mainly because using such agents make it easier to do a more “proper” solution. There have been times in the past where I bodge a crappy fix in one service because I didn’t want to touch five others. This is less of a concern now, but it does mean that deployment will involve six services instead of just one.
We’ll see how this changes in the future. I have head some interesting things around how code review tools are adapting to larger and more frequent reviews, such as adapting are more semantic approach to showing what changed, rather than the half-century old diffs1 we’re using now. As for micro-services, I still feel they’re becoming a relic of the manual coding age and that monoliths may be more useful in the future. Or maybe I’m just wish-casting here.
-
Oh, my apologies: 52 year old diffs. ↩︎
-
-
I kind of regret not writing about a topic because I fear how it would be received in the moment. These tend to be the posts you wish you wrote six months later just to gauge what you were thinking at the time.
-
Daring Fireball: Yours Truly on The Vergecast: ‘# the Epic Story of Markdown’:
But the biggest reason for Markdown’s continuing success isn’t Markdown itself. It’s the triumph of plain text files, both for system configuration and for the interchange of human-readable (and thus, LLM-readable) prose.
This. This is why Markdown is so successful. As expressive as HTML is, it’s not the first format I turned to if I want something I could easily read in a text editor. The ability to easily read Markdown files as plain text is one of its killer features.