development lifecycles
Better Software Magazine Articles
|
So, You Want to Be a Consultant? Many practitioners see becoming a consultant as their ultimate career goal. But what does it mean to be "a consultant"? In this email to an aspiring consultant, Fiona Charles (a consultant for more than fifteen years) discusses different consulting approaches and describes how working for a consulting firm can help you get there. |
||
 |
Catch Them Doing It Right Rewards can be powerful management tools, but only if you implement them effectively. In this installment of the Management Chronicles, discover how the right timing and getting to know your employees better can improve the impact of your recognition method. |
|
 |
A Release Without a Tester In this article inspired by an unfortunate video store rental, Lee Copeland invites software organizations that think testing is expensive to try the alternative. |
|
|
The Right Business Analysis Tool The continued rise of the business analysis profession has led to a surge in software tools specifically designed for the business analyst. Find out what types of tools are in the marketplace today and how to select the right business analysis software tool for your organization. |
Matthew Leach
January 13, 2010 |
|
|
IDEs and Build Scripts Teams benefit from using both IDEs like Eclipse and integration tools like Maven. Steve Berczuk discusses the risks that can occur when IDEs and build scripts diverge, and provides guidelines for keeping the two consistent, so that teams can be more productive. |
||
|
Software to Go: Developing Applications for a Wireless World The mobile arena is in constant evolution, changing the way we approach software development both from a business and a technical perspective. Taking the time to set your plan can make the difference between success and just a good idea. In this article, Luis Carvalho shares some guidelines for bringing new applications into the mobile ecosystem. |
Luis Miguel Carvalho
July 15, 2009 |
|
 |
Testing the Contract Metaphor A contract represents a service agreement between two parties, the bounded provision of service by one party to the other. This metaphor also applies to how we can think about the relationship between unit tests and code. A contractual mindset encourages test names and partitioning based on clear propositions, backed up with executable examples. |
|
 |
GUT Instinct Whether or not a unit test is considered good is not simply about what it tests: It is also very much about "how" it tests. Is the test readable and maintainable? Does it define the expected behavior or merely assume it? To be sustainable, the style of a unit test is just as important as the style of any other code. Perhaps a little surprisingly, the most commonly favored test partitioning style does not meet these expectations. |
|
 |
The Trouble with Derivation This article discusses the dark underbelly of derivation: the fragile base class. It's possible to modify a base class in such a way that, even though you've improved its implementation and all your tests work just fine, you've nonetheless damaged the derived classes, perhaps fatally. |
|
 |
A Path to Readable Code Test-driven development is usually presented as a developer process. On the other hand, acceptance test-driven development (ATDD) is a communication process between the customer and the developer. In ATDD, the tests provide the terminology in customer-understandable terms. The customer's terminology suggests abstract data types that make code more readable. |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.