I put forth a specific resolution for 2022 regarding my coding knowledge. What’s the coding plan of attack?
In the past year, I’ve reflected a lot on what makes me happy. To clarify, I’ve thought a lot about what I want for my future. Ultimately, I want a relatively privately glorious life. I’d like to work remotely, flexible hours, with the opportunity to live close to nature at any given moment. I want to swim in the ocean, climb a mountain, drive through glorious red-and-orange autumnal forests without the constraint of “coming into the office” on Monday.
So, what does that have to do with a coding plan?
I’ve come to the conclusion that the best way to attain that flexible, remote lifestyle, is to obtain a job that I’m passionate about that allows for remote work and unlimited PTO. Wouldn’t that be glorious? I feel the best way for me to get there is through STEM. I currently work remotely, and it’s a blessing, but I am attached to the stereotypical 9-5, with fifteen days PTO. It’s… Beinaheleidenschaftsgegenstand. To really attain the life that I want, I need to level up in my skills. Better skills = better benefits, and better salary! If I’m that desirable a hire, I can ask for more.
To put it into simple terms: “Sometimes, you need to work a little, so you can ball a lot.”
As a result, I want to sharpen my coding skills even further than I did in the past year. I’m really good at two or three things, but that will only get me so far. I think that adding two or even three languages to my repertoire could improve my portfolio, my resume, that much more. I’m in year two of my three-year plan. What if by the end of year three, I’m at that next level where I have that perfect job (for five years and then I re-evaluate what being in my thirties means for my happiness)? Score!
Essentially, I want to transition from my current position as front-end developer into software developer. What I like about software development/software engineering is that it’s more backend focused. Front end, what the average user sees, tends to be what people get persnickety over in my line of work. Back-end is more absolute, with specific measures of accuracy and efficiency. How ironic! I want a more absolute line of work to give me more flexibility!
Thus, I present my current coding plan, to level up in the next (let’s playfully say) 18 months.
Coding Plan
Part 1: Refresh, Polish, and Present
I have a very basic understanding of Javascript, which has become an essential for any line of front end or back end development. The same can be said for PHP and SQL (which tend to go hand in hand). I have a specific focus on Javascript and PHP for the beginning of the year. Once I know I have the knowledge, and fully understand both languages, I can create portfolio projects that prominently feature both!
Part 2: Start Anew.
I previously mentioned wanting to learn Kubernetes and AWS. However, the more I look into it, it would appear that both are helpful, but do not make-or-break a developer/engineer. What is important, however, is to actually have the programming languages necessary to build. As a result, I will take it on myself to learn C++, a prominent programming language, as well as Python, which I’ve previously dabbled in but haven’t worked with in a long time.
As well, I would like to learn Golang (also known as Go). This language features prominently in Google products. I fell in love with the mountains and energy of Colorado, and wouldn’t mind moving there. For all that I talk of wanting to work remotely, without needing to go into an office daily, wouldn’t it be funny if my job had an HQ in my state after all? Boulder has a Google office. Imagine that.
Part 3: Practice, Practice, Practice
Fun fact about the tech industry: as cutthroat as all high paying, high power industries are, those in the highest positions want the best and the brightest. As a result, there are resources aplenty for preparing for the fast-paced problem solving of STEM based positions! Aaron recently underwent a job change, which included tech interviews with practice questions. Turns out, such questions can actually be found online! It’s like Quizlet all over again.
At any rate, once I’ve got a portfolio and a resume (and maybe some LinkedIn Learning certificates) to grab a recruiter’s attention, my next step will be to actually make sure I can walk the walk, not just talk the talk. I’d like to go through as many resource websites as I can, solving as many problems as I can. Technical interviews sound terrifying, but it’s the sort of thing you need to ace to make it to the big leagues. Put me in, coach!
Part 4: Finish with a Flourish
So, I’ve got the skills, in ample supply. Now what? Time to pivot! Once I feel confident that I can answer most questions, and have the resume to prove it, I’ll flip back to more learning (with the continuous practicing). I’ll focus primarily on learning Javascript frameworks like Typescript and Angular, which appear to be the tried and true favorites of the moment. Lastly, as a cherry on top, I’ll go for an AWS certificate, and a basic knowledge of Kubernetes.
Game, set, match! Point. Joy. Game over. End of game.
CONCLUSION
If it weren’t clear, my coding plan flows relatively loose. I know the basic plot points, but I’m not sticking to an uber rigid timeline to get there. I’m hoping (and thinking) I’ll pick up some concepts quickly, but others will take more time. In addition, I like my current job! It’s not something I want to do forever, but I don’t feel an urgent rush to leave it, to escape my own misery. That in itself is amazing! Keeping a loose structure on things will help me focus on my other goals, like writing and learning non-programming languages.
I anticipate growing pains and burnouts. That’s all part of the learning process! I’ll keep track of my progress with this coding plan throughout to make sure that by the end of the year, I have something to show for it. Even if it’s only a completion of step one, that’s better than nothing. Always growing, always learning. WE DEVOUR.