Software Engineer in training, currently working across Java, Python, and JavaScript; with a habit of turning motorsport data into side projects.
A client-side race analysis tool for comparing driver lap times, sector splits, and stats from raw CSV data, built as a single-page app with interactive multi-driver charting.
A tool for organizing coursework and assignments across a two-year learnership programme, keeping track of what's due, what's done, and what's next.
Worked as Lead Researcher on a group workshop project, coordinating findings and deliverables across the team.
Comfortable translating technical work into plain-language explanations, including for peer review contexts.
Self-directed across multiple learning tracks (web, Python, and Java), adjusting approach as tools and requirements shift.
Balances structured coursework with independent side projects on a consistent basis.
Project-first learner: builds working tools first, then revises the underlying logic for correctness and clarity.
Comfortable diagnosing environment and dependency issues, from PATH conflicts to SSL certificate errors.
Works with structured data: CSV parsing, statistical functions, and relational database design.
Applies structured design-thinking methodology to real project and assessment work.
I'm currently in a two-year Software Development learnership, working through Java, Python, and web development while building projects on the side; usually with an F1 or motorsport angle, since it's the domain that keeps me interested enough to actually finish things.
I like learning by building rather than just studying: if there's a working version, however rough, I'll refine it from there.