You're a coder. I'm a coder. James is certainly a coder's coder. But stop thinking like a coder for just a moment, though.
Having (functional) product out the door (faster) beats having (better) code in the market (later). Every time.
Do I defend this? Yes and no.
Have I experienced this? Yes.
Wearing my manager hat, the product ships. Code refactoring is extremely difficult to justify.
Wearing my coder hat, I refactor and re-comment and rework and update the test cases while I still remember what I was doing with the particular routines. Then I move on.
This is the age-old conflict between better and faster; elegance and schedule. It's why managers and coders are so often in conflict, too.
True, but code is rarely ever shipped then abandoned. Refactoring is (hopefully) all about making code more manageable and as reusable as possible, not attaining some sort of aesthetic elegance.
You're a coder. I'm a coder. James is certainly a coder's coder. But stop thinking like a coder for just a moment, though.
Having (functional) product out the door (faster) beats having (better) code in the market (later). Every time.
Do I defend this? Yes and no.
Have I experienced this? Yes.
Wearing my manager hat, the product ships. Code refactoring is extremely difficult to justify.
Wearing my coder hat, I refactor and re-comment and rework and update the test cases while I still remember what I was doing with the particular routines. Then I move on.
This is the age-old conflict between better and faster; elegance and schedule. It's why managers and coders are so often in conflict, too.