A bit of a rant, but since it looks like people are still trying to consider all those technologies are equivalent... I think it's good to have an explanation on what makes containers different.

If you spend your time in dull meetings and then run like a headless chicken... it's definitely a sign you should cut down on the meetings and keep only the ones focusing on solving actual problems.

Interesting alternative retrospective format. The way of framing the questions might help get new ideas.

Interesting stuff. This should ease greatly sharing code between shaders and the host application, especially for data specification which is easy to get wrong.

Looks like a good set of tips of get more DDD practices in place without the badly understood vocabulary which usually comes with it.

A bit of a self-serving post towards the end. Still I like it because it clearly mention that it's not about dropping all documentation in favor of the code (quite the contrary in fact, documentation is very much needed). It really is about treating code like documentation, putting the same care into it in terms of readability and understandability. If you wonder what code reviews are for... it's also for this readability concern.

This is definitely a funny hack. I wonder how long the people behind this knew about the vulnerability and waited for the right opportunity to do something with it.

Important principles to have in mind for proper UX/UI designs. There are more of course, those are the bare minimum though.

Just looking at averages is indeed quickly hiding patterns. Make sure distributions are visible in some fashion.

A look back at XP practices with some interesting insights. This doubles as a good XP primer as well.

A list of opinions on our field. It's personal and biased of course, so make that you want out of it. I agree with most I'd say. A couple are rather niche though.

Looks like a nice resource to get better at finding the root cause of performance regressions and optimising code.