Requirements documentation
@Tony
>>academic guff or, MBA style drivel
Pot, meet kettle.
>>all designs are a series of compromises based on (hopefully well identified) priorities in an ever chnaging environment
True, and the better identified, the better the requirements
>>design and code quality are perceived as very low value.
Design and code quality perceived as low value? What are you smoking, brother?
I work with 20- and 30-something year old ASP, .NET, C programmers who think they're smarter than everybody else, and even they wouldn't make such a ridiculous statement about quality of design and code. Not having THAT, tony.