|
And did a black button light up black saying "don't press that"?
|
|
|
|
|
OriginalGriff wrote: Service Temporarily Unavailable
That's how I feel every morning 
|
|
|
|
|
... What exactly was abusive about this?
Heavy hitter too: platinum level abuse vote.
Now, I don't care about rep points, but I do get the feeling that someone is abusing their position...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Shirly winkled away somewhere in a log file somewhere there is record with an ID of who dumped on you. The privileged should be able to get at it!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
Well .. yes .. unless that service is temporarily unavailable!
|
|
|
|
|
Perhaps it's from the guy who wrote the error message? Easily offended, error message writers. It can't be easy knowing that everything you do is wrong! 
|
|
|
|
|
Member 9082365 wrote: Perhaps it's from the guy who wrote the error message?
Or from the one that write the failing code ? 
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
I think this guy is also raging in QA. It looks he is easily upset if answers don't use the tone he likes.
He downvoted 5 of my answers in a matter of 10 minutes. Ok I tend to be not nice to people that simply ask for a solution for their homework
I have even been downvoted for recommending to use a debugger to someone that didn't understand what a piece of code was doing, and another one that did not understood why its code was failing.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
|
How did they got dressed so well. 
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
|
And you're not God! If you don't want to know then don't read it. There was surely enough information in the thread title?
|
|
|
|
|
Member 9082365 wrote: surely enough information in the thread title
Yes.
|
|
|
|
|
|
The Only Thing Necessary for the Triumph of Evil is that Good Men Leave Catch Blocks Empty
|
|
|
|
|
ON ERROR RESUME NEXT
Software Zen: delete this;
|
|
|
|
|
At least the code won't annoy the user with, "Program stopped working" pop ups. 
I'll go with the devil.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Exceptions are for sissies. Programming languages supporting exceptions are toy languages. 
|
|
|
|
|
|
try
{
...
}
catch
{
throw;
}
|
|
|
|
|
Oh, you think an empty catch block is your ally, but you merely adopted bad code. I was born in it, moulded by it. I didn’t see good code until I was already a man; by then, it was nothing to me but a hindrance!
Sorry, had a Batman marathon last night 
|
|
|
|
|
I have an old blog, started circa 2010, last article 2012. I wish to reinvent and renew this blog, and would like to 'hide' the old articles. I thought it a perfect idea to shift them into CP, as new articles. Is that type of thing OK with members? There will be no plagiarism or duplication, or even sharing the articles elsewhere.
I want to shift the emphasis of my blog, www.thepraxis.co.za[^], toward more theoretical and academic discussion (with the occasional libelous, mouth-frothing rant), and concentrate my more practical efforts, i.e. coding inventions, how-tos, etc. and concentrate the more practical articles on CodeProject and CodeGuru.
No object is so beautiful that, under certain conditions, it will not look ugly. - Oscar Wilde
|
|
|
|
|
do you mean to let CP consume only new blog post, but not old? It sounds to me perfectly Ok...
See here how you can sign only specific blogs for CP, but not others...http://www.codeproject.com/script/Articles/BlogFeed.aspx[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Old blog articles as CodeProject new articles? Why would anyone read more than 3 years old articles?
May I be bold enough to suggest the opposite: The old blog articles remains on your blog while you post your future new articles on CodeProject.
|
|
|
|
|
Shao Voon Wong wrote: Why would anyone read more than 3 years old articles?
Because they may be still relevant?
I see for example, that many of your articles predate August 2012. Do I take it you are about to delete them all? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
