[nfbcs] Advice for presentation - Pair Programming for blindand low vision developers
david hertweck
david.hertweck at sbcglobal.net
Fri Feb 19 01:09:08 UTC 2016
Now that I am off my phone and back to my computer, I would like to offer
the following.
First I have vision to see the location of the curser and the location of
the text but can not read the text.
Magnification only helps me with text location, I use JAWS for reading the
source code.
These things have worked for me.
1. pair programming
A. Each person works in the same room or at the same table using separate
workstations. In this way you can use the accessibility tool independently
from your partners. With JAWS I use an ear bud so my partner is not
bothered.
b. Divide the tasks up each person creats blocks of code and another person
combines the code.
c. When talking about code with your partner talk about it using line
numbers IE "line 109 I think needs to change"
D. For all sighted or not, paired programming works the best if all people
adhear to a common coding standered. This creates uniformed code making
comunication of ideas share a common base.
E. If in a larger group and code is displayed up on a large screen as in a
meeting room. Find a way to use your workstation and follow along with your
version of the code.
2. Code reviews
a. most of the compare / diff software packages I have used are user
configurable to sho the dif in different ways. If you can not see colors
maybe you can use colors that appear to you as different shades. Another
idea if you can see fonts have the dif display in different fonts.
B. Review the code changes before meeting and take notes ahead of time. IE
if you review the code and you see a problem or have questions take a note
and then bring these things up at the meeting.
C. we did large group code reviews for years but found individual code
reviews followed by a meeting is much more affective in finding problems.
D. another tool you can use to help in code reviews is a static code
analysis package, the results of this analysis can then be reviewed at the
meeting. I have found these tool to be accessable.
-----Original Message-----
From: David Hertweck via nfbcs
Sent: Thursday, February 18, 2016 3:00 PM
To: NFB in Computer Science Mailing List
Cc: david.hertweck at sbcglobal.net
Subject: Re: [nfbcs] Advice for presentation - Pair Programming for blindand
low vision developers
I am a blind so fringe near that has been working professionally for the
last 20 years. I have done paired programming, code reviews, etc. Would be
happy to discuss methods are used with you. Please send me your email
address or phone number would be happy to talk.
Or you could give me a call at 314-537-6851.
Sent from my iPhone
> On Feb 18, 2016, at 12:26 PM, Suzanne Germano via nfbcs <nfbcs at nfbnet.org>
> wrote:
>
> I am legally blind and recently graduated from ASU with my BS in Computer
> Science. About one month ago I started my new positions as a Software
> Developer/Integrator at USAA.
>
> They are working on making the entire company Agile and want to get into
> much more pair programming.
>
> What techniques have you used in pair programming?
>
> I will be proposing a talk for the Grace Hopper Celebration of Women in
> Computing on the topic of how to effectively accommodate a blind or low
> vision developer on your team. So I welcome everyone's input on what works
> for you and what you would like to see implemented.
>
> So far I have found pair programming very difficult.
>
> I have enough vision that I use 2 27 inch monitors with ZoomText an have
> my
> IDE span the two monitors. If I am the one running the mouse and keyboard
> then it is fine. I cannot work at any of my teammates workstations as they
> work in regular size. Not only that, I am extremely light sensitive so I
> would not be able to read theirs even if magnified. I am currently in
> training, so one solution we use at times is a 55 inch monitor but I have
> to stand up right against it and still can't see the top or far side. We
> also do team code reviews on a monitor mounted on a wall so I am trying to
> figure out solutions for that and the fact the code review software uses
> color and I am completely color blind.
>
> Thank you for all ideas and advice!!!
> _______________________________________________
> nfbcs mailing list
> nfbcs at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> nfbcs:
> http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/david.hertweck%40sbcglobal.net
_______________________________________________
nfbcs mailing list
nfbcs at nfbnet.org
http://nfbnet.org/mailman/listinfo/nfbcs_nfbnet.org
To unsubscribe, change your list options or get your account info for nfbcs:
http://nfbnet.org/mailman/options/nfbcs_nfbnet.org/david.hertweck%40sbcglobal.net
More information about the NFBCS
mailing list