Ask Slashdot: What Should I Study?
A fellow Slashdot reader is seeking advice on a new field of study: After many years at the same company, I'm now thinking of a change. At my current place of work, I have worked on many different projects, from server side development, to UI development, and most recently, a lot of data science work. If I were to rate myself, I consider myself to be a good developer, thorough, conscientious and always willing to learn new things. Even my recent foray into data science (though not entirely new, since my graduate studies specialized in machine learning) has had reasonable success, and ideally, I'd really like to continue working in this space.
But, I'm starting to feel in a rut and I'm looking for a change. And looking outside my company, I'm not sure how to begin. Should I hit the books again? Should I focus on any specific technologies? I haven't particularly kept up with new technology -- after working for so long, I tend to think of that as something I can learn, when I need to. Any advice on how I should go about preparing for interviews? I'm quite willing to put in a few months of work into prep, so all suggestions are welcome!
But, I'm starting to feel in a rut and I'm looking for a change. And looking outside my company, I'm not sure how to begin. Should I hit the books again? Should I focus on any specific technologies? I haven't particularly kept up with new technology -- after working for so long, I tend to think of that as something I can learn, when I need to. Any advice on how I should go about preparing for interviews? I'm quite willing to put in a few months of work into prep, so all suggestions are welcome!
Look at the opportunity out there and become skilled at something completely different. There's a crapload to be made in many skilled trades now that Baby Boomers are retiring out. Some trades like plumbing and electrician can't find enough people, and the opportunity to become very successful is wide open. Be a long time before robots take the job of a plummer, electrician and other skilled laborer.
This is what I'd do if I were in my 30s even.
Did you ever wake up in the morning, with a Zombie Woof behind your eyes? -- FZ
I'm in Seattle area... People with Cisco CNE's, Security CISSP's are constantly getting poached. Good security people bring $200k-$1M salaries out here. Network engineers make in the $100K range (as do programmers out here).
AI is really growing an high paid, but you need a Phd to grab a top salary in AI. If you have that, you can start at the same wages (or more) of a neurosurgeon.
If I were 21 today and starting over... seriously.. I would spend 4 years in the military. Get out and get a job as a fire fighter. They start out here at $80K. Some work 10 days on, 20 days off..(those 10 days you live in the house). Retire at 53 or 54 with a full pension and health care and spend the next 30-40 years fishing, hunting, playing with grand kids, traveling... what ever.
This is a terrible submission. What the hell kind of question is "what should I study" with zero context? How fucking arbitrary is this?
I don't respond to AC's.
Original AC here. I should clarify - I don't want to entirely change my field of work. I still want to stay in programming, and possibly data science. I'm just really nervous about interviewing after a *very* long time, and I'm wondering how to go about it. I also have a very varied set of experiences, not specializing in any one thing - just really a matter of doing what was needed, when it was needed. I'm not sure how this will go down in interviews, and how to best portray it.
Get an AWS Cert, best study material is Udemy A Cloud Guru (Ryan Kroonenburg). I spent a few weeks on it, and passed my AWS cert, plus have a great introductory understanding of AWS cloud.
I have worked on many different projects [...] I tend to think of that as something I can learn, when I need to.
Sounds like you're a bit of a generalist with the will and ability to dive into a specialism when needed. If you really feel you need to "pick a side" and specialize, then all advice I can offer is: find something you love doing and specialize in that. But if you enjoy the learning process itself, the experimenting and ground-breaking work with new tech, then maybe you can find a job working in an innovation team.
Innovation is a bit of a buzzword, but there is plenty of legit innovation work out there. Innovation teams often offer a chance to learn new tech or new ways of doing things, and require a lot of flexibility from their team members. Perhaps that will suit you... I've been involved in innovation for 20 years or so, and I not only enjoy the great variety of technologies I have to deal with, but also the fact that I often get to wear many different hats: from project manager, team lead, architect, to coder and business analyst. Sometimes you'll be a one man team, sometimes the team will need someone to write a couple of tests for tomorrow's experiment or prepare a short presentation for a visiting VC, and yes I am sticking up my hand to volunteer. If you think that doing something yourself is often faster than getting others to do it for you, and if you can actually deliver results that way, then innovation might be something for you.
Positions in innovative work are few and far between and are often sought after, so you need to position yourself well for that when preparing your CV. Your background in data science and your machine learning study will help, since those fields are currently firmly hanging ten at the top of the hype cycle. But also emphasize your versatility as it's a key quality in such roles: show that you have experience in adapting to circumstances, and in diving in when the project calls for it.
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
Study art. Better yet: *Train* for an art.
Seriously. Is there an art (performing art in particular) where you say "OMG that is so awesome, I wish I could do that."? Study/train that. Obviously there are limits. If you're in a wheelchair doing ballet won't work. But perhaps music, singing, acting is something that would be an interesting challenge. I have a diploma in performing arts and even though I've never done anything remotely like that in the last 2 decades (except being quite good at social dancing (Argentine Tango)), the experience was like nothing else. It does help me do presentations, that's obvious, but I've also learned about styles and aesthetics, art history and how to move gracefully. It helps me with GUI design and understanding emotional aspects of the user experience.
Imagine getting a Chello and learning that. Your horizon will expand into a universe you couldn't dream of knowing doing IT/Software every day for the rest of your life. You probably have IT pretty much down and getting into some newfangled technology or PL is a walk in the park once you've got a broader perspective on life in general.
Art most likely won't earn you big bucks but from what I get that's not what you need right now anyway. Note that fine art is closer to programming as an art than performing arts, so I strongly suggest performing arts, but perhaps you do want to get into drawing or painting or illustraiont or - an intersection with IT - 3D/VR and stuff - then fine art might be a neat alternative.
But generally rest asured, if you move away from IT and into an art, your life in general will improve for the better. Especially with your life right now having you struggling for sense and meaning. If only art becomes an enriching addition to your life as an IT expert right now, that will spill over into your IT career and have measurable positive effects. Promise.
My 2 cents.
We suffer more in our imagination than in reality. - Seneca
teach.
Which has more power: the hammer, or the anvil?
Why does it matter?
Stop being an ageist prick.
They mentioned "after many years at the same company" and "since my graduate studies", so you can probably set a lower bound just from those hints.
I don't trust atoms -- they make up stuff.
* Do what interests you, and/or
* Do what pays.
Next question.
try learning more about functional programming. In my experience, most devs haven't really built anything using FP
Functional programming is a hot topic ... yet very little has actually been built using it. That indicates to me that it is just hype. Programming with "pure" functions sounds nice in theory, but the real world has "state", and you don't get far by pretending that it doesn't.
That's partially crap advice by Mike Rowe.
The secret to happiness is to remove false expectations
Yes, some people absolutely SUCK at what they love. The deluded ones are the ones who definitely SHOULD follow Mike's advice. They suck and always will, and no amount of talent will save them.
The problem Mike is painting everyone with the same brush. That does NOT imply that they will NEVER get better.
When I first started programming I sucked -- like every other fucking newbie -- because that's what a beginner is. Someone who DOESN'T have the knowledge and skills. I kept at it because I _loved_ it. I invested the years to becoming great. Today it pays the bills and I have a job that doesn't suck.
One of the secrets to life is to find what you love, and what your talents are.
Chances are, that if you invest in yourself, you can find a way for it to make you money.
There is no guarantees in Life. That's what makes it frustrating. Life isn't a simple checkbox-follow-these-instructions-and-success-is-guaranteed. Life is what you make it. Sometimes you need to _try_ things in order to know what _not_ to like.
Invest in yourself -- because chances are, no one else will.
If you're tired of data science already, jump on the AI bandwagon!
I would have to agree, if you have an interest in big data (data science is the gateway to big data analytics), then by all means, pursue it. You're already ahead of the curve by quite a bit.
If you want something outside your comfort zone, but close enough to your experience to be very interesting, I would suggest playing with a Raspi, especially the hardware end of things. Understanding RS232/RS485, I2C and/or SPI communications can be very rewarding work, both intellectually speaking and financially. Embedded hardware is fascinating because it really forces you to start considering all the ways that things can go very very wrong. High level development has a lot of simplicity in that you can pretty much always count on a certain subset of fundamental operations always working as expected. In the embedded space, you can write data to an I2C bus, and what arrives at the far end isn't always what you sent. The only error correction is whatever you bring to the table.
You might even be set in a very enviable position of being able to bridge the divide between big data and embedded systems. In the near future, the IoT will start producing simply vast quantities of data, even by today's standards. All of that data will be worthless without data analytics to figure out how to make it actionable.
I wish I had a good sig, but all the good ones are copyrighted
I knew a guy who retired from IT to start his own roofing company in his mid-50's. Makes more money in a summer than he does all year in IT.
Historically Phrenology has been a more reliable source of income than AI skills. AI comes and goes in popularity. Phrenology and Astrology are forever.
Some drink at the fountain of knowledge. Others just gargle.
Ever done real-time embedded firmware? It's pretty much all functional because it's highly deterministic, stable, and easy to debug with limited UI access. EVERY paradigm has its place; only a rather ignorant engineer would claim "X is a useless paradigm"...
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
Bioscience. We had digital technology in the 20th Century and we will have Biotechnology in the 21st. You can thank me later.
Facts are history now plebs have politics for religion on social media.
It's possible we are in an AI bubble*, so be careful, because in the shorter term you still have to pay the bills.
I would suggest you pick 3 areas that pique your interest and explore them deeper, including asking practitioners. After you know the 3 better, then select 1 to focus on in a formal career sense.
By the way, genetics/data-biology seems like it has a bright future: it doesn't smell as bubbly as AI, yet gene scanning is growing ever cheaper such that there will be tons of genetic data to analyze. We will soon get to the point where it's economical to scan the entire DNA of an individual patient.
* AI is not going away, but we may hit a wall or two where too much money is chasing too few practical results for a few years and investors lose patience, pulling the plug on tons of R&D, sending AI researchers flooding the resume boards.
Table-ized A.I.
Funny, I know quite a few 35-40 year old men just starting med school. I know some 45 year old new Ph D.'s as well. Problem is that American white men are their own worst enemy -- they're expected to follow a career for life by society, like some 1950s nightmare. Society doesn't jugge a 40 year old woman going back to school OTOH.
What's that you say?
Well OK then. Let's really try thinking outside-the-box. Start studying medicine with a long-term plan on getting a job in Pediatric ICU or Pediatric cardiac OR.
Roughly 19 years schooling, residency and fellowship.
That means you'll be about 75 by the time you're ready to start work. You might have racked up some enormous education bills to pay off. Just guessing that'll take 10 years to pay off. Then you can start saving for retirement. Another 30 years ought to do the trick. Assuming that Parkinson's or Alzheimer's hasn't set in by then, you can probably look forward to settling into a nice relaxing retirement at 105. Tee time's 5am. Be there!
Did I go for a worst-case scenario? Obviously. Just to make a point age can be a relevant factor.
The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
That's a totally unfair comparison.
A major in Art History could land you a job as a museum guide.
Confucius say, "Find worm in apple - bad. Find half a worm - worse."
You don't know much about functional programming, first of all it is not what you think, your functions here like sin() have nothing to do with it.
Secondly, real world functional languages allow to modify state via monads. https://en.wikipedia.org/wiki/...
In a functional language "functions are first class citizens", that means they behave like objects. e.g. the following code:
a = sum(sqrt(3.7), sqrt(4.2)
Creates three function objects, one instance of sum and two of sqrt, then it evaluates the "expression tree"
Behaving like objects means, you can store them, pass them around as parameters, create new functions by combining existing ones.
Regarding your answers: FP is not a hype, it is ages old, most likely older than you.
All modern languages support features of FP (C++ with functor objects, and now with lambdas), and nearly all modern languages either have lambdas or closures.
Depending on project and Java Version I use lambdas every day. If you use the STL in C++ you can not help yourself doing FP (albeit a bit limited)
Most prominent is probably Erlang. They used to write all the router and switching software in Ericssons gear in Erlang. https://www.erlang.org/about
That FP is only limited used is because the modern implementations e.g. in Java are so watered down and only support a subset of usages (e.g. lambdas/closures and the Streams API: http://www.oracle.com/technetw... )
Cost free eBook I read (by iBook/Kobo/Amazon/ObookO/Gutenberg etc.): "The Green Odyssey" by Philip Jose Farmer.
You think that's bad?
Someday you should count up the number of different ways God invented to compute pi.
pi = 16 arctan(1/5) - 4 arctan(1/239)
Seriously, any computation of pi more clever than that is pure showboat.