News for hackers. Stuff that matters.
Re:Wearing Out My Delete Key by Hoff on Monday August 04, 2008 @01:35PM (#266495)
The "ship it" rubric very often trumps the refactor debate; coders and managers tend to see the refractoring entirely differently.
Re:Wearing Out My Delete Key by possiblemat on Monday August 04, 2008 @01:43PM (#266506)
What James is referring to is not necessarily stripping out big pieces of code when they've been working in production for a while. Rather the point is that in a given coding sprint, he gets the first thing that works going, then starts from there and rewrites them better if need be. So it's just an approach to developing a given method or class rather than refactoring for the heck of it.
Re:Wearing Out My Delete Key by Hoff on Monday August 04, 2008 @04:19PM (#266703)
I know what he's referring to.

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.

Re:Wearing Out My Delete Key by jordyhoyt on Monday August 04, 2008 @10:43PM (#267087)
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.
Re:Wearing Out My Delete Key by zenspider on Monday August 04, 2008 @03:59PM (#266681)
I totally agree, and this is exactly what I do an the method/micro level. Generally I can get something working in just a few minutes but then I spend another 5-10 really polishing it up in 5+ small iterations on it (all test driven, so I know my changes still work).

Hoff's point was well above that, at the design/macro level. For that I alternate releases between adding features and house cleaning (bug fixes, refactorings, etc). With a sufficiently short iteration time, you can appease both the client/users with new features and the developers by keeping things clean and happy.