6 ms·

I'm a totally blind developer and I find the easiest way to do code reviews is to use git format-patch on the branch containing the code. I read the patch files

by jareds 7y ago

I'm a totally blind developer and I find the easiest way to do code reviews is to use git format-patch on the branch containing the code. I read the patch files in a text editor. Perhaps comments in the pull request referencing a commit and line would allow the developer to get the required context from the patch files?

fernandotakai 7y ago
i hope this is not an intrusive question -- but how do you usually write code? with a screen reader?
- jareds 7y ago
  Yes, I use Jaws for Windows. I also make heavy use of WSL for command-line stuff.
  - randomvectors 7y ago
    Kudos to you. Speaking as someone who has taken their eyesight for granted, it's absolutely incredible that anyone can do this at all.
    - skyyler 7y ago
      How patronizing.
      - mpoteat 7y ago
        What did you find patronizing about the statement?
  - murph-almighty 7y ago
    Maybe I'm mistaking you for someone else but did you write a blog post about this?
  - stallmanite 7y ago
    I have always wondered about this and I hope you wont mind one more question: For me being able to see as much on a page as possible really aids me. For you to get a piece of code into your mind it seems like you’d have to have really sharp memory to store the relevant items in working memory as the screen reader recites the code one word/token at a time. Am I missing something or do you simply overcome this with badass memory skills?
    - rjbwork 7y ago
      I've seen a blind programmer code before. His screen reader tool was set to go REALLY fast, and so to me it sounded like tiny short rapid fire bursts of audio but to him, he was getting like hundreds of characters per minute or more of context.
      - stallmanite 7y ago
        That makes sense. Thanks for the explanation.
      - StavrosK 7y ago
        I had a blind coworker. I was really jealous when he connected a Raspberry Pi to a power bank on the airplane, connected his headphones and a keyboard and started working in the cramped seat that wouldn't fit a screen. Seems like a very nifty way to work and you can just keep your computer in your pocket. And yes, the screen reader went super fast. I had trouble following it but I think that's mostly because I wasn't expecting what it was doing, whereas he was controlling the cursor so he knew more or less what he was hearing.
        Forge36 7y ago
        I program for accessibility, having used JAWS it can go FAST. Having observed a blind user: it's entirely a skill you practice, some people in the room could follow along, others were lost. I encourage you to try it if only to test your development.
  - faissaloo 7y ago
    When you get a new computer how does setup go? Do you have some shortcuts memorised that you use as soon as it boots or something?
    - mwcampbell 7y ago
      Windows and macOS each have a built-in screen reader with a standard keyboard shortcut to turn it on. On Windows 10 version 1703 and later, you can turn on Narrator with Control+Windows+Enter. On macOS, you can turn on VoiceOver with Command+F5. I think it's fair to say that most blind Windows users still use a third-party Windows screen reader. But at least they can use Narrator to get through the setup process and install their preferred screen reader.
      - jareds 7y ago
        In fairness to Microsoft they have been doing a lot of work with Narrator. I am posting this reply using it with Chrome on a windows insider build.
keufran 7y ago
OK. Thank for the tip, we will try.
sadlion 7y ago
It's tangentially related but I have always wondered how different programming languages, frameworks, and developer tools faired when evaluated against ADA. Are there any you find easier to work with and what should we be mindful about to make them easier?
- emdd 7y ago
  As long as the tools and programs are WCAG/508-compliant, it should be good to go. Common to use Braille Readers or screen readers. I’d be curious if certain syntaxes are easier than others.

by jareds 7y ago

fernandotakai 7y ago

i hope this is not an intrusive question -- but how do you usually write code? with a screen reader?

jareds 7y ago
Yes, I use Jaws for Windows. I also make heavy use of WSL for command-line stuff.
- randomvectors 7y ago
  Kudos to you. Speaking as someone who has taken their eyesight for granted, it's absolutely incredible that anyone can do this at all.
  - skyyler 7y ago
    How patronizing.
    - mpoteat 7y ago
      What did you find patronizing about the statement?
- murph-almighty 7y ago
  Maybe I'm mistaking you for someone else but did you write a blog post about this?
- stallmanite 7y ago
  I have always wondered about this and I hope you wont mind one more question: For me being able to see as much on a page as possible really aids me. For you to get a piece of code into your mind it seems like you’d have to have really sharp memory to store the relevant items in working memory as the screen reader recites the code one word/token at a time. Am I missing something or do you simply overcome this with badass memory skills?
  - rjbwork 7y ago
    I've seen a blind programmer code before. His screen reader tool was set to go REALLY fast, and so to me it sounded like tiny short rapid fire bursts of audio but to him, he was getting like hundreds of characters per minute or more of context.
    - stallmanite 7y ago
      That makes sense. Thanks for the explanation.
    - StavrosK 7y ago
      I had a blind coworker. I was really jealous when he connected a Raspberry Pi to a power bank on the airplane, connected his headphones and a keyboard and started working in the cramped seat that wouldn't fit a screen. Seems like a very nifty way to work and you can just keep your computer in your pocket. And yes, the screen reader went super fast. I had trouble following it but I think that's mostly because I wasn't expecting what it was doing, whereas he was controlling the cursor so he knew more or less what he was hearing.
      - Forge36 7y ago
        I program for accessibility, having used JAWS it can go FAST. Having observed a blind user: it's entirely a skill you practice, some people in the room could follow along, others were lost. I encourage you to try it if only to test your development.
- faissaloo 7y ago
  When you get a new computer how does setup go? Do you have some shortcuts memorised that you use as soon as it boots or something?
  - mwcampbell 7y ago
    Windows and macOS each have a built-in screen reader with a standard keyboard shortcut to turn it on. On Windows 10 version 1703 and later, you can turn on Narrator with Control+Windows+Enter. On macOS, you can turn on VoiceOver with Command+F5. I think it's fair to say that most blind Windows users still use a third-party Windows screen reader. But at least they can use Narrator to get through the setup process and install their preferred screen reader.
    - jareds 7y ago
      In fairness to Microsoft they have been doing a lot of work with Narrator. I am posting this reply using it with Chrome on a windows insider build.

keufran 7y ago

OK. Thank for the tip, we will try.

sadlion 7y ago

It's tangentially related but I have always wondered how different programming languages, frameworks, and developer tools faired when evaluated against ADA. Are there any you find easier to work with and what should we be mindful about to make them easier?

emdd 7y ago
As long as the tools and programs are WCAG/508-compliant, it should be good to go. Common to use Braille Readers or screen readers. I’d be curious if certain syntaxes are easier than others.