Create your own awesome maps

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account?
Log In

Code Oversight by Mind Map: Code Oversight
0.0 stars - 0 reviews range from 0 to 5

Code Oversight

Risks of solo programming

Tunnel Vision (a.k.a. Frog in a Well) Fatigue Higher defects Less knowledge transfer More distractions Less refactoring Weaker problem solving

There are no best practices

There are only the practices you are using now.

And practices that are better than the ones you are using now. -- Corey Ladas

Definition

2 pairs of eyes have viewed code before check-in

Team ownership

Option 1: Pair programming

2 people working as team

Overall time 15% more, repaid in shorter & less expensive testing, quality assurance, field support

Better designs, shared knowledge, team building, enjoy work more

Many styles: ping-pong recommended often

Option 2: Peer programming

Do some work, another dev must review and check-in

More time to explain, delay in reviewing, onus on reviewer

Coding can still be solo

Email pass-around – Source code mgmt system emails code to reviewers automatically after checkin made.

Option 3: OSS committer model

Do no harm principle

Commits reviewed by core team

Partial commit access an option

More suited for large teams

Option 4: Formal code review

Meet and review code line by line

Least fun, most tedious

Longer delay between written code, reviewed code

May not find more bugs than less formal reviews