4 ms·
Blind software engineer here. Sorry to hear about your eyesight issues, dealing with that is always hard, but the good news is that there is life here. I've bee
by mltony 8y ago
Blind software engineer here.
Sorry to hear about your eyesight issues, dealing with that is always hard, but the good news is that there is life here. I've been working on a bunch of open source projects and recently I found a full time job as developer. I know almost a dozen blind software developers working in big IT companies.
Let me introduce you to the tools you can use. There are basically two types of tools: screen magnifiers for those with low vision and screenreaders for those who don't have any usable vision. Judging by your description, you might want to start with a magnifier. In the unfortunate case if your vision keeps getting worse, you can consider switching to a screenereader. Magnifiers are obviously easier to learn, but you can write code and do all the good stuff with screenreaders too.
I am not that familiar with Magnifiers, but I've heard that the most popular one is called ZoomText and it is for Windows. Macs have their own magnifier, not sure about Linux.
In the world of screenreaders you have NVDA and JAWS for Windows, VoiceOver for Mac, ORCA for Linux and also EmacsSpeak, which is an accessibility extension for Emacs. You can also use phones with screenreader: there is VoiceOver for iPhone and TalkBack for android.
One suggestion is try to find an organisation in your country that deals with blind and low-vision people - ask your eye doctor if he knows any - they might be very useful in your situation as they can recommend a lot of tools and resources specific for your country, such as white cane trainig, if you need it, guide dogs, braille training, they can also probably teach you how to use screenreaders and magnifiers.
Feel free to contact me if you have any more questions: anton <dot> malykh <at> gmail. And good luck!
- therein 8y ago> Sorry to hear about your eyesight issues, dealing with that is always hard, but the good news is that there is life here. You're awesome. Reading this made me tear up a little bit. There were a few blind software engineers at my previous workplace and I've always found it admirable. I wish you all the best. As a software engineer, one of my greatest fears is losing my eyesight. I am currently not showing any signs of macular degeneration but having had LASIK, I am under increased risk of that happening. Had I known more, I would have kept my cornea intact. Now I feel slightly worried whenever I have problems focusing on text at night or getting blurry vision for a brief moment on occasion when I blink as these might be early signs.
- ndarilek 8y agoBlind developer/sysadmin here as well. I completely agree with the above comment, and would add to it: I'm not sure what platform you currently use, but if not Windows, you're in for some challenges if you're blind or visually-impaired. I'm currently using Linux because I'm a console-based developer (I mean, I still use Firefox and the GUI but run most dev tools from the console.) This generally works well enough for me until I need an IDE, because my current codebase is C#/CSHTML/JavaScript/HTML/CSS/TypeScript, and I can't juggle all that state in my head without something like an IDE to help out. And, as far as I know, there's nothing like that available and accessible for Linux. My hope is that VSCode can help a bit, but Electron apps are currently inaccessible under Linux, which rules out a whole bunch of traditionally useful tools (No "Electron is bloated" arguments here please, this is something else entirely.) Unless you're a Linux user who uses mostly GTK-Gecko-based tools and the console, and those GTK-based tools don't use crazy custom widgets, you can make Linux work. But QT is challenging, Electron is out, and Chromium/Chrome are inaccessible (though I hear that is changing soon.) Windows offers lots more tooling, plus access to Electron apps, which opens up many more possibilities for non-console-based development. But anyway, if you can at all transition your workflow to Windows before things get more challenging, I think you'll be in a better place. I'm about to ditch Linux soon, but for a high-end PC which will run VMs for anything I might need. Running a pile of VMs is probably the best solution to this issue, but second best would almost certainly be Windows. MacOS and Linux trail behind, unfortunately. I also wish you good luck. Happy to chat if I can help more. nolan at thewordnerd dot info
- _asummers 8y agoI've heard iOS is generally good towards people with visual impairments. Do you have experience with iOS/OSX and are you able to comment on their friendliness?
- forthewyn 8y agoOSX has been an accessibility leader for a very long time. However recently everybody else has been catching up. I was away from Linux and Windows for 10 years because neither provided key chorded full screen zoom by default and now they do. So, in short, accessibility support in OSX is good, but no longer best in breed, so choose the OS you're most comfortable with generally. IOS accessibility is excellent. Screen zoom, VoiceOver, high contrast, etc.
- andrewfong 8y agoI would toss in one other note about OS X. Consider enabling the "Speak Selection" or highlight-to-speak option. As the name implies, it reads selected text aloud. My wife is low vision but not so much that she needs a full screenreader. Voiceover is overkill for her and has a steep learning / adjustment curve. Highlight-to-speak has been good enough thus far.
- mhuffman 8y agoI have a serious question to ask you. Do blind software engineers work exclusively on systems-type applications or does there exist technology for blind developers to create UIs?
- jareds 8y agoI'm a blind developer and my job is all back-end database and REST api development. I have done UI development on internal applications where function mattered more then looks. It's pretty easy to create basic UI's using HTML since everything is in code. Specifically I used Grails to generate UI scaffolding as a starting point that I was then able to modify. Once I got everything working another developer spent a day adding some CSS and fixing a few rough edges.
- mltony 8y agoI mostly work in the backends, but I wrote a few UIs too. Either in HTML/PHP, or in wxPython. I can probably write UIs in other languages/technologies too if I had to. They probably don't look very nice, but they are functional. Every now and then something would glitch and all my buttons would end up one of top of the other or something like that, so I'd ask someone sighted to check for that.