![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
blufive"What we need is a detailed design document of our system"
I've been making noises about how we should be writing documentation for at least the last 15 months. This particular colleague always flys off the handle at the merest suggestion that he should document his code. He's responsible for a large part of the system (indeed, the entire component) he's now complaining about.
I suspect that if I nagged him about documentation, he'd flip, as usual. I despair, sometimes.
Cause. Effect. LEARN! Is it really that hard, just because cause and effect are six months apart? Apparently so, judging by the number of "professional" programmers who churn out code all day without bothering at any point to write down what it does...
I've been making noises about how we should be writing documentation for at least the last 15 months. This particular colleague always flys off the handle at the merest suggestion that he should document his code. He's responsible for a large part of the system (indeed, the entire component) he's now complaining about.
I suspect that if I nagged him about documentation, he'd flip, as usual. I despair, sometimes.
Cause. Effect. LEARN! Is it really that hard, just because cause and effect are six months apart? Apparently so, judging by the number of "professional" programmers who churn out code all day without bothering at any point to write down what it does...