"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 on documentation; have you come across https://esi.nl/research/output/methods/a3-system-overview?

On technical debt, I started to call it software “inventory” https://www.linkedin.com/pulse/hidden-costs-software-inventory-dirk-jan-swagerman

What do you think about that?

A3 System Overview

ESI
@djswagerman too detailed, too technical.

@adymitruk in an embedded systems context, the A3 already reduced existing architecture docs significantly. Not sure if you can reduce much further without negativity onboarding or new employees.

What do you use?