NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Merciless Refactoring (Score:2)
A good friend of mine, let's call him "George", would get deeply involved in some code he was writing, and would occasionally get tired of chasing the odd bug. His response was the famous three step process:
Now, George wasn't cavilier about this. He'd invest a decent amount of time in his code. Occasionally, he gets to a point where his understanding of a problem is much deeper now than it was when he started coding. For George, deleting all his code on a project[*] (or sub-project) was something to do when he was tired of dealing with yesterday's bugs and wanted to code it up the way he should have written it in the first place. Classic example of "throw one away".You can't get much more merciless than that. ;-)
*: For best results, temporarily forget about the backups and CVS revisions before you rewrite the code you just accidentally deleted. ;-)
Reply to This
Re:Merciless Refactoring (Score:1)
As is normal, I try to commit after every (write-test; code-code; pass-test) cycle, and I try to keep those cycles smallish. I refuse to leave my CVS checked out overnight, and delete it if it isn't committed. Some people think this is bizarre enough, but I've fou
rjbs
Re:Merciless Refactoring (Score:2)