Software: do you write it like a book, grow it like a plant, accrete it like a pearl, or construct it like a building?
The older I get, the more I believe that the only way to become a better programmer is by not programming.
In software, we rarely have meaningful requirements. Even if we do, the only measure of success that matters is whether our solution solves the customer's shifting idea of what their problem is.
In corporate environments the product don't have to be good. Sometimes they don't even have to exist... if you are a thoughtful developer, you are in the wrong place!
The best reaction to “this is confusing, where are the docs” is to rewrite the feature to make it less confusing, not write more docs.