Linked by Eugenia Loli-Queru on Sun 29th Jan 2006 21:05 UTC
Very little software is written once, installed, and then never changed over the course of its lifetime. And yet, the most prevalent development practices used in the industry treat change as an afterthought. This chapter will teach you to not only anticipate change in your software but develop specifically with change in mind. Also, this chapter provides a set of guidelines and formulas to think about when preparing large product teams for the large meetings that move their work forward.
Thread beginning with comment 90758
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Recent Original Stories
Recent Comments
Headlines
Random Comments
Random Stories
Random OS Link
Member since:
2005-12-21
Don't use C++..
Should be: Don't use C++ unless you actually know what you are doing. Then you'll be just fine. Stick to Java/C#/Python/Ruby/<insert_latest_fad_here> otherwise - especially if performance is not an issue.
Not kidding at all.