Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
BLACK FRIDAY DEAL: Trust the World's Fastest VPN with Your Internet Security & Freedom--A Lifetime Subscription of PureVPN at $48 with coupon code "BFRIDAY20" ×
Education Programming

Ask Slashdot: Best Options For Ongoing Education? 149

An anonymous reader writes "Lately, with the volatility of the economy, I have been thinking of expanding my education to reach into other areas related to my career. I have a computer science degree from Purdue and have been employed as a firmware engineer for 10+ years writing C and C++. I like what I do, but to me it seems that most job opportunities are available for people with skills in higher level languages such as ASP, .NET, C#, PHP, Scripting, Web applications and so on. Is it worth going back to school to get this training? I was thinking that a computer information technology degree would fit the bill, but I am concerned that going back to college would require a lot of time wasted doing electives and taking courses that don't get to the 'meat' of the learning. What would you do?"
This discussion has been archived. No new comments can be posted.

Ask Slashdot: Best Options For Ongoing Education?

Comments Filter:
  • community college (Score:4, Interesting)

    by i.r.id10t ( 595143 ) on Friday February 14, 2014 @01:13PM (#46248059)

    I am concerned that going back to college would require a lot of time wasted doing electives and taking courses that don't get to the 'meat' of the learning

    If you really want to get into teh web development side, I'd check out your local community colleges. All your gen ed stuff (english, math courses, history, etc) from your prior degree(s) should still count, so you'd just need to do the core classes for the AS degree you are interested in. You should be able to finish up in 3 or 4 semesters, if that.

  • by holophrastic ( 221104 ) on Friday February 14, 2014 @01:39PM (#46248347)

    I feel your pain. I actually went into, and then out of OO programming. The issue is that while it's a perfect technique for some very specific directions, it's horrible for solving real-world business problems.

    You, specifically you, need to look at OO programming much differently. Then you'll find it quite easy to use. It's not actually any different than procedural programming. It's simply a collection of encapsulated procedural mini-programs. That's it. It's exactly the same code, it's just called differently. It's the same function/subroutine, it's just launched/triggered/executed with a different syntax.

    The reason it's horrid for most business problems is simply because business problems are solved by figuring out how to sequence individual and often disparate tasks. Whereas OO is designed to solve problems where the same task needs to be solved countless times and the sequence is almost irrelevant.

    If you've always tried to use OO for business tasks, then your struggle wasn't with the hammer, it was with how to use the hammer to turn a screw. But if I were to give you a nail, you'd suddenly understand how to use the hammer quite instinctively.

    If you still/ever need someone to walk you through it, let me know. I'm happy to help.

I THINK THEY SHOULD CONTINUE the policy of not giving a Nobel Prize for paneling. -- Jack Handley, The New Mexican, 1988.