Different companies have different needs, early stage startups would probably fire you for spending too much time on documentation because they're paying you to make progress on their product and you're usually working alone anyways or very small teams with heavy interaction. So not only would nobody ready it, it would become outdated within a month.
People think that documentation needs to be kept up to date. It doesn't.
You don't have to always write docs saying "here's how this system works".
You just write a document as a proposal saying "here is how I want to build this system".
It takes 30mins. It helps everyone. If you want to change the system significantly, you just write another design doc.
Also, if you do this you probably don't have to redo things all the time.
If a company fires you for outlining how you're going to solve a big problem - they aren't going to do well anyway so you don't miss out on much.
Based on my experience from a fast growing billion dollar company, and a company that you would call "fast moving" but will never be anywhere near as successful because they can't focus, let alone sit down for 30mins and write a document.
