When you’ve immersed yourself deeply enough in programming to write a ray tracer in 68000 assembly language in your teens, it’s safe to say you probably aren’t going to become an accountant. So whilst I know some folks struggle to find theirs, my own career path was always rather obvious.
Since graduating from uni a not-insignificant number of years ago (!), I’ve been lucky enough to have worked for some truly inspiring folks at some amazing companies and on some very cool problems. I’ve had a chance to help build software for many different industries and sectors. I think that gives you a really valuable perspective on what we, as software engineers, can actually offer.
More importantly, it also gives you a great sense of what’s possible with this universal toolkit called “software”. For that’s all it is; a toolkit, and nothing more. As I’ve said before, it’s what we do with that toolkit that counts.
I’m mostly interested now in exploring what’s possible with technology, and what we can build with it to benefit each other. I think there’s a certain obligation to look up from what we’re building occasionally and to ask how it helps us. If the answer isn’t obvious, it probably doesn’t. Self-serving industries, with little benefit for those outside of them, no-longer interest me.
I realised that the earlier part of my career was probably naturally something of a travelling tech apprenticeship: You work in various corporate scenarios, learning, building and applying what you’ve discovered.
Beyond any apprenticeship, the bigger question always comes: What will you do with this now?
Unlike my initial career choice, the answers aren’t as obvious… but, if I’m open to finding and exploring them, they’re probably going to be at least as interesting.