This post originated from an RSS feed registered with .NET Buzz by Steve Hebert. Original Post: Report from the trenches - lessons from a 1.0 product Feed Title: Steve Hebert's Development Blog Feed URL: /error.htm?aspxerrorpath=/blogs/steve.hebert/rss.aspx Feed Description: .Steve's .Blog - Including .Net, SQL Server, .Math and everything in between Latest .NET Buzz Posts Latest .NET Buzz Posts by Steve Hebert Latest Posts From Steve Hebert's Development Blog

 I’ve spent the last couple of months in a new job, new project, etc..  The project I’m working on deals with securities data and the application's scope is very interesting.  We’re using a combination of ASPX and ASMX services for the consumer-facing services and WinForms apps on the back-end. 

When I started the position, the team was starting a 1.0 release push.  This push has been interesting and I’m sure I’ll be writing more about this in the future.  This process has made me think about universal traits you watch out for when walking into a project.  I think every project does some of these things well and need work on others – finding the right balance for a given project involves continuously questioning the whole process.

• Get so good at integration that it becomes second nature.  Daily builds, build tools, automated versioning, etc.. The sooner you get to this state, the easier testing, validation and cycle time become. 
• Question 3^rd party components ruthlessly.  Assume bad behavior, assume memory leaks, assume bandwidth hogging – make the components prove they can run in your environment. 
• Use 3^rd party testing tools.  Take a look at the testing landscape – tools that allow you to push your code and analyze its behavior.  For hammering on your website or webservices, check out ANTS Load.  For analyzing your code for efficiency and speed – check out profilers.  You can also use these tools to help validate any 3^rd party components.
• Put testing front and center.  Focus first on pushing the testing V into your development process.  Everything else in terms of test driven development, lean management and others will flow from this focus.  Some of these methods will fit your project, some will not – but continuously look to improve.
• Shared database connections are (more than likely) a code smell.  If you are looking at elusive connections problems that cannot be easily reproduced – look for this.

Enough for now, back to figuring out how TCPView works...