Stories
Slash Boxes
Comments
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

use Perl Log In

Log In

[ Create a new account ]

xsawyerx (8978)

xsawyerx
  (email not shown publicly)

Journal of xsawyerx (8978)

Thursday December 18, 2008
09:24 AM

Retiring deprecated projects

[ #38115 ]
Recently, an old project I worked on (and deprecated) was passed on to a new developer. When moving the materials with explanations for them to the new developer, it seems hard to let it go. Not so much because of the sentiments towards personal projects (and by that, I mean projects that I personally do - not just projects for myself), but more so because I feel like I've done such a poor job compared to what I would do today.

The improvements we make within a relatively short period of time to our abilities, insights, concepts and understandings are so tremendous that it makes sense how better we could do anything. I can't let go of the desire to bring the old code up to date with my current abilities or what I perceive as the bare minimum. I'm sure others feel this way too.

I don't think I can shake this feeling, but maybe with time, when more recent projects will be in par with what I perceive as reasonable coding standards (Damian, Critic, etc.), I'll have less and less to try and shake. I guess the most I can do at this point is try and work on a reasonable explanation to why I wrote the following line, and hope no one will ever remember it:

$subjects{"$subject"} = $id . ";;" . $desc;

Possible explanation candidates:

  1. He made me do it”
  2. “I was up 3 days in a row” (exempli gratia)
  3. “I didn't do it” (a la Simpsons)
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.