It depends on what the code is. If I'm working on writing unit tests for relatively simple code taht didn't have any tests when it was origionally written I can do 30 hours a week with out to much trouble. If I'm doing new development for non-trivial features I generally can't get 30 hours in unless I get lucky and get in the flow several days during the week.
I created an itunes account for my daughter when she was two months old. The phone stays on a charger in her room and is used for nothing but playing apple music when she's sleeping.
Thanks for linking to that comment. I'm glad to know I'm not the only blind person who doesn't understand how I don't get into a fatal car accident at least once a week.
I'm a totally blind programmer who saw this start to develop based on email list postings. As far as I remember originally the plan was to make Netbeans more accessible with screen reading software. This was done by creating Sodbeans,
https://sourceforge.net/projects/sodbeans/
I tried it out several years ago, and didn't find it to be worth using. By that point I was already quite comfortable with Eclipse, and Netbeans/Sodbeans didn't offer anything to make it worth switching. After working on Sodbeans I guess the researchers decided that they could only do so much to make Netbeans accessible so created a new language. By that point I was already a fairly experienced programmer, so lost any interest since I didn't see the point in learning a new language created at least partially based on the needs of blind programmers that I would most likely never use professionally. I don't have any opinion on whether this is useful since I taught my self to program using GW Basic 20 years ago so have no idea how someone who is blind would go about learning programming in 2018 with current technology.
Several reasons.
1. If you live in a terminal it's easier to stay in that terminal instead of switching to a new window to deal with your task manager, then switching back to your terminal.
2. It's quicker to type one command with all it's options instead of using a GUI and selecting multiple options.
3. IN my case as a blind programmer I find it easier to use as many command-line tools as possible instead of dealing with possible accessibility issues in a GUI.
I've been working on Mainframes for the passed 8 years full time, and several internships before that. I often go several days with out needing to use ISPF. I use
https://compuware.com/workbench-mainframe-modernization/
for dataset editing, job submission, etc. I find the Unix shell you access through ISPF to be very difficult to use. Luckily SSH is available on z/OS, so if I need to do Unix stuff I can just SSH in with the client of my choice.
The biggest difficulty I had when getting started was understanding JCL. I had come from a Linux background, so was used to executing commands with arbitrary file names, looping, etc. It took me a while to understand how JCL worked. Once I understood that you have to define datasets with things such as space allocation and disposition before using them, and that JCL was a series of sequential steps with the output from a prior step available to a later step a switch flipped and I went from struggling with JCL to fairly comfortable in a couple days. I'm not sure how much of this was the fact that I was an intern at the time so didn't have a lot of programming experience and how much of it is the platform. I find that once you get comfortable with the basics of JCL the structure it forces you into actually makes it easier, even though it is limiting in some ways.
The issue I still have with the Mainframe is documentation. Unlike most programming questions a google search does not turn up Stackoverflow results. I find I spend a lot of time going through random forums or reading the IBM doc. I don't find IBM doc easy to understand, but the more I have to deal with it the easier it gets.
At least with my work Java EE 6 and WebSphere 8 brought pretty decent annotation support. WebSphere Liberty looked pretty nice from the little I used it, but that was several years ago.
We are no longer living in the days of EJB 2 and Websphere 6. Springboot allows you to get started quickly with out spending a week configuring your app server and Java beans. The article should have been titled "Using enterprise Java technology from 15 years ago will kill your startup. PHP will save it."
1 reason I should stick with windows. I've never gotten Linux screen reading software to run properly in a virtual machine. About once year I grab the latest Fedora or Ubuntu distro, fire up Virtualbox, and install Linux. Then I reboot and speech will randomly die on me when using Orca. My Windows 10 insiders VM just works with both Narrator and NVDA screen reading software. To point 4 in the article I've found Chocolatey to be quite nice. While it's obvious that it's grabbing installers and running them as best as it can with Command-Line options instead of distro supported software updates it's better then the alternative of manually checking for updates or stopping what I'm doing to install an update when software prompts me.
It's been about a year since I did my last Linux install so if anyone has experience with something that is accessible let me know. While Linux may work better on physical hardware instead of a VM I only have a Desktop that I don't feel like duel booting since it also acts as kind of a home server.
I'm totally blind so I'd trust the call center employee more then my self. I'd love to have a self driving car that could get me where I wanted to go 99% of the time, as long as the 1% failure mode aborted the trip and sent me back home with out killing me. Something like a call center employee turning the car around and sending me home if the weather was going to be to snowy to make the trip would be life changing for me. Uber and Lift are useful, but not cost effective for daily commuting.
Articles like this make me worried about my future as a blind programmer. I enjoy back-end database and web services development, not accessibility work. A lot of the I'm a blind programmer articles I've scene appear to be blind developers who work on accessibility. I hope they work on accessibility do to interest not because everyone assumes if you a blind programmer accessibility must be the type of work you want to do.
I bought Jaws 15 years ago before NVDA was out. Because of this it doesn't cost me $1000 to keep using it, it costs me $200 every two years to keep up to date. IT's the only software I know of that offers good 3270 emulator support using third party scripts someone wrote. While it may be possible to make NVDA behave similarly with python scripting it would take more then $200 worth of my time since I'm not a Python programmer. Since I rely on it for my job it's also comforting to know I can call up someone and get help or open a support ticket if something is broken. I have not had to do this recently, but I remember calling up when I switched from office 2003 to 2007 at work because the UI was so different I wasn't sure if I was having accessibility issues or not. Support was helpful and had me working in under 10 minutes.
What do you use instead of Slack? I'm a blind developer and find it usable enough, but I'm also on a fairly small team with out a tun of slack traffic.
Depending on how complicated your spreadsheet is yes. I enter my fixed expenses a month ahead of time. I can then see how much money I expect to have on a given date with something like
ledger -e 2017-12-15 bal checking
If it's true that touch id was expected to ship until a couple months ago they may not have found an alternative. If they are expecting touch id to be in next years model I could see them not making face unlock accessible since you can still get new iPhones with touch id. Remember Apple did not make the iPhone accessible until the 3gs, so there's no guarantee that new features will be accessible.
I'm not sure. It was truly bad in the Android 2.3 days. I own a Moto E since it was cheep and I was curious if Android had improved. Running 5.1 was pretty accessible, but was slow which is expected since it's a low end phone. Android apps on a chromebook work pretty well, but who knows how that will translate to a modern mid range Android phone.
I'll be surprised if this works for me as a blind person. There's no way I could directly look at the camera. I don't need the iPhone X since I don't care about camera quality, but if touch id starts being removed from all new iphones I will be giving Android a long hard look.
I haven't had a chance to actually run through the tutorial but looking at it I don't think I'll have problems following it. It's well written and the graphics are not required to understand what's going on.
The site appears to generally be accessible with the exception of the interactive tutorial. I'm not a web accessibility expert so don't know the details. There are two major issues. The biggest one is my inability to arrow through the code in an edit field. I can read the text outside of the edit field, but it's difficult since line numbers are interspersed with the text. My assumption is that your using an open source editor which is inaccessible, but I have not had the time to look at the tutorial on Github. The second issue is that there are buttons that my screen reader reads as "button". While run, edit, and format are read properly several other buttons are not.
I have not found an introduction tutorial that assumes you go from no iOS knowledge to a working app with just code instead of storyboards. DO you know of a tutorial that does this?
I’m totally blind and bought a Mac several years ago hoping to learn iOS programming. As far as I can tell it’s impossible to create a simple app without using drag and drop in XCode. While it’s technically possible to do drag and drop with Voiceover I can never get it to work correctly. Apple has not put out any documentation on how to use XCode when blind that I’ve been able to find. This is disappointing since I find iOS to be much easier to use then Android. I also find Voiceover on the mac does not have quite as many shortcut keys as my Windows screen reader when reading the web, for example I cannot jump to a heading at a specific level or move by region. While Mac OS did have easy availability of Unix tools as a plus that no longer is a point in its favor. I find WSL to be quite good and accessible. Luckily the 11 inch MacBook Air was the best ultra-book I could get at the time so I don’t feel like I wasted my money even though I boot into Windows 95% of the time.
For general use Mac OSX is pretty good. I find the screen reader to be quite intuitive and there is a good tutorial to help you learn it. Voiceover just doesn’t have the breadth of shortcut keys or customizability of Jaws for Windows which is my preferred screen reader despite its cost.
I'm a blind developer and I've found Windows 10 to be pretty good about not throwing up popups if you configure it well. This is because we have a good IT group who builds machines from scratch so there's no trial software. I build my personal computers from scratch so install the OS avoiding junk software. When Windows does have notifications it's pretty good about putting them in the notification center so I can look at them when I want instead of having to deal with an notification dialog right away.
I had the IT group find me an old external monitor. Although I don't need it it's much easier to have the screen at eye height when a co-worker is standing then requiring them to hunch over and look at a 13 inch laptop screen.
If you want to develop iOS apps you need a mac. You should get the 27 inch iMac with 64 gigs of ram. This will be a lot more then $2000. If you don't need to develop iOS apps then ryzen looks like it could be good.