ClickedyClick

I’ve recently started playing Book of Hours and very quickly that led me down on an interesting rabbit hole, and had more of an effect on my “physical world” experience (that to contrast with the in-game one) than most other games recently.

This blog was left fallow for quite a while now.

Today’s story is a little note to self, something to remind me when I next hit the same issue.

A few months ago I’ve tried to up to Kagi, a subscription-based search engine, that I heard a lot of good stuff of.

Once in a decade or so the time comes to install (or reinstall) my personal computer.

Seemingly identical configurations, different results.

It’s pretty much impossible to miss the big push to use AI/LLM (Large Language Model) coding assistants for software engineers.

A bit like last time this post is about a bit of programmer hubris, a bit of AI, a bit of failure… Though I also took away more lessons this time about software engineering, with or without fancy tools.

It’s a relaxed Saturday afternoon, and I just remembered some nerdy plots I’ve seen online for various projects, depicting “code age” over time: how does your repository change over the months and years, how much code still survives from the beginning till

Doing software engineering (well-ish) is pretty hard to imagine without working in version control, which most of the time means git.