Good explanation of an important design pattern as soon as you have remote calls.

This is indeed two sides of the same coin. A good reminder that you need to pick the right approach depending on the context.

This explains quite well how TDD is made of several cycles of different length.

This is a funny setup. It's not very expensive either.

Or how it's possible to expose an object-oriented like API for a data oriented framework without sacrificing on performances.

Rituals are definitely important... if you understand why you're going though them. If you just "go through the moves" they're failing.

Seriously... Developers should be ashamed to produce such invasive tools.

Don't throw estimates out of the window. Keep in mind that the more precise they are the more expensive they become.

Interesting point of view. I'm not sure I fully agree with the classification but it gives something to mull over. For sure the less reliable your estimates the more padding is needed to have some predictability.