Interested in how dithering works? All the algorithms you will ever need are probably on this list.

A long paper which explains what can be expressed with concepts in C++.

This is a very valid question. The most likely answer is somewhat cruel though.

Indeed it feels like the Rust community has a cultural problem around abstractions. In a way it feels similar to the one Java developed years ago. This can bring lots of complexity and obfuscation you don't want in your project.

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.

Not a large corpus and some are more idioms than just words. Still it's a nice little experiment with interesting entries.

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.