BT
  • The Developer-Tester Divide

    by Gil Zilberfeld on  Apr 25, 2012 2

    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.

  • The Rise of Application Analytics: A New Game Demands New Rules

    by Sebastian Holst on  Dec 27, 2011

    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.

  • Implementation Decision Rationales – Program Comprehension in Agile

    by Fabian Kiss on  Feb 28, 2011 4

    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.

Agile Team Meets a Fixed Price Contract

Posted by Marcin Niebudek on  Jun 30, 2010

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

Are You a Software Architect?

Posted by Simon Brown on  Feb 09, 2010

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

Agile Lessons from a Management Guru

Posted by Ahmed Yousuf on  Sep 08, 2009

This article takes a look at Edward Deming's work and it's applicability to Agile methods. 2

Deployment is the Goal

Posted by Julian Simpson on  Aug 13, 2009

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

Layered Architecture for Test Automation

Posted by Bei Li on  Aug 11, 2009

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

Book Excerpt and Review: Release It!

Posted by Ryan Slobojan on  Dec 20, 2007

'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

Book Excerpt: Continuous Integration means Continuous Testing

Posted by Paul Duvall Steve Matyas Andrew Glover on  Aug 05, 2007

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

Implementing Automated Governance for Coding Standards

Posted by Mark Figley on  Jul 26, 2007

Mark Figley talks about enforcing coding standards and best practices in an automated fashion through the build process. 5

Agile, Architecture and the 5am Production Problem

Posted by Michael Nygard on  Jun 25, 2007

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

BT