Avoiding documentation bottlenecks while maintaining quality? (take II)

[Ned Bedinger]

Geoff Hart wrote:
> Several folks have written in to propose the "good/fast/cheap: pick  
> two [one?]" problem.
> 
> Without for a moment denying the validity of that tradeoff, there are  
> many ways you can make it less onerous:
> http://www.geoff-hart.com/resources/2001/triangle.htm
> 
> Basic notion is that you almost never have to eliminate one of the  
> three characteristics, and framing the problem that way tends to make  
> people assume that this is true. Most often, it's a question of  
> figuring out how to mitigate the consequences of the tradeoff. Again,  
> this isn't just theory... it's all based on real solutions I've used  
> throughout my working life.

Your 2001 article for the STC mag reminds me of the kid who is looking 
for a lost coin where the light is better, instead of where it was lost. 
:-)

Eschew obfuscation. Endorse the quality triangle.

Ned Bedinger
doc at edwordsmith.com