Documentation (including code comments) are vital and important, but it's far better to bake the proper constraints into the code/specs so that it's hard to make mistakes. Then the docs are less necessary, shorter, and easier to understand. I think this is what GP is getting at.
I don't think that's engineer so much as lazy bureaucrat in power. It's the mentality Douglas Adams made fun of with the "Your planet is being destroyed, you had plenty of time to read the posted notice".
Sounds like a classic footgun to me.
If people don’t read, it’s their fault. Reading the docs is not a big ask.
Documentation (including code comments) are vital and important, but it's far better to bake the proper constraints into the code/specs so that it's hard to make mistakes. Then the docs are less necessary, shorter, and easier to understand. I think this is what GP is getting at.
Typical engineer spotted.
I don't think that's engineer so much as lazy bureaucrat in power. It's the mentality Douglas Adams made fun of with the "Your planet is being destroyed, you had plenty of time to read the posted notice".
How dare we read documents before we put technology into use.
Like asking a bridge engineer to know the spec of his bolts.
2 replies →