Remove .Net Remove Continuous Integration Remove Software Review Remove Test-Driven Development
article thumbnail

AoAD2 Practice: Zero Friction

James Shore

To share your thoughts, join the AoAD2 open review mailing list. When we’re ready to code, nothing gets in our way. The deploy script will run the full test suite, and we also have a canary server that checks to see if anything goes wrong. A few minutes later, it says INTEGRATION OK , then starts deploying the code.

article thumbnail

AoAD2 Practice: Collective Code Ownership

James Shore

To share your thoughts, join the AoAD2 open review mailing list. Collective Code Ownership. Developers. We are all responsible for all our code. But how does that apply to code? Collective code ownership means the team shares responsibility for their code. It’s your code. Mob Programming.

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: Incremental Design

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. It’s Not Just Coding. Computers don’t care what your code looks like. If the code compiles and runs, the computer is happy.

article thumbnail

7 Business Drivers for More Software Engineering Excellence

Accenture

It’s becoming more and more difficult to identify areas of life that don’t depend on software. Yet it may surprise you that much of the software we use every day is poorly written and designed, has little code coverage, and has created in users such low expectations that people – despite much bellyaching – simply put up with.