Real programmers don't comment their code. It was hard to write; it should be hard to understand.
Real programmers don't comment their code. It was hard to write; it should be hard to understand.
thanks for letting us know
some entropy with that sink? entropysink.com
there are two cardinal sins from which all others spring: Impatience and Laziness. - franz kafka
real programmers are rational thinking human beings designed to analytically solve problems from an objective viewpoint. You won't remember everything that you've written no matter how good you think you are. Comment.
EDIT:
fool
you know how many hours i've slaved over quake2 source trying to understand that caca? Well, about 30 times longer than if it had been freaking commented well
Lighten up.Originally posted by axon
thanks for letting us know
I had the same problem with Wolfenstein 3D when I first started C. Sure they labeled the sections with little headers, but the comments just weren't there, but it probably has ore than Quake 2. It also helped that the name of the source files really didn't help much. Luckily there were online groups that gave descriptions of every file and had line numbers were certain variables were located. Plus, the assembly was commented, arent Carmack and Romero nice.Originally posted by Silvercord
you know how many hours i've slaved over quake2 source trying to understand that caca? Well, about 30 times longer than if it had been freaking commented well [/B]
Last edited by unanimous; 03-24-2004 at 11:01 PM.
yes, the wolf 3d source code was freaking impossible to read, regardless of how good you were. I just spent hours playing with it and finally got to change the color of the main menuOriginally posted by unanimous
I had the same problem with Wolfenstein 3D when I first started C. Sure they labeled the sections with little headers, but the comments just weren't there, but it probably has ore than Quake 2. It also helped that the name of the source files really didn't help much. Luckily there were online groups that gave descriptions of every file and had line numbers were certain variables were located. Plus, the assembly was commented, arent Carmack and Romero nice.
but most of my problem was probably that i was using the borland turbo 3.1's editor
Maybe game programmers have a special compiler which strips comments out of their source code when they go public... they can still release their source code, but it wont do any good if people don't understand it :P
Real good programmers do comment their code. It wasn't that hard to write, it shouldn't be that hard to understand either.
By the way DavidP, a horse is a badly capitalized handle to an Orse ( whatever that may be ) One day you will understand that
hth
-nv
She was so Blonde, she spent 20 minutes looking at the orange juice can because it said "Concentrate."
When in doubt, read the FAQ.
Then ask a smart question.
>Real good programmers do comment their code.
No, real programmers don't comment their code. If it was well written, the code is its own commenting.
>Real programmers don't comment their code. It was hard to write; it should be hard to understand.
This is a very old joke by the way, just in case some of you were taking DavidP seriously.
My best code is written with the delete key.
Real programmer ?
Thanks guys, now I am really confused whether I am a real programmer or not
How do I know that
>How do I know that
If you've had the perseverance to complete a program larger than "Hello, World!", you're a real programmer. I've seen a lot of people give up before that.
My best code is written with the delete key.
Hang on guys...lemme finish my "Hello World" program and then I'll come back as a REAL programmer ;Originally posted by Prelude
If you've had the perseverance to complete a program larger than "Hello, World!", you're a real programmer. I've seen a lot of people give up before that.
>By the way DavidP, a horse is a badly capitalized handle to an Orse ( whatever that may be ) One day you will understand that
lol
NEVER!!! I shall never give in to the Hungarians!
Self documenting code will tell you what the program is doing, the comments are there to tell you why. The reason why is often times far more important then the how.
i know david was just making a joke, but there's NO WAY you could figure out a program that's over 50 lines or so in assembly...unless the variables were VERY well named...but even then...
I've heard of a fully graphical OS written entirely in asm, can't imagine how many lines of code that is.
PHP and XML
Let's talk about SAX