"Yes, but all #documentation is technical debt. You constantly have to update it. It’s always wrong. Consequently, you should write as a little of it as possible."

👆 The worst take that keeps fueling #agile zealots.

This keeps pushing the "#code is documentation" racket. No, documentation needs to be there because it's the only thing that destroys the silos. Because we had a bad way to document doesn't mean we don't fix the core problem of making documentation effective.

The best documentation is a #design diagram that's used for communication to run the project - not something used by only one or 2 roles in the organization.

Roping this into #TechnicalDebt is just absurd. And tech debt is such a bad analogy anyway.

This dysfunction in the supposedly advancing computing trend of agile is what forced us to come up with #EventModeling

@adymitruk so often skipped, and it slows everybody down. We’re still human and tend to be afraid we’re the only ones with a dumb question, so just go along. Design diagram gets everyone in the same page and gives the ability to ask questions in context.