In a book by a retired NASA astronaut, Chris Hadfield, it is said that you should aim to be zero. This means you do not shy away from responsibility, but you also understand when you take on too much. You understand there is a lot to learn, but at the same time you are confident in what you know. To some, this may seem like sitting on the fence, but as I have applied this philosophy, I believe being a zero is a good state to be in. The above characteristics mean I value and encourage the opinions of others, enabling me to be an active and hopefully respected member of a team. I never stop learning and at the same time I try to pass on what I have learnt to others; I always listen whenever others try to pass on advice to me. I am always trying to discover my weaknesses and aim to improve them; I believe denying your weaknesses is the first step to failure.
Technology is my passion – not just my job. If I’m not out running, hiking, or spending time with friends and family, you’ll frequently find me playing around with a mess of chips and wires trying to build a Z80, or spinning up QEMU to mess around exploring some Operating System concepts. I love technology and the fact that I can do this for a job makes me extremely fortunate.
I love coding challenges – I’ve been completing challenges on Project Euler since the end of college and recently began completing coding challenges on LeetCode. Part of the reason for starting
As Software Engineers, we tend to have CVs where we explain our experiences and qualifications. However, software engineering is a creative profession; like other creative professions, I think it’s important we too have portfolios. This is my portfolio. Here you can find information about projects I have / am working on, blog entries containing coding challenge write-ups (I’ve been completing coding challenges for over 8 years), as well as links out to my GitHub (see top of the page).