I design and build business software with a focus on .NET, React, Angular, and service-oriented systems.

My current work sits across three active workspaces:

• private product and client systems
• public reference repositories and reusable code
• an engineering lab for notes, system design, and operational guidance

• full-stack commerce systems with a React storefront, Angular backoffice, and .NET microservices
• business applications for onboarding, invoice workflows, calendars, student management, and internal operations
• integration-heavy backend systems, including SAP Business One related work and service-to-service communication
• engineering documentation that explains architecture, delivery flow, troubleshooting, and operational standards

• C# and .NET application design
• service boundaries, domain modeling, and long-term maintainability
• React and Angular application structure for business-facing products
• data integrity, validation, and failure handling
• turning messy projects into flatter, clearer, easier-to-maintain repositories
• writing practical documentation for developers, maintainers, support, and technical leadership

I work at the level where feature delivery is only one part of the job.

I also care about:

• service contracts and ownership
• error handling and common behavior across services
• local development flow and deployment readiness
• operational clarity through logs, metrics, and documentation
• architectural decisions that still make sense after the codebase grows

• olih-app: a unified application repository with a .NET backend API and a React web client
• engineering-lab: a living knowledge base for engineering notes, platform guidance, system design, and development practice
• sap-b1-service-layer: a C# client library for SAP Business One Service Layer integrations
• data-cockpit: a reusable .NET CRUD-focused library built around shared data access patterns

Some of my strongest work is private, but the themes are consistent:

• commerce and ordering workflows
• identity, gateway, inventory, payment, and saga-style coordination
• business partner onboarding and import pipelines
• enterprise integration and operational support tooling

• keep the structure flat when possible
• choose names that are easy to read and hard to misunderstand
• remove placeholder code, dead notes, and accidental complexity
• prefer stable systems over impressive-looking diagrams
• document the parts that other engineers actually need to operate and maintain

• backend projects with clearer boundaries and practical .NET patterns
• frontend projects focused on maintainability, form workflows, and admin-style product experiences
• repository cleanups that improve naming, layout, and documentation quality
• technical notes that explain not only what the code does, but how the system should be run and supported

• improving repository quality and portfolio clarity
• raising the standard of documentation and operational readiness
• refining reference systems that other developers can study and learn from
• building systems that are realistic, teachable, and maintainable

• The public repositories linked from this profile are shared for learning, technical review, and knowledge sharing.
• No permission is granted to copy, reuse, modify, redistribute, sublicense, sell, deploy, or republish that work without prior written approval from the repository owner.
• See LICENSE, DISCLAIMER.md, CONTRIBUTING.md, and CODE_OF_CONDUCT.md.