So I’ll start with some context, a (kind of) brief dive into me and my history. I am currently Engineering Manager for Games at Dubit, navigating my team and company through rapid growth and a focus shift/addition into the Metaverse.

I started my professional life roughly 10 years ago as a software engineer in the games industry working first with c++ at EA Criterion on Need For Speed: Most Wanted 2012, before moving to Team17 where I helped to create a bajillion different Worms games and began leading small teams as the company picked up Unity as a tech, releasing a number of titles.

Seeing an opportunity for career growth I found my way to Dubit using my Unity skills to make mostly apps in the kids space, where I moved from Senior to Tech Lead over roughly 2 years. After about a year of great success in that role, my career trajectory rocketed up and I made the leap into management with the new title of Engineering Manager, a role which has consistently grown in responsibility as the company scales up and adds a focus on the Metaverse. I’ve had to deal with a lot very fast and in an often overwhelming way. I’ve found myself having a very fuzzy idea of the various elements of the job and being able to turn them into something clear that I can explain to someone else is invaluable.

All this to say I am starting this blog in an attempt to slow down my thoughts a bit, collate the things I learn/think about as a fairly new Engineering Manager and stave off the dreaded Imposter Syndrome.

Simply Rubber Ducking to the void