Remove 2004 Remove Software Review Remove Systems Review Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Test-Driven Development. We produce high-quality code in small, verifiable steps. At best, mistakes lead to code that won’t compile. No wonder, then, that software is buggy. TDD isn’t perfect, of course. Why TDD Works.

article thumbnail

AoAD2 Practice: Feature Toggles

James Shore

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. For many teams, releasing their software is the same as deploying their software. Kent Beck calls it a “Keystone” [Beck 2004] (p.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

AoAD2 Practice: Feature Flags

James Shore

Visit the Second Edition home page for information about the open development process, additional excerpts, and more. To share your thoughts, join the AoAD2 open review mailing list. For many teams, releasing their software is the same as deploying their software. Beck 2004] (p. Test-Driven Development.

article thumbnail

AoAD2 Practice: Continuous Integration

James Shore

To share your thoughts, join the AoAD2 open review mailing list. We keep our latest code ready to release. We keep our latest code ready to release. Most software development efforts have a hidden delay between when the team says “we’re done” and when the software is actually ready to release. Refactoring.

article thumbnail

No Fighting In This (Agile) Dojo with M. David Green

Marcus Blankenship - Podcasts

How can we train teams to consistently produce quality code without negatively impacting productivity? Convincing skeptics to try a new system (32:12). Announcer: Welcome to The Programming Leadership podcast, where we help great coders become skilled leaders, and build happy, high performing software teams. Episode 46.

Agile 59
article thumbnail

Agile vs Waterfall: Key Differences And Definition?—?Which Model Is Better?

Codegiant

Agile is also about human interactions, customer collaboration, adapting to change, and producing working software. You observe how the market reacts to the software you create and then make iterations to improve it. The Agile methodology definition was introduced by 17 software developers gathered in Utah back in 2001.

Agile 52