You are done writing code. Now what, ship? You have other things to do, and this code review is “delaying” you. Yeah, no.
Software Engineering can be like running a car repair shop. You have to be able to wait for the parts to arrive for one car that’s in service, and be able to move to a second car, leave the first one half-way repaired while the parts for it arrive, then go fix the first car now that its parts have arrived, then back to the second or third car, and so on.
Can you imagine, if the next car doesn’t start getting repaired until the first one is fixed. Or worse yet, that the first car is pulled down and called done with a drilled hole and shop’s random rusty screw and given back to the customer, just because we didn’t wait for the parts to arrive because we really needed to get to that second car?
Code reviews are professional, they are part of the process, and they are an implied expectation by our customers and stakeholders.
Software Engineering can be like running a car repair shop. You have to be able to wait for the parts to arrive for one car that’s in service, and be able to move to a second car, leave the first one half-way repaired while the parts for it arrive, then go fix the first car now that its parts have arrived, then back to the second or third car, and so on.
Can you imagine, if the next car doesn’t start getting repaired until the first one is fixed. Or worse yet, that the first car is pulled down and called done with a drilled hole and shop’s random rusty screw and given back to the customer, just because we didn’t wait for the parts to arrive because we really needed to get to that second car?
Code reviews are professional, they are part of the process, and they are an implied expectation by our customers and stakeholders.