|
I know you were being facetious, but seriously, this is sometimes done. IMHO it is professional malpractice of the worst sort and should result in being summarily fired. If it's done to keep the coder's job, it should have exactly the opposite effect.
BTW, this should be caught in code review.
As a separate issue, there is sometimes the need to obfuscate the code, for IP reasons. There are code tools that can do this reversibly (I am the author of one).
|
|
|
|
|
But they must be helluva productive, having written most of the code I got to see in my career.
|
|
|
|
|
They all work for Sage.
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
|
|
|
|
|
And I doubt they left comment in this forum!
Marc
|
|
|
|
|
I comment on code where I think "Hmmm in 6 months when I look at this again, will I know what I am looking at?"
So tend to block comment rather than every line, and tail-comment on a complex or unusual line of code.
(Also, why is it possible to select "I don't Comment" and any other comment selection? Mutual Exclusivity!)
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
|
|
|
|
|
Dalek Dave wrote: "Hmmm in 6 months when I look at this again, will I know what I am looking at?"
Heck, I can't even remember what code I did yesterday... 
Nothing more embarrassing than asking all the collegues: "What idiot did this piece of code?" just to get the answer "You did!"
|
|
|
|
|
I mentioned in a thread in the lounge a little while ago about seeing the horrors of a 16x Nested IF...THEN...ELSE statement.
It was one of them slowly increasing over time things that got out of hand, so I rewrote it as a CASE, but I was embarrassed about that one!
------------------------------------
I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave
|
|
|
|
|
6 months? Sometimes last week is more like it!
I have to say that I do not ever comment code to say what it does. It should be obvious, as the saying goes 'it does what it says on the tin!'. If it is not obvious then either the method is to long, or the method is badly named.
Hoever, I always comment what I was thinking at the time. At least then I know why I wrote this rubbish, and it is usually only rubbish if the reasoning/understanding of the problem was wrong, or the problem changes.
|
|
|
|
|
Dalek Dave wrote: Also, why is it possible to select "I don't Comment" and any other comment selection? Mutual Exclusivity!
I won't comment on that.
|
|
|
|
|
But, in fact, you still can.
Ninja (the Nerd)
Confused? You will be...
|
|
|
|
|
I was in middle of code handover at client premises, and the IT personnel was like: "I cannot see any comments in your code  "
Then we did.
Noman Muhammad Aftab,
Software Mechanic
|
|
|
|
|
It's going to be interesting to see the result...
modified on Monday, July 19, 2010 4:43 AM
|
|
|
|
|
|
Very well asked, I agree.
|
|
|
|
|
Of course good question. But 10 12 21 27 people voted for "I do not comment code." 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
