Good basic post on dogfooding. I also believe this is critical and something that has been trickier personally in the last couple of years.

“We are sleepwalking into a terrible situation where a few parties have almost complete control over our entire energy supply, while these parties don’t fall under any energy law. We regulate them as if they were a normal website, which means we hardly regulate them at all.” Bert Hubert

Advanced Testing with Go slides and video: quite a lot of good content not specific to Go. (via Ben Hoyt)

TIL the name “Protege effect”, but I’ve definitely seen and experienced this too. Mentioned in this list of reasons why hiring juniors is important.

Good suggestions for evaluating dependencies - I would look at project activity before the code, though, just because it’s much easier.

I also look up the project on snyk (socket is also ok, but I find snyk more insightful), and do some searching around CVEs and security.

Recommendations from people or organisations or projects I trust have an impact, too.

Interesting thoughts on accidental vs. deliberate spending in the context often of open-source funding. The linked splitting the check idea is interesting in too, although these really need big players to get on board to get anywhere.

Long but good read on Agile, Scrum, Jira, and the like (but with more cussing than it needs).

Scathing take on the viability of a Mars colony.

In a reflection of the last 20 years Matt Gemmell has 5 lessons learnt:

There’s no substitute for just doing the work, day after day, year after year. The best strategy is almost always to avoid conflict. Quitting the news enhances happiness. Mental health is a very real thing, and you never completely heal from abuse. Becoming a parent changes everything.

These all resonate with me very strongly.

Interesting thoughts on automated dependency updates - I’ve come across this in work situations too. At the moment we’re also going for a quite minimal approach focused around when we do releases.

I love this accident forgiveness policy from fly.io. I think this really is one of the most terrifying aspects of using elastic cloud services.

Wonderfully pointless network transmission via a profile field.

“the dream of every Aucklander being only a short walk away from a bus on a 15-minute schedule” - people who write things like this seemingly have no idea what kind of places Auckland encompasses, and it’s always super annoying to read.

A bunch of new features from Apple focused on the death of a loved one would be really great. There would be plenty of heartstring-tugging opportunities for marketing, too.

Good talk by Gylph on “the perfect Python project” - the important bit is about 2/3rds through, after the song.

Delightful (with explicit language) screed against the current business obsession with genAI.

Ben Brooks in his latest journal (membership required and recommended):

“Why are we still doing signatures? It seems really antiquated when you realize you could sign with biometrics [and] I could not tell you if it was my signature or not on most documents because …I am pretty sure I have three signatures now. I have my ‘wet ink’ signature that I can sign with a pen. I have my left-handed fingertip signature than I do on most digital documents when asked. And lastly I have my […]scribble that I have come to do when shit is more annoying than anything else. None of them look remotely the same.”

So true (both points).

I’m no expert on TV viewing metrics, but this:

“Figures provided by TVNZ show the premiere episode of NZ’s Best Homes with Phil Spencer had an average audience of 490,000 – almost half a million people. Notably, that was more than the 473,900 who tuned into the final episode of Sunday last month” (This Spinoff)

sounds to me like the people who are watching linear TV on a Sunday night don’t care what’s on, they’re just watching at that time.

It also boggles my mind that about a tenth of NZ are still watching linear TV.

Horrific but incredible tool to convert a PDF to a podcast episode. I don’t have a key to try it myself, but the examples are pretty incredible.

I guess for people that are ok withh summaries and like getting information via audio, this could actually be useful.

Via Simon Willison

“The hard lesson we learnt is that effective, long term remote work requires specific skill sets and DNA to pull off."

I wish people took that as the lesson rather than “remote work doesn’t work”. I also feel like orgs that suddenly became remote/distributed did it poorly in most cases so have come to poor conclusions.

Interesting comments on language, too. Canonical seems to do this well, even with ~100 countries. I’m not sure why that is.

Somewhat a side note, but I agree this with:

While many orgs have the utopian goal of committing the entirety of institutional memory into neat documentation, knowledge maps, and wikis, I have come to realise that it is essentially a pipe dream. If we look around, rarely is an org able to copy another org’s culture or way of working

The list of good traits to look for when hiring for remote/distributed is good, too.

An interesting theory that great engineering managers are great at debugging. I think my experiences match this, but I don’t think I have enough data (either way) to be sure I believe it or whether it’s more correlation than causation.

Interesting - I’ve been reading a bit about rewilding lately (on The Spinoff and in the linked physical book) and here it is applied to the internet.

I really like that by current job pushes towards this:

Our job is to keep open as much opportunity as we can, trusting that those who come later will use it.

But I think this is one of the biggest challenges:

Instead of tech firms extracting and selling people’s personal data, different payment models will fund the infrastructure we need.

This is a lot of words on “no wrong door” policy, but basically it’s just asking another group for help on behalf of someone (copying them in) rather than just directing them to the other group.

I definitely agree with this approach and try to follow it myself.

Pretty compelling argument to use “login” and “permissions” instead of “authN” and “authZ”.

Good advice on effective communication. I like how the focus is on outcomes rather than specific implementations. Most of the outcomes are ones that I’ve had when communication was working best, too.

This is near the end, but super valuable advice:

One of the most important tools you can use, regardless of channel, is to just decline to engage. If you don’t have anything to add, don’t have time to take on more, or just aren’t interested: say so.