About

I'm an electronic systems engineer learning to code by building functional software with AI collaboration.

My approach: Build clear requirements first, then ask AI to coach me through the implementation. I treat code like I treated complex electro-mechanical platforms - understand the system, identify what needs to change, troubleshoot when it breaks. Started with multimeters and oscilloscopes fault-finding analogue circuits, now it's console logs and error messages debugging React components. Same logical process, different domain.

My coding journey started when I saw someone clone Pong and asked ChatGPT: "Could I do that?" The AI's proposed solution was too technical; assumed knowledge I didn't have. When I explained this, it offered to break it down into steps. That 14-step coaching plan walked me from zero to building the game. That's when I understood: I don't need deep coding skills if I can articulate problems clearly and learn from what AI generates. Setbacks become the learning-obstacles inform the path forward.

Background: Army engineering (REME), rugby coaching, business analysis. Common thread: take complex systems, understand what matters, build solutions that work.

Current projects focus on tools for volunteer rugby coaches - session planners, player rotation managers, reflection frameworks. Real problems, real users.