Re^3: Should I leave behind beautiful code or readable code?

So where does DrHyde say it was a dumb question? He simply pointed out that entertaining the idea of leaving some code of dubious merit when you could fix it anyway was grossly unprofessional. I tend to agree with that.

At $work, I have to deal with crappy legacy code written by people who don't know any better, but if one has to ask the question in the first place then there's probably something wrong.

• another intruder with the mooring in the heart of the Perl

Comment on Re^3: Should I leave behind beautiful code or readable code?

Replies are listed 'Best First'.
Re^4: Should I leave behind beautiful code or readable code? by BrowserUk (Patriarch) on Mar 28, 2007 at 18:14 UTC
Well. The first bone of contention is whether there indeed is any code of dubious merit. It is a value judgement and peoples values vary and change. Some call the code in question beautiful; some call it ugly; some, complex; some functional; some idiomatic. You and DrHyde may have your opinions fixed--through experience or dogma--, but to expect that the OP should have fixed his opinion and reached the same one as you is plain...wrong. but if one has to ask the question in the first place then there's probably something wrong. Yes! What is wrong is that the questioner has either insufficient experience to have yet reached a conclusion; or perhaps is starting to question the efficacy of received wisdom. Either way, seeking council on the way to reaching his own conclusion shows intelligence and forethought. The OP has the right to reach his own conclusions. And to demerit him for seeking council in bolstering his inexperience or indecision is likewise, wrong. Bullying of the very worst kind. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]
Re^5: Should I leave behind beautiful code or readable code? by DrHyde (Prior) on Mar 29, 2007 at 09:49 UTC
Some call the code in question beautiful; some call it ugly; some, complex; some functional; some idiomatic. But in this case, the person who wrote it who is also the person who says that he can fix it says straight out that it is hard to read, and that the only reason for leaving it as it is is pride. As for the notion that pointing out obvious error is "bullying" - thankyou, you've made my day. I'm upvoting your node for having exceptional comedic value.	[reply]
Re^6: Should I leave behind beautiful code or readable code? by BrowserUk (Patriarch) on Mar 30, 2007 at 05:50 UTC
I'm glad it amused you. I pretty much knew it would. You might like to read this. It's real short, shouldn't take you more than 30 seconds. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]