2 ms·
> they should be captured in your specifications / docs / ADRs, in a concise form that respects the reader's time. And if'n they don't? What should the disresp
by eviks 2mo ago
> they should be captured in your specifications / docs / ADRs, in a concise form that respects the reader's time.
And if'n they don't? What should the disrespected reader of the future do, not use the non-concise form?
> I guess everyone's just too cool to actually write good docs now?
They've always been cool like that, good docs have always been rare and precious
- NateEag 2mo ago> And if'n they don't? What should the disrespected reader of the future do, not use the non-concise form? Sure, the reader should still use what's there. I thought we were discussing the best ways for a team to structure its codebases and processes for comprehension, not how to survive in the face of bad techniques. > They've always been cool like that, good docs have always been rare and precious Yeah, that's certainly true. I feel like it's gotten worse since the grand LLM invasion, but maybe I'm off-base.