The contrast is indeed very stark. I got my own bias and fondness for heroic failures.

Feels a bit odd to go to such length to put it in numbers. And yet, it's clear that friendships in the workplace are a must. They should be fostered rather than stifled.

This is indeed an important cultural trait in the Rust community. This can bring challenge when integrating Rust code into a context with more ambiguity.

This has been documented for a long while. Of course, it's been followed by an unhealthy fascination for the "Toyota way". This kind of cargo cult of course lead you nowhere to doing things properly. And yet, now that the dust settled, there are good lessons to learn from Toyota management back then.

An odd but interesting article. When a journalist randomly discovers that his wife is the best Tetris player in the world.

Interesting research. Can it give insights on the pervasive views of the time?

Or why focusing on the practices will likely lead to cargo cult and you might never reach the real benefits. Don't mimic other organisations, think about the underlying philosophy.

Definitely this! All systems are produced in a given context. The organisation and the people producing it are what matters most to get something of quality (or not).

This would probably be a good thing indeed. We'll see of the web culture will evolve next.

If you're wondering where emoticons and emojis are coming from, this is a nice little piece about that.

Nice little article to get an idea of the culture and art behind magic tricks.

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.

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 really a funny idea. I admit I'm curious about what it contains.

Very nice article on the Wikipedia success. Or why being boring and the ultimate process pettiness became the crucial part of the formula. This community really developed a fascinating culture which so far resists to mounting political pressure... But will the editors morale hold?

This is already an old article now. Still the core of it still rings true. The optimistic note at the end of it didn't come to pass though.

A good way to frame the possible models for your organization regarding remote work. The GitLab Handbook stays a very good resource regarding remote work, they really thought about it and documented their findings.

Indeed, it's not just about hiring people it's also about having a safe culture in the workplace.

Both approaches have their pros and cons of course. Whatever you pick, it has to start with a care for quality shared within the team.

I like this article. Indeed, focus on building organisations and teams where it's easy to do the right thing bit hard to fail. This is much better than obsessing over mythical 10x engineers.