I’m looking for suggestions for learning something that might help me have better job security, even if I don’t need to move out of Web dev completely. Also, I’m not looking to change companies voluntarily in the near future.
- I’ve been considering looking into Data Engineering, ML, and/or AI. My Math background is not solid (I got up to basic integration but never completed Calc 2, Linear Algebra, Discrete Math, or advanced Probability/Statistics). How much Math do I really need, and what’s an effective way to learn it (I’m 42)?
- I really like Elixir and its ecosystem, and have an interest in learning Nx/Axon/Bumblebee, but Python’s ecosystem is more established and seems to have much more mindshare. Does anyone have a day job doing Data Science-type things with Elixir?
- Has anyone been able to transition to new tech fields via Udacity/Coursera/EdX without huge side projects to show? I am willing to put time into learning and side projects, but doubt I have the ability to treat it as a second job.
- Outside of DS/DE/ML/AI, I’m also interested in Programming Languages and Compilers. Is there an abundance of meaningful work in these areas where someone without a CS degree (just a Web dev bootcamp and some university courses up to Data Structures) could potentially get a foot in the door?
I agree that Python has a more mature set of libraries for this sort of thing, but OTP provides some useful distributed features that would be difficult to implement in Python. I also think writing code in Elixir is more productive due to things like pattern-matching, Lisp-style macros, and a lack of OOP.
Job security is a function defined as of a lot of different things by different people, so I think I'd really look at that concept and do some frameworking around it before going into tech, and thoughts like what you can do with this tech or job or that one.
For example, a lot of people perceive that job security is an issue due to latent relational concerns at work. For example, they watched a junior get promoted above them, or they get the sense that their ideas fall on deaf ears.
Regardless, if job security is your priority, I would really hold on tight to that model of what you're looking for--outline it, define it, give it depth and color and meaning.
Even the "best careers for job security" can lead people into individual _roles_ or _jobs_ that end up being functionally insecure.
I'm also not really sure if web dev is facing a glut in all areas, and I would absolutely interrogate this idea for your own sake, maybe even make it prove itself--simply because you have so much darn experience / XP / momentum in this area that it'd be a shame not to bring as much of that forward as possible.
Anyway, just sharing some thoughts on what you wrote and I wish you the best of luck.