go ahead... be a heretic | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Hi,
have a quick look at crush_data-node which was one of my first postings here. It took me some 30 or 40 lines to do what merlyn did in just one line. But -hey- that's simply OK, because there is a way you'll probably trod along while you sometimes use this or that language to fulfill this or that task. As long as you can acutally solve the problems you got at hand (say without further constraints like performance or the like) you're doing a good job as a (Perl)programmer. You'll probably get to points when the job has to be done particularly good (e.g. better than the coder before you did ;-) That will be one of the moments you start thinking thru things more precise and maybe find other (better) ways to fulfill a task. That is what programming in C is for me ;-) Anyway, in Perl I tend to refuse to think about further constraints as long as I get the job done, because at least 95% of the perljobs I do are straight forward and don't care whether they take 5 seconds or 5 minutes...
Regards
In reply to Re: Stepping in the Footprints of a Perl Programmer
by stefan k
|
|