Once again GitLab has plenty of good advice for operating remotely. This time it is about meetings which are obviously part of life in an organisation. And actually, quite some of the good tips also apply to in person meetings.

This is an interesting pattern that I still seldomly meet in C++ codebases. Of course don't go overboard with it, but don't be scared of using it for wrong reasons.

Indeed it is. It's not the perfect or most sexy language, and yet it has some interesting properties.

This article is short but very interesting. That's indeed something to keep in mind when using Postgres, you could have surprisingly bad performance results in some cases otherwise.

I'm trying to approach interviews like this as well. It's better for everyone when it feels like a conversation rather than constant questioning. The trick is to still capture information about the skills you need to evaluate though.

A very long read but contains lots of insights. Goes from two very famous security related failure, to highlighting how a test first approach could have helped. It then finishes with a long section on how to foster a testing culture in an organisation.

An old one but it shows quite well how social engineering works. It's often way more powerful than the technical defense you try to raise.

Tiny intro to using cryptsetup. I confirm it's surprisingly easy.

What's behind the notion? Some historical musing about self-organizing teams and the design they produce.

A few interesting ideas for having retrospective at a larger scale than the single team.

I still think we have an ageism problem in our industry. I feel it's less than before, but this short article shows well how far it went.

Serverless based architectures leading to bad cases of complexity and latency when used for more than trivial workloads... who knew!? ;-)