About / My Journey

The Teacher

Before I became a software developer, I worked as a private tutor during my school years. This experience taught me something important: if I could not explain an idea clearly, I had not understood it well enough myself.

• Making complex ideas clear to others — this habit moved from classrooms to code, documentation, and technical discussions
• Writing documentation so the next person inherits good judgment, not just code syntax
• Mentoring as a long-term commitment — even during periods when my own financial situation was uncertain

The Entrepreneur

In 1998 I founded MobyDick Coaching Center — my first formal education and coaching business. I ran the centre directly for about two years, then stayed involved for another two years before leaving. When I departed, I received my full ownership value and share — I left with my integrity intact, not because I had failed.

• Integrity matters more than ownership — and long-term trust matters more than quick profit
• I have left other successful businesses when staying would have required me to compromise my principles
• Entrepreneurship taught me to take responsibility before it taught me to write code

The Engineer

For me, technology has always been a tool for solving real problems — not a way to define who I am.

• Work across hardware, web development, system architecture, and human–AI collaboration — I remain accountable for what ships; AI assists me
• PHP and platforms including CakePHP, CodeIgniter, Laravel, Joomla, Drupal, WordPress — plus HTML, CSS, and JavaScript
• Professional roles at Quantum Cloud and Win-Win Service Provider, where I continue product and practice work today
• Early training in proper analysis and database design — data integrity as the foundation for everything built on top of it

The Software Architect

Across more than 150 projects — combining freelance and in-house work — I progressed from delivering solutions to designing them.

• International remote work with clients in Australia, Canada, Singapore, the United Kingdom, and other countries
• Recording architecture decisions as contracts with users and with future development teams
• Separating related concepts honestly — for example, keeping identity separate from profile, or business events separate from ledger entries
• Stabilising inherited systems, building new systems from scratch, and maintaining long-running products with direct accountability

The Product Builder

Product work focuses on systems that stakeholders can trust — when a system reports ownership, access, or financial information, that information must be correct.

• GrowSharely — one recent reference product under Win-Win Service Provider — one example of work across a career that includes education, finance, distribution, and enterprise systems
• Project work from 17 June 2026 onward: building foundations first, recording architecture decisions, and maintaining handbook documentation alongside the code

WINWINSP — Practice founder

WINWINSP (Win-Win Service Provider) is the engineering practice I have built from real product delivery. It includes philosophy, standards, lessons learned, and documentation structures — so each new product starts from proven habits rather than rediscovering the same lessons.

• Consulting experience, documentation discipline, and product delivery — all working together
• This website is the public summary of that practice; private working notes are not published here

Where I Am Today

I work at the intersection of architecture, product delivery, and reusable engineering practice. I continue to write documentation, teach through conversation, and build products that operators can explain clearly to their stakeholders.

Business capabilities I have developed across my career — including share and financial management, education, communication systems, and enterprise operations — are summarised on Solutions. Engineering Philosophy describes how I think. Knowledge & Publications covers books, handbook material, and lessons.

Professional Identity

Alongside hands-on technical work, I hold leadership responsibilities in some organisations. Those roles inform my judgment, but they do not define this professional profile.

Software Architect · Product Builder · Mentor — that is how I introduce myself professionally.