Dragan Stepanović

When you co-create as a team (together and at the same time) “quality is everyone’s responsibility” mindset is inherent and you don’t have to keep reminding people of it.

The “cost” is increased speed.

tends to be inversely proportional to the amount of mobbing needed during outages.

…which decreases transaction cost, which enables even smaller batches, which means (even more) co-creation.

What if we shift thinking from
“everyone focus on finishing what they’re doing”
to
“everyone helping each other finish what they’re doing”?

I see people having to beg others to review their PR.

I tend to advocate for very small SUTs when (unit) testing (a.k.a. micro-tests).

The slower the test suite, the less often we’ll run it, the more we’ll backtrack whenever we make a wrong turn in the code, the slower we’ll go at the end.

Up until this point I was thinking that tests, as a safety net, help us to extend MTBF of the system. Just figured out that they actually help us with MTTR. But a different kind.