> Sometimes the WTF you've just encountered has justification, and it takes a deep dive to understand the code enough to know why. God forbid some documentatio

> Sometimes the WTF you've just encountered has justification, and it takes a deep dive to understand the code enough to know why. God forbid some documentation. At a previous employer I was consistently baffled at how nearly all information about the mission critical application (and the business) was distributed through random verbal conversation, with the remainder coming from those deep dives into the code (at least until I could no longer hold my breath). There was literally zero documentation for an application with 1 million lines in the source tree and another million in SQL stored procedures (!!!). The size of the project alone was shocking considering it was a fairly standard line of business app, albeit with inventory, HR and customer interaction all rolled into one, but the experience was just about as bad as it gets for development and organizational practices.