Linked by Thom Holwerda on Tue 18th Dec 2012 23:12 UTC
Permalink for comment 545850
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2007-03-26
1/Coding under strong time constraints, a burst of inspiration, or something else that puts their minds' focus elsewhere.
2/Not able to notice the mess left around until they try to read through it again after a few months without touching it.
The human brain's content indexing abilities are truly a thing of magic, but they become a hindrance when you try to distinguish what's clean from what isn't.
Some good points but I don't entirely agree with point 2 on a personal level.
I tend to rewrite code as I code it (usually because I'm mentally debugging it as I'm programming so find cleaner / more optimal designs as I'm writing it). So the mess generally does get noticed (baring when I'm under time constraints, as you mentioned in point 1.
That's purely my method of programming though. I'm by no means saying it's better or worse, nor that you were right or wrong with your view
Thankfully that example did go on to explain the routine and the reason the for kludge. I just cropped that out of my post as it didn't wouldn't mean much to anyone who wasn't involved in that project.