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

Once an interviewer asked me, how would you design a telephone for blind people and is there something already on our phones today for it. My answer was short, i said "Braille". He turned the landline phone towards me and asked to take a look. The middle keys sometimes have this bevel shape(just like a keyboard). Since i'd already said braille, i thought he meant something else now. I said i don't know.

He's like 'notice the small bevel at the bottom of the center key". Apparently he didn't know what it was called and that it was named after the inventor. Well, technically it's not proper Braille, but i would have taken that as a correct answer.



Is it Braille? Isn't it just designating the center key in a number pad (the '5'), from which it is evident to the user what the key around are? There is a slight bump on my '5' key, but one bump is certainly not Braille for '5'. Braille is like Morse code, it refers to a specific 'code', not just "any bumps meant to be felt for".


>Well, technically it's not proper Braille, but i would have taken that as a correct answer.

I just wanted to highlight that even though the candidate/me was aware of the basic concept. The answer just wasn't the exact thing the interviewer was looking for, hence it was wrong according to him.


I can't tell what your interviewer knew or intended, but the point of the question it seems to me is the "one non-Braille bump on the '5'" solution is actually better and simpler than using actual Braille. So answering Braille actually does seem wrong to me, and insisting it's not wrong seems like missing the point. You had generalized Braille to mean any bumps, so maybe your interviewer knew what Braille was, and that this was not Braille, and thought the point of the question was specifically that it was not Braille.




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

Search: