View Single Post
Join Date: Jun 2012
02-22-2013, 02:22 PM
Originally Posted by
ya gotta know which three numbers TO edit-and if you're talking legacy code (and we are) from coders that may or may not have documented properly (and we are) being examined/poked/tweaked by coders hired on recently (and we are) it gets a bit more complex than "change x, y, and z values".
If the source code is undocumented spaghetti, then yes, you have more problems then you probably know about. Object oriented coding and encapsulation are not done because it makes coding easier. Procedure oriented coding and OO coding have the same results. It's OO coding is done because it makes bug fixes and modification x1000 easier. "A ounce of prevention is worth a pound of cure" as the saying goes.
Edit: I don't document my code like a dyslexic bibliophile just so
can know (or remember) what or why I thought something.
One the one hand, I've spend a month tracking down a fence post bug because I offset by one twice in two different locations. Basically I read the offset, checked it should be there, scrolled down a few pages, forgot about it, and checked it off as being correct
. (Then again, I was a utter newbie and still using BASIC at the time.) I sense write code that spans thousands and thousands of lines as a hobby side projects and learned from my mistake.
On the other hand, It is literally their job to know the code. If they don't know the code, or have a standard for communicating with section that are not "theirs" they are not doing their job.
In truth I want to give them the benefit of the doubt, and say they fixed it so quick because they
know about the bug
release. I think someone just green lighted it and shoved the ships through so they could start earning money "now", not caring about the long term damage.