Linked by Thom Holwerda on Tue 18th Dec 2012 23:12 UTC
Permalink for comment 545840
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 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2010-03-08
Sadly not all developers can be bothered to do so and if they've used nondescript variable / functions names as well as weird developer logic, then the code might as well have been deliberately obfuscated.
I've worked on plenty of projects where debugging other peoples code worked out just as time consuming than if I had rewritten the code from scratch. Albeit we're talking smallish projects in those instances.
From personal experience, even good devs who have a pretty good idea of what good code looks like can write pretty unreadable code if they are...
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.
I remember once stumbling across the following within one of Oracle's own APIs for Java / Oracle RMDBS Forms: "This is a terrible kludge". It pretty much summed up the entire product in one line hehe
These clever snippets become much less funny when you try to figure out what the code actually does, though
Edited 2012-12-19 08:09 UTC