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.
Serverless based architectures leading to bad cases of complexity and latency when used for more than trivial workloads... who knew!? ;-)
Tiny intro to using cryptsetup. I confirm it's surprisingly easy.
Indeed it is. It's not the perfect or most sexy language, and yet it has some interesting properties.
This article is short but very interesting. That's indeed something to keep in mind when using Postgres, you could have surprisingly bad performance results in some cases otherwise.
Wonder what is gamma correction and why it's needed? This is a nice and short explanation.
Interesting stuff, very rich I think I'll have to get back to it. This gives good clues and ideas of metrics to look at when evaluating teams output. Some of the findings confirm hunches which is welcome. It also shows that measuring productivity keeps being a messy business, there are so many factors influencing it in some way.
Good reminder that it's better to design your APIs to avoid putting people in the situation of inadvertently creating a divide by zero.
Interesting approach to gauge how accurate a profiler is. With some results in the Java ecosystem, so now you know which profiler to pick there.
It's a bit of a sour article but it rings so true... We let Open Source take the mantle in companies which are mostly free loaders and churn closed products, or even worse have them closed and DRM protected. There's really quite some work to still realize the Free Software goals.
A reminder that if there's too much complexity in your configuration the syntax used to represent it probably won't save you from issues.
Interesting tag... It's indeed been totally forgotten somehow.
Apparently people need to be reminded that "Don't Repeat Yourself" is more a guideline than a rule. So "The Rule of Three" is a way to do that (although I find ironic it's called a "rule").
It's kind of an unusual design choice... This is subtle, I think I'm still a bit on the fence regarding this one.
Well done everyone. This bullet was dodged... for now! This kind of fever comes back regularly unfortunately.