Writing technical standards people follow
Most technical standards I have encountered were written once, read twice, and ignored. Not out of rebellion. The document was forty pages, it did not say why any rule existed, nothing enforced it, and the person who wrote it had moved to another team. The standard was true the day it was published and fiction a year later. I have written a few that teams did follow, and failed with more than a few that they did not.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in