Let's talk ↗It moved from understanding how systems break, to building them, delivering independently, creating products, founding a company, and solving open-ended problems across business and technology.
The journey started close to software quality: understanding expected behaviour, finding failure points, and learning that reliable products begin with careful questions—not assumptions.
Moved closer to product creation and implementation, turning an understanding of how software fails into a stronger instinct for how it should be designed and built.
Built experience inside an enterprise environment where dependable delivery, collaboration, maintainability, and the realities of production systems matter as much as the code itself.
Expanded across engineering and automation work, contributing to APIs, systems, and workflows while learning to connect implementation choices to measurable operational outcomes.
Worked directly with real clients and businesses—translating open-ended needs into focused web products, making practical technical decisions, and carrying work through to delivery.
Created an anonymous student community experience, connecting product thinking, user needs, interface decisions, and full-stack implementation in one self-directed build.
Crossed from engineering execution into company and product ownership—making architecture, product, business, prioritisation, and delivery decisions across the complete lifecycle.
Now working at the boundary of business, product, engineering, AI, cloud, and delivery—taking ambiguous problems, aligning stakeholders, and owning the path to a working production solution.
Each chapter added a new layer: quality, engineering, enterprise delivery, independent ownership, product judgment, founder empathy, and confidence in ambiguous environments.
Start a conversation ↗