Weeknotes 177

The “journaling suggestion” notifications that iOS produces are continuing to paint a sad picture of my life - “An afternoon in Costa Coffee” is not something I would ordinarily feel I need to process via a journal.

I created a Bluesky account. I’m nothing if not a hypocrite.

My new computer arrived after I missed the first attempt at delivery when the couriers arrived outside of the delivery window I was given. I’ve yet to set it up other than to connect to the WiFi and run software updates.

I saw this ids_must_be_indexed GitHub workflow and because it’s written in Bash it’s a very lightweight addition to any CI. It didn’t work for me on GitHub unfortunately.

snacks.nvim by folke. A similar idea to mini.nvim.

It sounds like the first version of an official Elixir LSP will be out with Elixir 1.18.

The official Elixir LSP should be out with the next @elixirlang version, 1.18.

Via @NickGnd.

Small Steps

Some thoughts on choosing small steps. I think it’s always possible. Is it always the right way to go? I issue a challenge to myself.

Justin Searls' essay on the current job market is an interesting read. I think a lot of this rings true, and it made me reflect on my own position.

One of my side project ideas a few months ago was to build a customer communication platform similar to Intercom – not to start a business, but as a real-life example of a project. I got as far as mocking-up a simple UI for the “chat” interface, but didn’t go any further with it.

I would’ve chosen Elixir and Phoenix for this, for the reasons I’ve written about before. If there was ever a one person framework, this is it.

Well, it seems that someone else has been building such a thing called Papercups, in Elixir, but for the last few years and it has developed an impressive amount of features. Check out this interesting blog post the feature set.

How we made a Ruby method 200x faster

I wrote some test cases with AI for the time this week. It was surprisingly good at it. Of course I had to tweak and test them, but it took the grunt work out of the task.

When I come across some code which I’d like to refactor if it’s untested theres an extra obstacle in the way of that change happening. If AI can help me quickly test it, that’s a good thing.