I’ve been in the software engineering field since 2009 with a focus on front-end development and UI/UX. This is funny to me because when I first started learning web development back in the early 2000s, I avoided JavaScript like the plague. I would only touch the HTML and CSS of the website. The design was all I cared about. Now, JavaScript is all I do.
The Now
Currently, my team is contracted by Cisco to convert and migrate their Networking Academy application to replace all unsupported Flash assets into Canvas. Everything from localized SVG translations, animations, and simulations is being converted over.
We used JSFL in Adobe Animate to export what we could, and manually update and fix what we could not export. This and the effort to break out different pieces of course content for subject matter experts to build and/or modify a given course for their students is still ongoing.
What scripting language did we use to migrate this over? I want to say Python… But it was JavaScript. Leveraging Node we didn’t need to context switch due to a change in languages since we were all front-end engineers. I wanted it to be Python though.
The Obvious Choice
I’m at a crossroads here. It’s obvious which direction I’m going given the title of this blog post but if that wasn’t clear, I’m planning to shift careers into data engineering. Why? The current project I’m on has me shifting data from one place to another to be consumed by subject matter experts as I’ve said before. This very action has inspired me to move and transform data on a bigger scale but with a different impact.
I’d like to help data scientists and ML engineers get the data that they need to work their magic or analyze the data in a way that helps either the business or the world.
Python has intrigued me since being introduced to it circa Python 3 but I’ve never had a chance or time to work in that language.
Now, I’m making time…
The Future
I’ve set up a personal learning plan for myself because I wanted to be clear on what to study next. I tend to ponder too much on “what’s next?” rather than what I’m learning at this very moment. The learning plan I’ve created is only a start and not the end all be all of data engineering. Of course, this plan isn’t set in stone and will be modified if a course is subpar.
My Data Engineering Learning Plan
My company offers “professional development” funding every year and I’ve opted to subscribe to Datacamp and Udemy to learn data engineering as well as a single book for now.
Broad Topic
The first two list items above are courses that cover a wide range of topics. The third in this list is a book I see everywhere and have been enjoying the read. Datacamp’s teaching style doesn’t match the way my brain learns. I see inconsistencies in teaching methods and exercises. I’ll still complete this course, but that’s my high-level review of Datacamp.
Programming Languages
Python & SQL are, from what I’ve researched thus far, required as a data engineer.
Python is such a beautiful language. I’ve worked with it before, but don’t feel confident to call myself proficient. I’ll be changing that after the courses above are complete.
SQL joins make sense. Complex SQL joins hurt my brain to read. Hopefully, this course on SQL will help with that.
Technologies
These are courses on topics I’ve researched that a data engineer should know. I can’t speak on these technologies yet, but these courses are highly reviewed.
Certifications
My company is an AWS shop. Speaking with my team lead, he has stated this would be a good starting point. But I feel I need some knowledge of how these pieces work together… maybe the courses cover that? Regardless, I’ll be taking this course, the Python course and reading my Fundamentals of Data Engineering book in parallel.
Practice
Who doesn’t need practice? I like puzzles. These links will scratch that part of my brain that likes puzzles.
From here on out…
All in all, I’m pretty excited. I haven’t been this excited in a while. After years of saying, “Oh, another JavaScript library/framework to learn.” I can say, “Oh, a new tool that may be better than the current one.” :shrug:
Off to learning!
Be sure to follow me @chrisparaiso.