Forgot your password?

Comment: Re:Training and/or Documentation (Score 1) 451

by ryen (#46434873) Attached to: Ask Slashdot: How Do I Change Tech Careers At 30?
Only thing I would add is that the tech sector is a whole different animal than the school scene. A lot more politics are involved and you're beholden to investors and other outside forces (although i'm sure schools have their fair share of outside forces, school boards, etc). You may not have the same job security that you might have in a school. Good luck!

Comment: Training and/or Documentation (Score 4, Informative) 451

by ryen (#46421409) Attached to: Ask Slashdot: How Do I Change Tech Careers At 30?
With your limited skillset without programming or intermediate sysadmin, but given your background in teaching and familiarity with concepts i'd say you'd be a good fit for training and/or documentation within a tech company. Training can include on-boarding new hires and getting them familiar with internal systems, or even training customers on using the software. I've worked with many people in these roles at companies i've been with. Documentation also might be a good route: writing manuals, online specs, and online training stuff. Theres lots of people doing this at the larger software shops.

Comment: Try community colleges (Score 1) 183

by ryen (#42824927) Attached to: Summer Programming Courses Before Heading Off To College?
I was in the same boat the summer before college. Wanted to learn more about programming but wasn't sure about it yet. I chose a course at the local community college which was affordable and no hassle to register for. It was C++ but focused on beginning programming which was probably not the best route to learn programming but it gave me a good start to everything. You might find more topical courses at community colleges if you're trying to stay away from the "general stuff".

Comment: Programmer vs Good Programmer (Score 4, Insightful) 767

by ryen (#41354719) Attached to: Can Anyone Become a Programmer?
I think a distinction should be made between a programmer and a *good* programmer. My CS program had a number of *really* smart kids - 1600 SAT scores and the like - but many of them really struggled at the concepts and barely made it through the curriculum. I think a good programmer takes 1. Creativity to think about problems from different angles 2. Drive to hunker down and get through hard problems (be it starting a new language, that pesky compile error, starting a large project from scratch). 3. I'm sure fellow slashdotters can think of many more

"The greatest warriors are the ones who fight for peace." -- Holly Near