The evolution of the software industry has created two separate roles: The developer and the tester. Traditional software development put these two at odds. Now, agile practices are bringing them together again in order to meet the original business goal: working software.
When developers know how their applications are really being used “in the wild,” they will build better software, more efficiently, and with greater confidence. Sebastian Holst shows you how using application analytics.
Given the fact that the bulk of a developer's work is maintaining and enhancing existing code, Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to help later developers tie the source code syntax to its meaning in the application domain. Using simple tags and clearly thought out rationale to provide just-enough value.
Fixed price contracts are often decried as evil, however they are something which many agile teams face. How can a company execute one using agile practices to achieve better results with lower risk? 16
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect? 45
This article takes a look at Edward Deming's work and it's applicability to Agile methods. 2
To turn code into working software we need to deploy and test it. Often, we fail to emphasize the latter as well as the former. 2
In this article, the layered architecture of test automation is presented to solve the problem of test logic getting buried in unrelated supporting code. 9
'Release It!: Design and Deploy Production-Ready Software' by Michael Nygard discusses what it takes to make production-ready software and explains how this differs from feature-complete software. 4
Continuous Integration has become a standard development best practice - but it's not always done well. InfoQ presents advice and examples in Chapter 6: Continuous Testing from a new CI book. 4
Mark Figley talks about enforcing coding standards and best practices in an automated fashion through the build process. 5
Can refactoring and TDD create “working software” that survives real life? Michael Nygard suggests that "leaky abstractions" ambush us at 5AM when we've paid too little attention to architecture. 25