Wow, this is the entire content of a +5 Insightful post.
Could you at least give us a single piece of technical evidence to back that up? However anecdotal?
The question is "Do you feel vindicated or victimized by the +5Insightful rating for your post?". As you must realize that your completely common place observation has been 'agreed to' as being 'Insightful'. Congratulations man, you're part of the 'problem'
Reactionaries always whine about 'those dirty damn liberals' as an effort to distract from real policy discussions. Troll like, they are often spit out comments about how 'their liberal friends' are 'so stupid'.
I wish websites would understand this.
Some already do. Almost any ecommerce site, and many 'support/help' sections will redirect based on specific searches. What you want to know is what they are, and for them to more often to support account function queries.
"Where did you get that ring???" sob - slap slap
To that you're supposed to answer "I went to Jared", or at least that's what the TV says will make her and her closest friends happy.
Now, technology marches on, and all you need is a big pack of green chemlights from walmart... crack them, drip the liquid in a field, and instant, cheap, area denial..
Maybe for an hour or two, those glow sticks don't last that long. Mines have a much longer 'death span'.
In the business world you have hopefully more experienced programmers than the average undergrad.
You weren't talking about the 'average undergrad' reading the code, but the Professor, and his TAs. Somehow you seem to think that academics are the only people who need to understand code quickly.
Comments are integral to demonstrating that, knowledge, but there is no need for doing that in actual application development.
I read that as: "I don't comment code, it's only good for showing that you've learned your lesson". Sounds to me that you were taught properly in college, but just don't 'like' to do it in real life.
Truly good code is both 'easy to follow' (for a coder of appropriate skill) and well documented. Bad code is neither. Good code and bad documentation (inline and external) is generally acceptable, but harder to learn/fix/change (well, without errors).
I don't have the time/energy to produce documentation appropriate for everything that I do, but at least I don't lie and say that it is never needed.
. But that's because the professor (or rather, the TA:s) need to quickly read through 50 or so computer lab reports every couple of weeks, and doing so without comments takes ages
However in the business world we have all the time in the world?
Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?
