I’m doing the CodeYear thing, but I don’t want to work as programmer.
I want to work with programmers, though, and I already do. I work for a publisher, which these days means that everything is online. I run a community site there, and I got that job because I already knew “about the internet”. I’m not at all a programmer. I write words rather than code. But to my coworkers, I’m the “tech person”, because I know how to talk to the freelance coders that we do hire, and what goes where on the site, and why we can change some things but not others. I’m not afraid to look at source code.
In my previous job, I was a biochemist, working with lots of people who had never taken a programming course in their life. I took C in undergrad, and a super-basic intro to Bioinformatics in grad school, and those meager credentials alone were enough to be asked to help with a project where biochemists (in the lab) and bioinformaticians (at the computer) had to collaborate.
Most non-programmers avoid even thinking about coding, and have no grasp at all of what you can ask a programmer to do.
If anything, it’s my kind of job(s) that CodeYear participants are after, not programming jobs. They’re not going to be coders, but they’ll understand coding, and they’ll be able to work on projects where programmers are a relatively new, or even temporary, addition to the workforce. They’ll be able to think of things in a new way, and actually provide opportunities for coders, by spotting things in their workplace that could be improved through programming. They won’t be able to do it themselves, but they can hire someone.
To my understanding, that’s been the goal of projects like CodeYear: To give non-programmers an insight into things that can be done, and to better understand how things work. In other words, to explain how a toilet works, without providing a complete plumber certification course.