Slashdot Mirror
Predicting the Future of Electronics and IT by Watching Component Demand (Video)
A big question college students should be asking is, "What IT and electronics knowledge will be most in demand five or six years from now?" In these fast moving niches, an answer is almost impossible to come by. But what if you were one of the people who supplied raw components to the electronics industry? Wouldn't you have a better handle than most on what kind of devices and components are becoming more popular among prototypers and engineers? And wouldn't watching those trends possibly give you at least a little insight into what the future might hold? Randy Restle, Director of Applications Engineering at component supplier Digi-Key Corporation, carefully tracks orders and tries to determine what's hot and what's not. His reason for doing so is to figure out what Digi-Key should stock in coming months and years. But his insights can also be used to decide what you might want to study or -- if you're already working in the field -- what products you or your company should consider developing. Digi-Key also has an online video library where they feature new products and give ideas of what you can do with them. Even if you're not an engineer or electronics hobbyist, it's fun to see what's available but may not have hit the mass market quite yet.
How the hell am I going to pay off my student loans by entering an industry moving towards decentralized. lowest-bidder IT and commodity hardware, where the labor market is global and comprised of people who have either been in the field for decades or can live on peanuts compared to you, where the brighest minds of a generation are bent on extracting pennies from stock trading algorithms, or coming up with new ways to make you look at ads, or engaged wholesale invasion of privacy.
Do I really want to piss away the best years of my life writing code for yet another tech startup with no business plan beyond IPO, making billions for investors while getting nothing in return? To know that, in the end, I made no difference in the world?
My advice: Make computer science a hobby, not a career.
A big question college students should be asking is, "What IT and electronics knowledge will be most in demand five or six years from now?" In these fast moving niches, an answer is almost impossible to come by
Actually, I believe there are good solid answers to this one that have been true for a decade and will likely be true for the coming decade.
First off kid, you have to understand that there are a lot of fields you seem to be lumping together. There's a difference between code-monkeys, sysadmins, network engineers, electrical engineers, embedded engineers, and web-devs.
For any programmer there's a big question of which programming language to learn. This is something that induces flame-wars and strong passions because everyone has an opinion and their own choice is best. This is because it's an inverse tragedy of the commons, everyone wants you to learn their language because it benefits them and their language to have more users. But a binary search tree is a binary search tree in any language. Some are more verbose. Some are cludgy. But if you understand binary search trees, or whatever, the language used to deal with them by and far doesn't matter. Knowing the syntax of a language doesn't make you a good programmer. Knowing how to use the language to accomplish meaningful tasks, that's what's important. It's a little easier if you learned C rather than IBM RPG back in the day, but if you could learn RPG, you can pick up C without serious problems.
For Web-devs, they'll fret over... let's say... which CMS project is better: Joomla, Sharepoint, Drupal, Django, Wordpress, yaddayaddayadda. Conformity is nice and picking one is important. But you're a COLLEGE KID, when you graduate you'll know what goes into a CMS, theoretically how to make one, and how they work. If you just wanted to learn how to turn it on, you should have gone to a tech school. They'll hold your hand and read the manual with you.
(By the way I also have a thing against "certification". It might make sense for the sysadmin types, but a cert on a programmers resume is a net negative.)
Sysadmins, network engineers, and the hardware guys all probably have similar stories. There are common tools out there you should know, but god knows everyone and their brother make a version of it. Try not to tie yourself to one particular set of tools least you suffer from over-specialization.
tl;dr: It doesn't matter what specific component, language, framework, or gadget is popular in 6 years. You're in college, not a tech school. Learn the basic fundamentals of your field and whatever the hip new thing is will fall nicely into place and you'll understand what it's doing and what's going on. You need to learn how to use a hammer and nails to build things, not fret over which hammer is the best bet.
If I was a young double E student I would focus on analog electronics. Designing analog electronics is a dieing art. And it is art as much as electronics. Simulation only goes so far. Then you need to know the tricks of design and layout.
The old school analog electronics engineers are retiring and there is not a new crop of young engineers to take their place. While more and more things are going digital we will always need analog electronics to interface with the real world.
Analog electronics will become a specialized niche that will command big bucks. Kind of like COBOL programming. Neither of which are very glamorous but both of which are all around us.