3 ms·
Not really, to be honest. I mean, right now I do what should be "accessible via high school courses"--I do devops/infrastructure development and automation. I c
by eropple 9y ago
Not really, to be honest. I mean, right now I do what should be "accessible via high school courses"--I do devops/infrastructure development and automation. I call it "e-plumbing" and I'm not even joking. But I have zero worry about competition for a few reasons:
1) There is enough subject matter expertise in the infrastructure/devops sub-field that being able to synthesize approaches out of all of it is really, really hard and is in many ways gated on experience. Understanding all of the products AWS throws at you and when to apply them versus using vendor-independent solutions versus using a different cloud provider entirely is a problem that high school and YouTube won't really prepare you for.
2) Being able to cohesively apply that subject matter expertise requires a framework that takes a lot of theoretical knowledge that takes a while to both learn and to understand the importance of. People shit on college all the time but I would be significantly worse at my job if not for the rigorous algorithmic courses forced upon me at college (it's one of those "do you know what you don't know?" things).
3) The baseline computer science background, programming chops, and breadth of experience that make me good at applying code to #1 and #2 means I have other options if I want to get out of infrastructure work. That's how I ended up here--I went from college to doing bog-standard Java work at TripAdvisor to leading a mobile team two years later because "you're smart, you'll figure out what you don't know" to devops/infrastructure work, where I'd never touched AWS or Ruby and yet picked both up on the fly. A few years later, I consult to pay the bills and work on other stuff that I find fun.
4) The demand of the industry is not going away any time soon; there will be a need for seniors to guide and manage even that theoretical legion of juniors. I'm much more worried about those juniors than I am today's juniors or seniors.
- austincheney 9y agoI am a JavaScript developer. I also have 0 worry about competition in the job market. It isn't that I am a rockstar programmer, that JavaScript developers are hard to find, or even that demand is low. Unfortunately, it is that most JavaScript developers suck. Absolutely horrid. The primary culprit is a lack of education (formal or mentor-ship) on how web technologies work and I have almost never encountered somebody who did well with these technologies due simply to their university education. If you are hoping your mastery of Java or C# is good enough to quickly jump into JavaScript or some other web technology will be sorely disappointed.
- eropple 9y agoIt's funny that you say that, because I've been getting into ES6/TS lately (mostly to implement my own stuff) and that's basically been my reaction: "this stuff is pretty straightforward, why is so much code so bad?". Then I realize that I've had to understand, if not implement, those web technologies to do the work I've already been doing (and, years back, I wrote a JavaScript runtime as an experiment, so the language's guts aren't foreign), and I'm just picking up the other end of the rope now. The amount of implicitly-carried junk we all know about to be good at our jobs instead of just tolerable is pretty amazing.