Hacker News Reader

Very nice article. My primary question: when I need to document the process, how do I best encode the culture and values into the document?

Should I aim to explain the values that we're upholding (code quality, documentation quality, test quality, etc.), in every step?

View on HN

My takeaway from the article was exactly that: if you document anything, document the WHY, not the HOW. That way, when the HOW changes with time, the WHY will guide its new form.

Agreed on the quality of the article. As always, Rands manages to put the right perspective on the topic. I'm forwarding to quite a few process-averse folks I work with.

Yes, this is the real problem. I find all process-related documents are, once written, shelved and ignored.

Reply on news.ycombinator.com