Ask HN: Short and Simple Technical Writing Standards
I'm looking for a short list of Do/Don't items that people can refer to when writing documentation. Something that people with English as a (long used and familiar) second language can understand.
In a similar vein of thinking, I've run into multiple people in operations and development who feel like documentation is something someone else does. They don't feel the need to write descriptive ticket comments. Nor do they want to learn about best practices and standards. I guess this feeds into the more general question of how do you push people to improve themselves?