| > After a few months I realized I was unemployable and set out to change it. First, as 20 something I can't imagine how hard it must be to wake up with the realization that you no longer have a job. Second, I think you deserve some real credit for 1. identifying that you were unemployable and 2. fixing it. However, the real trick is identifying when you're unemployable (or even starting to get close to it) before you're unemployed. This is a game - and one that you'll never really win. But like all games: you keep playing - you get better. The trouble lies in that this is a game in which you need to be ahead of the gamemaster (that is - current and future employers). > I do think if I found myself unemployable again I could repeat... I want to stop you right there. I think your objective from here out is to make sure you never find yourself unemployable again - rather than waiting and/or hoping it doesn't happen. > almost any kind of expertise in a major JavaScript framework like Angular, Ember, or React/Flux might get you a remote job fairly easily These are valuable skills and expertise to have - and they will land you a job - but don't let it make you a one tricky pony - as that's a fast-track ticket to unemployment. I think few of these front-end frameworks will be here for the long-haul. If I were in your shoes (of course I'm not in your shoes - it's 100% your choice) I would take what you've developed so far and start to dive into the fundamentals and then get the expertise. For example: get to know the architectures of these frameworks: analyze and criticize them, attempt to improve them if you can; learn design patterns and identify the anti-patterns (important !); learn your algorithms - as it is these features that make you a valuable professional in the long run. Not just another PHP/JavaScript/ColdFusion dev. Then you can wade in deeper and build up deep full-stack expertise. You could think about: "Oh how can I optimize view rendering in Angular?"
"How can I solve head-of-line blocking when using web sockets?"
"What is the optimal compression algorithm in order to serve JavaScript files for mobile devices?" I can't imagine a huge number of people think about how to solve these challenges - but I would bet that a lot of people face them. All the other stuff is just tools to enable you to apply your expertise easier and faster. |
I think that's kinda like saying, "I want to stop you right there. Instead of buying auto insurance, your objective should be to not get into a car accident again." It's a nice goal, but you're gonna need a backup plan for if something goes wrong.