All Your VMK Are Belong to Us

[darkacre]

It must not be worth going back and fixing, but now that I'm playing Hyperspace Mountain again, I find myself cracking up about how your recharge generates that message saying

"Your are completely refuled."

Everyone makes typos from time to time, but shouldn't this one be fixed at some point?

 

[Loves Disney]

It's a free game, how much class can it have? heh, I don't think anything in this game should have typos though...are they not allowed to check over what they did before they submit to the offical game? Can they not make sure everything is spelled correctly before they send it out for thousands of people to view?

lol or maybe, they aimed it to say "your"...

 

[Goofy05]

And just think...those are spelling typos of text we see. Can you imagine what typos would do to programming code?

 

[Disney Dreams]

But the real quiestion is - how long till it is now fixed?

 

[qruthie]

And just think...those are spelling typos of text we see. Can you imagine what typos would do to programming code?

They usually generate syntax errors. Sometimes they generate semantic errors. In some cases they slip through all that checking and result in what we call a bug. In the worst cases they slip through all that checking and result in what we call a crash.

Which brings up the ethical question, should I add bugs to my code to increase my job security? The answer seems to be no because enough bugs are added anyway.

 

[dippydawg]

They usually generate syntax errors. Sometimes they generate semantic errors. In some cases they slip through all that checking and result in what we call a bug. In the worst cases they slip through all that checking and result in what we call a crash.

It's a bug from a user's standpoint.

From a developer's standpoint, it's a bonus feature.

"What? You didn't want the program to go into an infinite loop and eat up all the CPU? Oh. Sorry."

 

[qruthie]

It's a bug from a user's standpoint.

From a developer's standpoint, it's a bonus feature.

"What? You didn't want the program to go into an infinite loop and eat up all the CPU? Oh. Sorry."

Oh so true! The downside is, when you change the "feature" there is always at least one customer who immediately complains because you just broke their application.

Then there's my favorite comment to find in the code, usually in the "else" part of an "if" statment, "You should never get here." and the programmer didn't bother to write any code. It's always in an error handler and of course you get there! One place I worked for had a, "Fatal error contact your (name of company removed) sales representative." Not the support department, your sales rep! I guess the error was so bad your best bet was to replace the software!