|
I had a user once who would have phoned for the same. Not because he read the help. He clicked everywhere and made lists of everything that he did not like. Then he would forward memo after memo to the CEO to complain about the system. CEO later knew that he moans for the sake of it...
|
|
|
|
|
Some people aren't happy unless they are moaning
|
|
|
|
|
And don't make me do it. You'll regret!  
-
Just that something can be done, doesn't mean it should be done. Respect developers and their efforts!
Jk
|
|
|
|
|
Not as an afront to other developer's. More as a comment of frustration - typically when having to code around e.g. an API not working as documented, or code working around bugs in other systems. They also serve a purpose to prevent future developers (myself included) removing such workarounds in favour of the "clear" approach that failed originally.
|
|
|
|
|
Does "Bugged like hell." count?
I tend to mark things as "Depracted" during tests and use "Bugged like hell" as a description (when applicable), I know it's the wrong way but it's the way it gets the attention it deserves.
My colleagues notice the description and start asking questions to the one responsible, if he marked it as 'finished' that is.
|
|
|
|
|
I have never seen it done and wouldn't think to do it: utterly pointless and childish. I may curse like an old navy salt but in code? Why would anyone bother to do that?
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
Have you ever tried to fix a program without any structure? Real spaghetti code? Often everything is so mixed up with all the rest that you can't really do anything at all except throwing the whole mass away and writing a new program.
In such cases I often had to do terrible things myself to keep the program running and, usually unlike the heroes who caused the mess in the first place, leave a comment to let those who come after me know why I did what I had to do. And perhaps a note about why the programmer who caused all the trouble is a disgrace to our craft.
The first part of the comment may be helpful to someone later, the second part just makes me feel better. I could just as well post it in the code horrors section, but my bosses would not let me do that. Recently I retired a web application which could be posted there completely. I did not find one single thing that I could live with. Can you really blame me for wanting to drown the guy who wrote it in the river?
"I just exchanged opinions with my boss. I went in with mine and came out with his." - me, 2011
---
I am endeavoring, Madam, to construct a mnemonic memory circuit using stone knives and bearskins - Mr. Spock 1935 and me 2011
|
|
|
|
|
CDP1802 wrote: Have you ever tried to fix a program without any structure? Real spaghetti code? Often everything is so mixed up with all the rest that you can't really do anything at all except throwing the whole mass away and writing a new program.
Blimey!!! How did you know??? It's what I've spent most of the morning doing. Fortunately the chap (who is in India) is still with us so I am talking him through writing some proper code.
CDP1802 wrote: Can you really blame me for wanting to drown the guy who wrote it in the river?
However annoyed with him I am I just can't see the point in adding childish or unhelpful comments to the code: surely that would reflect badly on me rather than anyone else?
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.
nils illegitimus carborundum
me, me, me
|
|
|
|
|
3) I used to.
4) I'm going to start now.
5) I don't write comments (the Q&A approach).
6) I cuss in code.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Manfred R. Bihy: "Looks as if OP is learning resistant."
|
|
|
|
|
Number 6, always.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
if(condition) UpYours()
else YourSock();
All the best,
Dan
|
|
|
|
|
So maybe I do sometimes, temporarily, but would never keep it in the code. Its unprofessional.
I know a couple of our developers that has done it but in afrikaans which is their home language. For the customers sake.
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >>
|
|
|
|
|
I'd probably be thrown out if I did.
I cuss a lot in life.
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it.
|
|
|
|
|
|
Totally agree! 
|
|
|
|
|
Agree! Though I don't do it always but yes sometimes when I get frustrated.
|
|
|
|
|
So agree...
This happens mostly when we got a code which was developed by another developer. 
Rating always..... WELCOME
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
oh! absolutely right
sunaSaRa Imdadhusen
+91 99095 44184
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
or 
or 
or 
or 
or 
stuff, for my further reference I just comment it with some funny words.
