The meaning of pragmatism as a term has been hijacked to mean subjectively justified hacking and piling up a mountain of cruft.
A "just dump it under the rug while no one is looking" development.

**Proceeds to add the 25th dependency in a class and a corresponding stub in 50 tests, while breaking a bunch of other tightly-coupled-to-implementation tests that suddenly fail for a wrong reason**

Vulnerability to be seen as a human (that makes mistakes).
A precondition for building trust among people and safety.

We want our old DDD Nick back!

Often, when we reach the step that when discussing a bigger change we initially wouldn't have agreed on, once we got there in smaller steps, it's often not a point of contingency anymore because we realize our assumptions were wrong or that we didn't really understand each other.

"No one is going to take you serious if your book is less than 350 pages long"

Let me think about it.
Hmmmm...yeah, people will vomit more (even worse) code.

That's to say, teams that struggle with refactoring skills are also teams that most likely struggle with design skills, because tapping into a rich pool of domain and design insights generated as you refactor in small, safe steps is out of their reach.

2/2

I wanna join!

But then I won't have the chance to practice my skills for reverse engineering understanding from the implicit code!