"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.

@adymitruk Say more about how documentation destroys the silos.
@dhemery is usable by multiple roles opening the communication channel to be real-time instead of passing off artifacts over a wall to a different role.
@adymitruk Do you mean because the documentation is published as a separate artifact, separate from the code, and accessible to people who don’t have or need the code?
@dhemery yes, but it's close enough to implementation yet not drowning in detail to make it guide and document the code.