The slower the test suite, the more we'll be retracing

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.

»
Author's profile picture Dragan Stepanović

How to minimize MTTR for change in the code?

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.

»
Author's profile picture Dragan Stepanović

Trading and TDD

“To achieve wealth optimize for minimizing losses over maximizing gains”

»
Author's profile picture Dragan Stepanović

Wanna increase MTBF of your system?

Try building quality in by shifting left on the collaboration. Instead of mobbing on the outage, mob during the development. Diversity of thoughts, needed skills and system understanding builds the quality in.

»
Author's profile picture Dragan Stepanović

Wondering why your efforts to reduce PR size further are not going to work?

With every halving of the PR size, you get 2x more interruptions for each of the reviewers of a given PR. Multiply that by the number of PRs in flight (one person, one PR) and you get the total number of interruptions in the team.
E.g. if it’s mandatory for at least one person to review the PR and if you have 4 developers in a team, total number of interruptions in the team increases 8 times (4x2). Just for one halving of the PR!

»
Author's profile picture Dragan Stepanović

The problem is not the monolith full of cruft and technical debt

The problem is the engineering culture lacking design, refactoring, and incremental development skills that produced it as an artifact.

»
Author's profile picture Dragan Stepanović

Delivering value?

The ways that we usually set up “cross-functional” teams doesn’t really help us with this, but it’s crucial for each member and role in a product development team to ask these questions on a regular basis:

  • “How are our features doing in the production?”
  • “Are they meeting users’ needs?”
  • “How do we know that that’s the case?”
  • “Are they solving the problem that they were supposed to solve?”
  • “Is the work and effort we’re putting in delivering value or we’re just spinning our expensive wheels?”
»
Author's profile picture Dragan Stepanović

Architecture influences the need for documentation

Have you thought about how architecture and functional decomposition of a system influence documentation and a need for it? 🙂

»
Author's profile picture Dragan Stepanović

Pairing and mobbing for Psychological Safety

It’s very true that in environments without psychological safety pairing/mobbing or any kind of close collaboration won’t work.

»
Author's profile picture Dragan Stepanović

Mob-Commit-Revert

Mob/Pair-Commit-Revert

»
Author's profile picture Dragan Stepanović