Remove 2016 Remove Continuous Integration Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Build for Operation

James Shore

Test-Driven Development. Continuous Deployment. Complicated configuration ends up being a form of code—code that’s written in a particularly lousy programming language, without abstractions or tests. It’s okay to use DEBUG logs during development, but don’t check them in. Feature Toggles. Further Reading.

article thumbnail

AoAD2 Practice: Incident Analysis

James Shore

2016], particularly chapters 12-14. A programmer makes an off-by-one error, but their pairing partner suggests a test to catch it. A team member accidentally erases a file, but continuous integration rejects the commit. The details of how to respond during an incident are out of the scope of this book.

article thumbnail

Lean Software Development: The Backstory

LeanEssays

To counter sequential processes and the long integration and defect removal phase, agile software development practices focused on fast feedback cycles in these areas: Test-driven development: Start by writing tests (think of them as executable specifications) and then write the code to pass the tests.