Who I am and how I think.

My Story

My professional path started in existing enterprise codebases. At Atos, I learned how software is built in a team, how to work inside an established process, and how to deliver changes without treating the codebase as a blank slate.

At GOPAS, I worked on a newer version of StoryBoard, a WPF/MVVM desktop application for creating interactive training lessons. The version I joined had an architectural skeleton, capture core, MVVM structure, and database model, but much of the product still needed to be completed: desktop UI, business logic, entity and view-model mapping, import/export, deployment, and long-term maintenance.

Later, at Unicode Systems, I worked on Head Office and Back Office systems for operational business processes. My main focus was backend work in C#/.NET and SQL Server, with React frontend work when features crossed application boundaries.

At Mews, I moved into larger finance-related backend systems in a hospitality SaaS platform. The work involved billing, accounts, payments, reservations, taxes, and fiscalization. Many problems were difficult because they touched production data, accounting correctness, customer configurations, backward compatibility, and gradual rollout.

Today, I am applying the same ideas to AI Factory and AI Coach. One explores how AI agents can participate in a governed engineering process; the other explores personal planning, reflection, habits, and AI-assisted retrospectives.

How I Think

• Understand before changing.
• Solve root causes instead of symptoms.
• Keep business rules explicit.
• Improve processes, not only code.
• Architecture should support long-term evolution.
• Automation should remain understandable and recoverable.
• Documentation should preserve intent, not only implementation.

Current Focus

I am currently building products around autonomous software engineering, personal productivity, journaling, and AI-assisted workflows. I am especially interested in how software teams can make change safer by improving context, validation, documentation, and feedback loops.