Quote:
Originally posted by /)eathKiller:
ROTFLMAO that is SOOOO true!
Comments and Indentation are for the weak! Who in their right mind fills a complicated-enough looking structure with just more words unless they want to make it look like they REALLY worked hard on it [img]tongue.gif[/img]
|
I do.
You try debugging someone elses work. Let alone your own work ten projects down the road..
why did i do that again???
It's not to make it look like i worked hard on it, that goes without saying.. it's to let other programmers (and myself) know what i was doing and why i did it.
When you get a job as a programmer and your first project is to finish off what the last guy/girl was working on when he/she left.. let's just hope it isn't a twenty mb program with no comments anywhere eh?
As far as indentation goes.. i do that because it looks cleaner imo. What will an employer think when you are showing them your portfolio and some of your code modules and you have if-tests or select cases/switches within select cases/switches and no comments anywhere. The next dude applying for the job does have comments in there and his/her code is more readable thanks to the indentation? Whose work is easier to understand? If your going to be on your own.. well then well and good continue programming klingon style.. if you are going to be working in a team environment.. you'd best learn to start commenting..