Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

Your Code is Not a Version: How 'Build for Disable' can bring you true continuous integration by Mind Map: Your Code is Not a Version: How 'Build for Disable' can bring you true continuous integration
0.0 stars - reviews range from 0 to 5

Your Code is Not a Version: How 'Build for Disable' can bring you true continuous integration

Build for Disable Techniques

Code Example: OldMath vs NewMath

Simple if check with a static boolean

Add a method for the alternative approach and static boolean

Extend the class and override the methods you want to change. Point the app config at the new class, and to disable point to old class

Actually USE interfaces!!

Leads to better coding practices in general

BONUS

Presenter Info

Nicholas Tuck

This preso url: buildfordisable.nicholastuck.com

Previous Brown Bags

TheSoftwareGardener.com

twitter: @nicholastuck

Find me on G+ (not kidding) seriously...

The Goals

Be productive... every day

Stop fearing merging and start improving your product confidently

Thought Experiment

The Room for Improvement

Feature Branch

Simple Solution

Commit Constantly and Push Hourly

Why Isn't Everyone Doing This? Introducing 'Build for Disable'

Few teams are implementing true continuous integration because we believe our code exists in versions

The Solution

In closing

Your code as a version

Your code alive

Review Goals

Questions?

How do you manage peer reviews with everyone's code mixed together

Does this only work if there exists a good automated test suite on the project?

When do we remove the extra and disable code?

When do we peer review the code? Before disable code is removed or after?