From Math & Physics Instructor to Software Developer

Hello! I'm Scott Skanes, I'm a Software Developer and Data Scientist with trophi.ai.

What did you do before Get Coding?

Oh, so many things! I atteded MUN for engineering, leaving after 2.5 years to explore some other options that might spark more joy. This search included Audio Engineering, Culinary Arts, and Video Game Development, to name a few. I eventually went back to MUN, earning a B.Sc. in Applied Math & Physics and a B.Ed.

This gave me the opportunity to explore the world, teaching in the UK for a year then teaching college in the Middle East for 7 years, visiting a few dozen countries, getting married, and becoming a dad along the way!

What made you decide to switch your career?

It wasn't an overnight decision - the thought had been building for quite some time. I've always been "techy", figuring out computer stuff since I can remember, but it was really my time spent getting a Master's in Ed.

Tech that opened my eyes. I kept hearing how important "computational thinking" was for the new generation of students, and how there will be a huge need for code-related knowledge in the workforce of the future. I was starting to look for a change from the teaching gig, and this got me thinking... Why don't I try coding? Surely it's not too late. So, my Master's work planted the seed, but it wasn't until 3 or 4 years later (when I was laid off my college job) that I dove headfirst into a career change.

Did you ever think of switching your career to tech?

Yes, but my teaching approach was always kind of tech-adjacent. My approach to teaching prioritizes experiential learning, and I'd often develop hands-on lessons where students would explore math and physics concepts using apps, widgets, all sorts of interactive, techy stuff. I also designed all my lessons.

These experiences gave me a wide and varied set of transferable skills which have truly been a boon for my current job. That said, switching to a "true" tech career was only a pipe dream until I lost my job and took a good hard look at my situation (and dwindling happiness levels).

Why did you choose Get Coding?

I didn't want to get another degree. I didn't want more one-size-fits-all classes, lectures, busywork, theory, or electives. I wanted a laser-focused learning program that I could pour all my energy into, and get back concentrated knowledge and experience I could apply in the field as soon as possible.

I needed something personalized that would meet my specific needs and someone to be there when I had questions. To be honest, I thought that was a totally unrealistic expectation, and was pretty dejected thinking I'd never find such a thing. It was phenomenally fortunate that I heard about Get Coding almost immediately after being laid off, as it was exactly what I was dreaming about. I contacted Jan Mertlik the next day and got the ball rolling.

Were you working during your time with Get Coding?

Nope. I chose to do Get Coding full-time, and I treated it like a job. I would get up early, help get my son to daycare, then work on projects all day until late afternoon. I tried to avoid evening work to prevent burnout, and to allow for some quality time with my wife and son. I wouldn't have been able to get where I am today without the support of my wife, Allison, who helped with so much at home while I dedicated myself to the program, so I have to thank her for that kindness.

What did you build during your time at Get Coding?

Two really cool projects, if I do say so myself.

The first was called Beat Circle, and the concept was to provide a fresh take on a metronome, giving some tweakable settings and allowing people to visualize the cyclical nature of a bar of music, including its rhythm and tempo. I built it using my then-rudimentary knowledge of HTML, CSS and JavaScript, along with plenty of Googling and questioning my fantastic coach Leon Chisholm.

My second project is called Townsbattle, built using React with support from a phenomenal coach, Devin Marsh, and it's significantly more involved. I chose to build a unique game, which I honestly can't really recommend as a good Get Coding project.

Why, you ask? Well, there are a few reasons, but Number One would be you don't want to be bogged down by game design questions when trying to figure out React principles! There are enough tricky concepts to wrap your head around when learning to code; I don't recommend the extra stress of the parallel development of game mechanics. And, if I was to recommend making a game, I'd suggest choosing one that already exists and making some fun or unexpected tweak to make it yours.

Finally, I did start work on a third project which would help people in stores instantly determine if local items were taxed, track prices, and find sales. I only got a few weeks into the project with another star of a coach, Mitchell Hynes, before being contacted by trophi.ai.

What are you doing now?

I work at trophi.ai developing coaching software for racing sims and other video games including Rocket League, and I absolutely love it. I get to work on difficult problems each day with a really positive and supporting bunch of co-workers. Our boss gives us enough autonomy to try fresh and often experimental ideas to see where they go, while providing guidance when needed to keep us focused and ensure a quality end product.

There are plenty of challenging days, but that helps keep things interesting. Perhaps most impactful for me is that I feel seen now, more than I ever have in past jobs. If I do good work, people notice, they give compliments, and I get lots of great constructive feedback. If I do not-so-good work, well, I also get constructive feedback and direction, which helps me to grow. In my experience, tech in NL is just a really positive environment, and I can't recommend it enough.

How do you think your previous career helped you in achieving your goal?

My previous career gave me the wisdom to understand how to communicate well with others, to be an effective worker and collaborator, how to help others learn, how to design products that are fun and intuitive to interact with, how to manage my time effectively... the list goes on.

I think any career can act as a source of transferrable knowledge and skills if you take the time to reflect on your experience (good or bad) and extract lessons.

What would you say to people considering switching their career to tech?

Do it. It may be scary or uncomfortable to do something so seemingly-reckless -- it sure as hell was for me -- but that temporary discomfort is nothing compared to a potential lifetime in a career that isn't fulfilling.

Believe in yourself and go for it; there is a huge support group waiting for you in tech.