About

I’m a Mechanical Engineer based in Australia, with over seven years’ experience leading reliability, maintenance, and capital projects across underground mining — spanning uranium, copper, and gold operations in the Northern Territory and Queensland.

My formal training includes a dual Bachelor of Engineering (Honours) and Bachelor of Science, majoring in Mechanical Engineering and Mathematics, from James Cook University, and more recently a Graduate Diploma in Finance from Griffith University. Outside of formal study, I’ve always had a strong interest in software development, data analysis, and programming.

I started this site to document some of the projects I’ve worked on, along with the broader interests that keep me curious outside the day job. My hope is that something here sparks an idea for you (the reader), or helps you make progress on a project of your own.

Engineering & Reliability.

Most of my career has centred on keeping critical infrastructure running — and running well — in some demanding environments. That’s meant a lot of time spent on root cause analysis, asset strategy, and capital projects where the cost of getting it wrong is measured in days of lost production. I’ve led teams through major shutdowns and emergency events, designed reliability improvements for fixed and mobile plant, and worked across the full lifecycle of mine infrastructure projects, from concept through to commissioning.

I also enjoy the more technical, modelling-heavy side of the discipline — structural assessments, FMECA-based asset strategies, and increasingly, using open-source simulation tools like OpenFOAM (CFD) and CalculiX/Code_Aster (FEA) to explore problems outside the constraints of a commercial licence.

Finance.

Since completing my Graduate Diploma in Finance, I’ve developed a genuine interest in both fundamental and technical analysis of traded assets. Engineering and finance overlap more than people often expect — project costing, net present value, and building the business case for capital expenditure all draw on the same underlying skill set.

My personal interest leans toward the statistics and machine learning side of market forecasting — a problem that’s notoriously difficult to solve well, even for people who do it full-time as a profession. I track my own trading activity and experiment with automated strategies, partly out of curiosity and partly in the (admittedly long-odds) hope of one day making work optional. I wouldn’t bet on it, but it’s a fun problem to chip away at.

Analytics & Numerical Modelling.

I’ve always enjoyed mathematics — enough that I extended my undergraduate degree by a year to pick up a major in it. There’s something genuinely satisfying about watching an analytic expression that describes the world around us get broken down into something a computer can actually compute. More than a decade after starting university, that process still hasn’t lost its appeal.

I particularly enjoy working in computational fluid dynamics, discrete element methods, and finite element analysis — partly for the engineering applications, and partly because the underlying numerical methods are interesting in their own right.

Statistics, Machine Learning & Data Analysis.

My interest in statistics and data analysis started with my first university course in the subject and has stuck with me since. I’m always looking for an excuse to apply it — most often to finance and real estate, where there’s no shortage of data, and no shortage of bad assumptions worth testing.

Automation & Software.

I subscribe to the idea that the difference between a good tradesman and a great one is that one never blames his tools — and the other makes his own. For an engineer, that toolset lives mostly in software rather than hardware, but the principle holds.

My goal with automation and software isn’t just to be a good engineer, but a great one — by building the tools that solve the problems I actually face, and that make the rest of the work faster. In practice, that’s meant a fair amount of time in Linux (NixOS, specifically), Python, C++, and Emacs, building out a development environment and a set of personal tools I keep iterating on.

Disclaimer.

Feel free to use anything you find on this site — code, ideas, or otherwise — but I can’t offer any warranties or take responsibility for what you do with it. Use at your own risk.

If you have an idea you’d like to share, want to collaborate, or think I could help with something you’re working on, get in touch via the Get in Touch link in the main menu. I’d love to hear from you.