http://blogs.msdn.com/ricom/archive/2004/02/12/71665.aspxPaul Vick has some interesting things to say about his experiences in this blog . I think we carry a lot of the same scars.en-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/ricom/archive/2004/02/12/71665.aspx#71824Thu, 12 Feb 2004 17:04:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:71824David LevineI carry many of the same scars. <br> <br>I'd add one rule to the list he gave; <br> <br>rule #11. Performance is a feature, not a side-effect. <br> <br>In other words, it should be given first class status as a product requirement the same as any other feature. It should also be quantified otherwise you wont know when you have achieved your goal.http://blogs.msdn.com/ricom/archive/2004/02/12/71665.aspx#71837Thu, 12 Feb 2004 17:36:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:71837Jack Mayhoff [MSFT]From the other side of the fence, Maintainability and Readability are also Features and not side effects. <br> <br>Juggling game. Only add performance where its needed, not for any other reason. Case by case basis.http://blogs.msdn.com/ricom/archive/2004/02/12/71665.aspx#157110Wed, 16 Jun 2004 14:14:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:157110Jack Mayhoff [MSFT] it should be given first class status as a product requirement the same as any other feature