Depends on the project.
A lot of startups and even larger businesses create experimental products that require fast, sloppy code to cut down costs. Rather than having well-documented code that'll get scrapped in a week anyway after the MVP fails, or the product is so simple it doesn't need to be architected -- just assembled crudely.
Then you have gigs where you work on an existing product pushing new features to it, and those require more documentation to ensure people down the road know what happened to the main pipeline.
It's all part of the pyramid of quality. You can either have something that works great, takes no time at all, but incurs great costs -- or sacrifice one for the other. And usually, people don't want to sacrifice time or cost, so you'll find that the quality dwindles greatly.