This organization indeed doesn't seem healthy. Especially regarding the amount of user data they are responsible of.

Good reasons to really make sure your organization practice code reviews.

Make sure your OpenSSH server is up to date.

Starting from a wrong analogy to raise real thinking and questions about TDD.

Interesting approach to structure CSS custom properties. Should help a bit with maintainability.

Makes a strong case about why LLMs are better described as "bullshit machine". In any case this is a good introduction into bullshit as a philosophical concept. I guess with our current relationship to truth these are products well suited to their context...

From the perspective of a given implementation. Still this is a good list of what POSIX 2024 changes. I'm particularly interested to see that per-file-descriptor advisory locks finally made it to the standard. Still some progress to make in this department but it's a good step already.

Obviously very opinionated. Still probably a nice list to pick from when making your own project specific coding guidelines.

Nice return on experience of using a simple stack to serve loads of web requests.

Interesting tips and actions to help frame the conversation. The goal is to get the team better self-organized and directed.

Very good primer on a widespread and very hard to avoid bias. This is why it's hard for projects to properly meet deadlines.

A nice collection of versioning schemes. I definitely didn't know them all.

A nice zine introducing the topic of faults and failures in distributed systems.

If you needed to be reminded that allocating small blocks of memory is a bad idea... here is a paper explaining it.

This is bad for two reasons: 1) people clearly put too much trust in random CDNs to distribute their dependencies and 2) people don't track depencendies obsolescence properly.

I remember playing with this a long time again... but it's actually even older than I suspected.

Definitely not the rules you want to apply on your projects. Still it's interesting to know how the STL uses explicit.

A nice pattern to separate decision from actions in complex algorithms.

This is become an important industry. Regulation is needed to avoid consumers to be in a mouse trap. This is necessary to reap the benefits of those technologies.

This is a useful construct in Python which is often forgotten.