You can definitely continue as a software engineer. I'm living proof. It won't be easy, especially at first. For a while it will feel like you're working twice as hard just to keep up with your sighted peers. But eventually, the better you get with your tools, you'll find you have some superpowers over your sighted peers. For example, as you get better with a screen reader, you'll be bumping the speech rate up to 1.7…
> You'll be amazed how good your memory will get without the crutch of sight That's all really interesting. I personally have a problem with my thoughts in that I need to "sound out" or read them aloud in my head. This sometimes really slows me down, I mull over a thought until it sounds right. Especially when I'm tired I can get stuck in a loop. And it applies when reading too, I can force myself to read faster but…
Ask HN: I'm a software engineer going blind, how should I prepare?
161–170 of 497 posts
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#162You can definitely continue as a software engineer. I'm living proof. It won't be easy, especially at first. For a while it will feel like you're working twice as hard just to keep up with your sighted peers. But eventually, the better you get with your tools, you'll find you have some superpowers over your sighted peers. For example, as you get better with a screen reader, you'll be bumping the speech rate up to 1.7…
> you'll be bumping the speech rate up to 1.75-2X normal speech. You'll be the only one who can understand your screen reader Huh. I already listen to most podcasts and recorded presentations at 2x. Now you make me wonder if I could process information faster with a screen reader even though my sight works just fine...
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#1631. Emacspeak, a text-to-speech system developed by T.V. Raman (a developer at Google) who was blind since childhood: https://en.wikipedia.org/wiki/Emacspeak & https://en.wikipedia.org/wiki/T._V._Raman
2. How a completely blind dev/manager uses Emacs daily (talk at a recent Emacsconf) -- https://www.youtube.com/watch?v=i8dBvssptP0 & https://www.parhamdoustdar.com/2016/04/03/tools-of-blind-pro...
3. Google has an app called "Lookout" which they suggest using while wearing your phone attached to a lanyard around your neck, that uses ML (not fully perfect) to identify objects in front of you.
To the extent that you stay within some homogeneous environment and avoid fragmentation in your tools, you might be able to get good text-to-speech. (The quality of AI solutions will hopefully continue improving drastically over the next few years)
Also, probably experiment with and invest into one of the software ecosystems (Google/Apple/Amazon/etc) so they get comfortable with understanding your voice.
You probably want to avoid the mouse, and get comfortable with a fully keyboard based workflow. To that end, check out browsers like Qute and Next.
----
Beyond software and tools, would you want to relocate to some place where there is dependable public transport (or cab service)? Once you move, it might take a while to get familiar with the surroundings.
Good luck, and hope you manage to stay ahead of the curve. I'm sure finding community would help. Try reaching out to some of the people mentioned in this and other comments -- I'm sure they would love to help.
----
PS, HN'ers: It would be great to find a few interviews with accessibility-oriented guidance on "Usesthis". To that end, I've opened a Github issue with this request. Feel free to comment there and add suggestions of people to interview, or other recommendations https://github.com/waferbaby/usesthis/issues/97
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#164Earlier quoted context omitted.
Your comment about proof reading and errors not sounding right reminds me of the "proper/best" way to learn Morse code for ham radio. Most everyone is familiar with the charts that show A=.- B=-... etc. Lots of beginners try to actually interpret the sounds in their ears and convert that to a letter and then convert a bunch of those to a word. Obviously, that is very processor intensive and has a high failure rate. T…
Similar experience for when I taught myself the Dvorak layout years ago. My fingers learned the common motion for whole words first. Actually, I'm not sure I could draw the layout of the qwerty keyboard I'm typing on right now from memory either.
Obviously it’s just practice but I don’t mind using qwerty on my phone. It keeps it vaguely present in my memory.
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#165Earlier quoted context omitted.
Meat of your comment to me is this phrase, “he had this insight about the balance between when to use hardware and when to use software that I think is somewhat lacking today” - would you attempt to clarify what you’re expressing he would have said about balancing the design of how software & hardware work together? Thanks.
I'm interested in hearing more about that as well.
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#166My immediate advice to you as an engineer is to remember that your most powerful and valuable tool is your mind. The ability to solve software engineering problems starts with the cognitive aspects of your knowledge, intuition, experience and who you are. An engineer's cognitive ability to solve problems and guide outcomes is the most valuable thing that we bring to any project we join or undertake.
Look for a team or project that values critical thinking to drive execution over just banging out code. Don't sweat being hands on in the long run, i.e. writing code and pushing features. Make the most of the work you're doing now to start honing your skills to be able to drive things like architecture, implementation choices, etc. based on experience, lessons learned, people you enjoy working with etc.
Also, keep in mind that you have a unique albeit unfortunate set of circumstances that can bring a perspective as you're going through this to what works and doesn't for others in similar circumstances that want to have careers in software technology. Be open to an awareness for areas where you can help solve problems and be involved in building solutions for others in a similar circumstance as you're in. Look for ways to develop products, tools, advisory groups, training, etc. that can help engineers with similar disabilities.
I wish you the best and again, I'm very sorry you're facing this. I hope that my thoughts help in some way.
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#167First, in college I knew a guy with RP. He was hands-down the most brilliant coder I knew at the time. Aside from blowing up the screen (screenreaders did not yet exist), he ended up simply memorizing his code. He held the whole thing in his head.
I also knew -- internet-only -- a woman with the more severe form of Usher's (born deaf, go blind) -- who was quite techy even in the early 1990s and now works doing tech stuff for libraries, last I checked. She, also, had it going on.
In short, I can tell you this: other people have done it, so you also have a shot at it.
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#168I have just the visual component of Ushers, I’ve got about 5 degrees left of my visual field. I never really did front end work, but I still regularly do back end, and project management. I haven’t moved to non visual coding yet. Instead I have optimized for the vision I have left. I have a very bright monitor, very bright lights in my office (overhead) and have learned to make a place for everything, and always put…
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#169You can definitely continue as a software engineer. I'm living proof. It won't be easy, especially at first. For a while it will feel like you're working twice as hard just to keep up with your sighted peers. But eventually, the better you get with your tools, you'll find you have some superpowers over your sighted peers. For example, as you get better with a screen reader, you'll be bumping the speech rate up to 1.7…
> Also, because code is no longer represented visually as blocks, you'll find you're building an increasingly detailed memory model of your code. does refactoring by other team members have an outsized negative effect on this?
Re: Ask HN: I'm a software engineer going blind, how should I prepare?
#170Earlier quoted context omitted.
This person is sharing personal information about a serious disease and disability in their life and asking for help. But thanks for taking the time to share how superhuman you are.
Personal attacks will get you banned here, so please don't do that, even if another comment rubs you the wrong way. https://news.ycombinator.com/newsguidelines.html