Adam Dymitruk   Nov 13, 2022

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

Show threadSidNov 13, 2022

@adymitruk IMO, addressing it as "Agile zealots" is a bit reductive. A *lot* of people who profess to follow Agile only give it lip-service, and ignore the actual principles and rationale that drives it, which defeats the purpose. I've heard it termed as Fragile Development from time to time.

1/n

Show threadSidNov 13, 2022
@adymitruk From what I've seen, the main driver for documentation is that code tells you WHAT happens and HOW it functions, but it'll almost never tell you WHY. And when the code's incorrect (a bug, or a change in business direction), not knowing why something was written will make it ridiculously hard to change safely or easily. Documentation captures intent. I've been meaning to write a full post on this; there's a lot to unpack there (feeble mind likes to procrastinate).
2/n
Show threadSid
@adymitruk I'm interested in the idea of #EventModeling though, it's not something I'm personally familiar with so I'll need to look it up. Interested to see how it deals with these problems. Thanks!
3/end
Nov 13, 2022 at 6:57pmWeb
Show threadAdam Dymitruk   Nov 13, 2022
@sid I have lots of material including meetup recordings and podcast interviews.