If it fails for everyone then it's not a bad choice on your part, right?

Bunch of random script ideas. Some I don't see the point of for me, some are neat and seem useful.

It was around two years ago, but maybe a good idea to revisit it with the recent AWS outage?

Interesting historical look at how and why modal editing appeared.

Some food for thought about the use of bounded contexts in Domain Driven Design.

I like the approach. Indeed what matters is to have visibility, don't weaponize measurement otherwise the trust will falter.

Looks like an interesting alternative to pulling a full blown ETL for pushing data to ElasticSearch.

Looks like a nice tool for syncing mailboxes locally.

Git pre-commit hooks indeed bring nice benefits. Like everything else they're not a panacea though.

Looks like the trend is now clear. The reasons for picking a web framework are lessening. It's more and more viable to use the web platform directly.

If you're not recklessly accumulating technical debt, this is an interesting way to frame the conversation around it.

It's just impressive what we can achieve with instanced rendering. Even the mobile web browsers support it nowadays.

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.

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.

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.

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.

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.

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.

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.