Architecture and business
Translate business rules into explicit models, common paths, and controlled extension points.
Not a chronology of employers
Selected work and impact
These moments show the same method at different scales: find the limit, create a reusable model, keep a live platform stable, and transfer the system so others can continue.
- 1998
The limit becomes a working question
While building an accounting application at home, I increased the data until the application stopped responding. I found the limit before the first client did.
- 2003
ID-first paging
I separated the identification of the page rows from loading their complete data. A business list moved from tens of seconds to under one second in a documented historical case.
- 2004–2007
A reusable application engine
I designed an ASP.NET engine with business objects, explicit actions, XML, XSLT, and integrated paging. The architecture was hosted in SharePoint 2003 and 2007 and used for many business applications.
- 2005–2014
Nine years on one platform
Continuous technical responsibility for the SharePoint and ASP.NET environment of an airline: installation and migration across three SharePoint generations, business web parts, and about ten internal applications built on the same engine, alongside day-to-day production support.
- 2008–2013
Platform continuity during rapid growth
I held primary hands-on technical responsibility for the SharePoint environment used in day-to-day business at Vente Privée: development, administration, deployment, support, patches, training, and production continuity.
- 2018–2021
A platform built to be observed
On my own time: a multi-site ASP.NET MVC platform with one shared core, ten site projects, and a custom view engine so each site overrides only what it needs. Structured logging, dedicated log tables, and audit tables recording changes and deletions were designed in from the start. Five of those sites are still running publicly today.
- 2022–present
A confidential operational platform
Primary technical responsibility for an operational and financial platform in construction and infrastructure. The public description keeps the method and scope while omitting identity, commercial data, and sensitive implementation details.
- 2024–2025
Public institutional work
Three online assessment questionnaires for the Romanian Order of Architects: category scoring, generated recommendations, server-side PDF reports produced from the same views as the on-screen result, and Excel export so the institution works with its own data. Live at locuire.oar.archi.
- 2026
The modernisation lab
A 2011 application rebuilt four times server-side and measured under identical load: three data volumes, first and last page, three paging strategies — 216 requests, one warm-up and three samples per case. Equivalence was verified alongside speed: every implementation returned the same rows. The measurements run on my own synthetic data, never on a client system.
What I bring today
End-to-end technical responsibility
Performance and data
Measure access, processing, combinations, allocations, percentiles, and the final verified result.
Observability
Build logs that explain execution through identities, phases, operations, volume, time, and errors.
Continuity
Prepare code, conventions, tests, and documentation so the organization does not depend on one person.
Long-term ownership changes the quality of the decision. Designing a solution and leaving shows that it can be built. Remaining responsible for years shows whether it survives real data, new requirements, incidents, upgrades, and transfer to other people.