sarenji
As for watching through these glasses, they use a holographic display for the captions. Since they are projected directly onto the glasses, I learned very quickly to keep my head absolutely still so I could read the capions without getting motion sickness. The brightness and size are adjustable, which means you can choose from a bright green text and background or fainter levels of green. I'm not quite sure how the glasses receive the captions to be displayed, but it's via some sort of wireless technology. In the three theatres I've watched movies at with these glasses, they drop lines frequently, which is an exercise in frustration. I assume those two things are related. These glasses are hard to distribute -- each costs about $1,000, or so I hear. Not good if you run out and a deaf person needs to watch a movie, which has happened before.
Rear-view windows have similar problems, replacing wearing something uncomfortable on your face with wrestling against an adjustable mirror on a stalk. All in all, I'd say I enjoy open captioned movies in theatres the most -- where they display the captions directly in the movie.
A lot of my post outlines a struggle as I become more proactive. I'm leagues beyond what I used to be 3 years ago, but obviously I'm still not completely there.
I couldn't find any good/reputable speech therapists in SF, but I should have been more proactive on this. Do they have to be specifically deaf ones?
> At some point in time, I developed an ability to lip read and was able to speak without difficulty.
Can you expand on this, either on here or email? This seems like the most important part, especially as I'm not at that point.
2) My speech has never been a problem as my work understands me quite well. I perceived I had bigger things to deal with, like working on understanding what people say and getting up-to-date on stuff happening at work.
3) I have many Deaf friends back in college who I try to hang out with. I'm still learning sign language from them, and they've all been very helpful and supportive. Until I become proficient enough to actually participate in signed conversations, though, I still don't feel as if I belong.
By the way, me being more proactive is something I'm also working hard on :-) It's all a process.
Actually, you're right. Sometimes the girl I like is deaf, sometimes not. I should be fine with kids either way, and put in the work to make sure they develop right. I'm rethinking this entire paragraph. Perhaps I should have said I don't specifically search for a girl who is deaf, and then just left it at that, or just removed it entirely. Love is love.
Let me respectfully suggest that this is just untrue, a persistent myth about language learning. Hearing kids learn spoken language just fine, even if their parents don't use it.
Some (old) studies had suggested otherwise, but you made me remember the bilingualism argument, which is gaining traction. I do know that if you have a hearing child to both deaf parents, it's very important to expose the child to spoken language as much as possible. Of course, I hope I'm that kind of parent :-)
Bilingual kids do have a lot of advantages over kids who only know one language. I'd be very happy to teach my child, hearing or deaf, both sign and English.
Thanks for the insightful comment.
I also wanted to make it clear that I'm extremely thankful to my work for taking the chance to hire me. I love literally everyone here, even though, sometimes, I feel alone. Now, I'd consider all of them my friends. That's the basic sense I tried to get across with this post.
Namely -- Frank Rubin published a criticism of Dijkstra's letter in the March 1987 CACM where it appeared under the title 'GOTO Considered Harmful' Considered Harmful. The May 1987 CACM printed further replies, both for and against, under the title '"GOTO Considered Harmful" Considered Harmful' Considered Harmful?. Dijkstra's own response to this controversy was titled On a Somewhat Disappointing Correspondence.
:-)
Specifically the sayName function was created in the global scope, so when it came across the statement this.name it looks in the global scope for the value of name.
It doesn't matter where a function is created, but it matters how it's called. A pretty simple example is that typing sayHello() by itself desugars to sayHello.call(window);, where window is the global scope[1]. JavaScript function invocation is fairly confusing until you learn the rules.
I also really liked Yehuda's JS prototypes article[2]. It really helped me understand them.
[1]: Except in JS strict mode apparently? I don't know too much about that. See http://yehudakatz.com/2011/08/11/understanding-javascript-fu...
[2]: http://yehudakatz.com/2011/08/12/understanding-prototypes-in...
The solution was to implement a regex of whitelisted characters; since it's an English-only program, this works well and is future-safe. For multiple languages, a blacklist is probably okay, but the difficulty lies in keeping the blacklist both complete and up to date.
How did that happen?
I learned Cued Speech[1]. It's not mentioned anywhere in this article. It's a system that, summed up in a few words, uses signs for phonemes. Because of this, I could learn English within English. And when I took Spanish classes, I learned Spanish within Spanish.
I also dream in verbal words. Even after I learned ASL, I still dream verbally. The words are always quiet, a bit muffled -- this is how I heard things early in life, with hearing aids (I have a cochlear implant now). Occasionally I see captions, as if it's a TV show.
A last note. In the article it mentions little d and big D deaf; the way I learned it is that little d deaf people are deaf people in general, and big D deaf is the Deaf culture and community.
I did this every morning in high school. It also helps to immediately take a shower. I never understood why my peers would just go back to sleep and I didn't, but I suspect this is why.
I recently was interviewed by a co-founder of a startup for an internship position. He lives in San Francisco, I'm on the East Coast. We used Skype and he was very nice, very open to instant messaging. To code, we used an EtherPad clone. But it's difficult to convey your passion like this, because there are two inputs: video and text. It's hard to appear passionate visually while you're typing, so there's a kind of disconnect.
How I handle phones: I ask them if they can text, email, or instant message instead. Never did teleconferences, but they sound like a nightmare. For in-person stuff, my college provides me access services for free. I practiced like hell with approaching people, understanding spoken language with the cochlear implant (got it three years ago), and speaking accurately, so conversations are no longer the sweat-inducing terrors they used to be. It turns out that most people didn't care I was deaf.
Consider a VP (video phone). Acts just like a phone, but a middle-person interprets both ends of the conversation. Naturally, there is a lag between translations. Be sure to let them know.
If you have any personal questions don't hesitate to contact me (see profile). You aren't alone. If you hadn't made this thread, I would have myself when I make a startup.
"I made this letter longer than usual because I lack the time to make it short." -- Blaise Pascal
My friend and I used to laugh at this quote because we thought it wasn't true. Now we laugh because we know it is.
Is the problem lack of awareness? It takes much more effort to caption or transcribe videos and make websites screenreader friendly than to use valid HTML and CSS. But when I ask about making something accessible, people are usually happy to oblige. I suspect it's because suddenly they realize part of their target audience needs it.
The tiles are very familiar but I can't for the life of me remember which commercial game they are from. They're used a lot in indie games. A lot of sprites from the SNES era are. :)