In middle school we were reading "House on Mango Street" horrible horrible novel, but because it was multi cultural we got that shit shoved into us. Anyways a girl in my class wrote "Latino Praide" on several of the novels.

retwitting Romney typo: Amercia instead of America. Obama typo: Kenya instead of Hawaii.

I hope Romney fired the designer who cranked out that app without catching the typo. That's unforgivable. The IT industry is full of tech wizzes who don't don't proofread their work.

It's odd too, because source code will not run if anything in it is misspelled. But content? Who cares, right?

It's odd too, because source code will not run if anything in it is misspelled.

The code will run, if the misspellling is consistent.

Bad Spellers of the World, Untie!

This tired old joke is funny for me today because earlier I was creating a spreadsheet with sales data by region and comparing it to the whole US market. The header I initially put in for the whole US market was "Untied States."

It's odd too, because source code will not run if anything in it is misspelled. But content? Who cares, right? -- carol at May 31, 2012 1:37 PM

Have to agree with Steve. With the intellisense and similar functions, coding mistakes can work.

For instance I had misspelled a variable @FacilityID as @FacilitityID last night. Because of the intellisense it was riddled through my code. Once I caught it, a simple search and replace fixed it. I also had a remark that said "put the cusomer name here". Luckily no customer will ever see it.

But anything the end user will see, I have someone else proofread it.