Linked by Thom Holwerda on Fri 15th Feb 2013 10:40 UTC
General Development "Since I left my job at Amazon I have spent a lot of time reading great source code. Having exhausted the insanely good idSoftware pool, the next thing to read was one of the greatest game of all time: Duke Nukem 3D and the engine powering it named 'Build'. It turned out to be a difficult experience: The engine delivered great value and ranked high in terms of speed, stability and memory consumption but my enthousiasm met a source code controversial in terms of organization, best practices and comments/documentation. This reading session taught me a lot about code legacy and what helps a software live long." Hail to the king, baby.
Thread beginning with comment 552951
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: Comment by ilovebeer
by ilovebeer on Tue 19th Feb 2013 17:33 UTC in reply to "RE[5]: Comment by ilovebeer"
ilovebeer
Member since:
2011-08-08

"Code being difficult to maintain can be the result of a bad programmer doing the job, where the code itself isn't the actual problem but rather your lack of ability is."

You are throwing around these underhanded insults implying that we're bad coders if a piece of code gives us trouble, but the truth is that even good coders have trouble with bad code. What's the deal with wanting to defend bad code?

I've done no such thing. If you've taken offense then it's due to your own lack of confidence in your ability because I at _no point_ called into question your ability, or any other specific individual here. That is why I quote "you". That means the comment is not directed towards any single individual, but rather anyone who the comment applies to. No need to get upset Alfman, unless the shoe fits. But then that wouldn't be my problem.

And again, I'm not defending "bad" code. I'm stating the fact that "bad" code is often merely subjective. And the fact that sometimes a persons difficulty in maintaining code is the result of the maintainers inability or inexperience as a coder in general or in a specific area, and not the actual code itself. No sane person with half a clue would disagree with either of those statements.

Reply Parent Score: 2

RE[7]: Comment by ilovebeer
by Alfman on Tue 19th Feb 2013 20:35 in reply to "RE[6]: Comment by ilovebeer"
Alfman Member since:
2011-01-28

ilovebeer,

"I've done no such thing. If you've taken offense then it's due to your own lack of confidence in your ability because I at _no point_ called into question your ability, or any other specific individual here. That is why I quote 'you'. That means the comment is not directed towards any single individual, but rather anyone who the comment applies to. No need to get upset Alfman, unless the shoe fits. But then that wouldn't be my problem."


You can quit this stupid double speak now.


"And the fact that sometimes a persons difficulty in maintaining code is the result of the maintainers inability or inexperience as a coder in general or in a specific area, and not the actual code itself. No sane person with half a clue would disagree with either of those statements."

*Sometimes* that is true, but your initial claim that code and designs can't be bad as long as they work was completely naive. There's nothing more to say here since this is obviously true to everyone else.

Reply Parent Score: 2

RE[8]: Comment by ilovebeer
by ilovebeer on Wed 20th Feb 2013 07:43 in reply to "RE[7]: Comment by ilovebeer"
ilovebeer Member since:
2011-08-08

You can quit this stupid double speak now.

Umm... What are you rambling about? If telling you directly I wasn't calling you out specifically doesn't soothe your butthurt then I guess your confidence really is shot and the shoe fits. Unfortunately lashing out won't solve either of those problems.

"And the fact that sometimes a persons difficulty in maintaining code is the result of the maintainers inability or inexperience as a coder in general or in a specific area, and not the actual code itself. No sane person with half a clue would disagree with either of those statements."

*Sometimes* that is true, but your initial claim that code and designs can't be bad as long as they work was completely naive. There's nothing more to say here since this is obviously true to everyone else.

That's nice. Only one problem... I never said designs can't be bad as long as they work. I said if they work as intended and are stable then they were engineered correctly.

I don't know why you try to be deceiving but whatever the reason, it's pretty dumb. If it's a matter of not paying attention to what's actually being said, maybe you should start....

Reply Parent Score: 2