Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm curious. How do you handle typos in code? Say you're working on a team, and they've got a lot of foreign devs who mis-spell words like color with o u r.

Or they just mistype something and leave it... but your screenreader reads it and you hear/know how to spell it so you introduce bugs because you're using correct or localized spellings of a variable name when everywhere else in the code uses the incorrect or other-localized version?



It isn't a mis-spell. Color is used primarily in U. S. Rest of the English speaking world uses colour.


yeah but my point being if half the team is uk and half is U.S. and you have a blind programmer on each team.

You could see where there could be some major nomenclature issues.

Of course a good design policy could help, but someone still can mis-spell something, or even just caps in the wrong place.

Someone might make: const Sidebar and someone else calls it SideBar.

My main question is how do blind programmers deal w/ these sort of issues, I think that would be the hardest thing not being able to see.

Hell, I've mis-spelled something before and took me awhile to figure out that was what was breaking things.

Of course maybe using statically typed languages and things could help.

I'm sure their also tooling I'm unaware of, but definitely curious how they navigate these type of scenarios.


I once inherited code written in Spanish and I knew just enough to figure out how to maintain it. Definitely slowed me down a ton but I learned more of a real language while coding! I wouldn't recommend it though for any serious application haha. Back in the day it was on Flash and classic ASP which were both new to me too. Back then you didn't handpick your projects. You just took them and figured them out. I'd attribute a lot of my success from plunging into those types of things.


Yeah, I worked a lot on software written by russians, ukrainiens and chinese; basically the software has no usable comments for me (translation software was not helpful back then) and a lot of variable and method names were wrongly spelled english or ascii (not cyrillic etc) written russsian etc. It had a solid feeling of being obfuscated code a lot of the time. Fun times.


It’s reasonable to standardise on a flavour of English that you want your code and comments to be written in. For some teams, that’ll be US English and all developers should be expected to abide by that standardisation. For other teams it’ll be British English and US developers would be expected to meet the common coding standard too.


Screen readers are modal and I believe e.g. JAWS has a character-by-character mode to spell out the character that's under the cursor. Aside from that, from what I saw in a conference presentation, sight impaired users can use tools like Intellisense.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: