[al_borland]

Sadly the docs are error messages are not seen as part of the product and something that is needed to make something complete. Shipping fast and constantly adding new features has pushed good documentation to the backseat. It’s something that’s nice to have, but almost no one prioritizes, so it never gets done.

From what I’ve seen, it is also something that comes with a mature team, as some stability is needed before a team starts to talk about documentation and standards. The constant churn of teams hurts documentation and error messages a lot. Why bother documenting or writing good errors if you won’t be around in 2 years to deal with it? More people need to stick around long enough to feel the pain of their bad decisions and laziness.

[mangamadaiyan]

> Shipping fast and constantly adding new features has pushed good documentation to the backseat

I'd just like to add -- shipping fast and constantly adding new features has pushed _almost everything else_ -- including design, and product quality -- to the backseat. Design documents are a rarity these days, forget about well-written and well thought-through design documents.