|
By chance, I found this: "A" is for "Array"[^]
Perhaps we should point new members to that? 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I think it was about five minutes after I found out where to turn that unattended TRS-80 on in 1978 when I learned what PRINT is for and very shortly after that also IF and ELSE. (must have been something like IF X < 20 GOTO 30 ELSE END). Even if there had been Q&A, I'm very sure I would never have asked that kind of question.
I would suggest we make the book obligatory reading before someone is allowed to post questions. How do we verify that online?
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
"Please enter word 6 of line 18 from page 42"
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Sasquatch
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
They never did really suss out that in a world full of photocopiers, the manual was not as difficult to copy as the disk, did they?
I hated Sierra ones though: when the word was on the wrong page, or misspelled, or ... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Some used silver or copper thermal printing paper for the codes. They gave the copier a hard nut to crack. I still have some with my Atari ST disks.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
A is for Aspirin
B is for Backache
C is for Code-rot
D is for Despair
E is for Eye-strain
F is for Elephanting .NET ...
Slogans aren't solutions.
|
|
|
|
|
I is for Index was outside the bounds of the array
O is for Object reference not set to an instance of an object
|
|
|
|
|
P is for Possible mistaken empty statement
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
P is for P-complete
Q is for Quicksort
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
Way too advanced for most undergraduates!
veni bibi saltavi
|
|
|
|
|
|
|
If that was true, it should be compulsory watching before you are allowed to post a QA question...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The case for the prosectution
I couldn't even be bothered to put a comment on that one.
Is it time that some of these we're just deleted on arrival with an auto-reply of "sorry, no-one can help the helpless?"
Slogans aren't solutions.
|
|
|
|
|
I'm not sure about that one - I suspect that it's actually spam?
I've reported it in S&A to see what others think.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
After some thought:
PeejayAdams wrote: Is it time that some of these we're just deleted on arrival with an auto-reply of "sorry, no-one can help the helpless?"
No, I don't think so - I used to get irritated at the number of questions that were closed as "not a question" back when He Who Must Not Be Named was active here. Just because he didn't understand the question was not a good reason to leave a sarcastic remark and vote for it to close: somebody might understand it - that happened a lot to Bill and me. And it is damn annoying to spend half an hour typing up a solution to find the question is closed when you try to post it...
Asking questions is a skill: many, many people have never developed it. But it's one of the really important skills in development - it's not enough to go "it don't work" you have to ask "why didn't it work? What did it do? what evidence can I gather about how it failed?". You know that, you probably do it every day when your code doesn't do exactly what you expected.
And how are you going to learn a skill if every time you try to practice it, you get told "you are a hopeless case" and your question closed?
Instead, lets explain to these people that we need better info, and try to point them in the direction of how to ask a question. Improve them, and they might start to think on their own - yes, yes, I know that education systems, corporations, and many governments aren't interested in producing people that can think - and perhaps they can start to take our places as "the generation that knows what it is doing" instead of just being "the generation that was all copy'n'paste FarceBook Twatters".
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'd certainly agree with many of those points but I do think bad questions fall into certain groupings:
Group 1 - Lazyitis:
I want to write something to progressively map the changes in a series of MRI scans/predict stock market trends/work out the weather for next Christmas. What I have tried: Nothing.
I would advocate rejecting these mercilessly (if only to save Richard, NPC or yourself the trouble of a witty response).
Group 2 - "I'm not quite sure what's going on"
I'm trying to do x but I don't know the name of the concept and I'm struggling to explain what I'm asking. What I have tried: I've tried stuff but I'm getting nowhere.
Those, I would keep, as the poster obviously needs help but let them know that they're going to have to provide a few more details before they can get and maybe point them at some good beginner articles. These are maybe the sort that were treated too harshly in the past.
Group 3 - I CNT XPRZ MYSELFIE
These are a bit trickier because behind the complete lack of communications protocols (ESPECIALLY THE SHOUTING) there may or may not be a coherent and answerable question within. Obviously we have to factor in that not everyone is first-language English but maybe there should be a certain standard below which resubmission is requested.
I certainly don't advocate over-moderation - to me the beauty of Code Project is that it doesn't suffer from the same (often well-intended) Stack Overflow obsessions with requirements for this, that and the other. It's great to have a place where people can ask a question along the lines of "Can anyone see why this doesn't work?" without being required to accompany it with a dissertation or be made to feel inferior for daring to ask such a lowly question.
So, yes, generally I'd agree that CP should be the kind of nurturing environment that SO isn't but against that, there's a real danger that the QA just gets so full of bad Qs that no-one bothers to look at the As.
Slogans aren't solutions.
|
|
|
|
|
|
Name recalled in funky reggae collection (9)
Slogans aren't solutions.
|
|
|
|
|
|
Nope.
Slogans aren't solutions.
|
|
|
|
|
EASTEREGG?
Anagram of REGGAE SET and it's often a reminder who wrote the software?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
That's quite an ingenious wrong answer!
Slogans aren't solutions.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
