Portfolio · Selected projects · Contact
I design, build and modernize business applications, APIs and transactional platforms, combining practical delivery experience with clear architecture, maintainable code and evidence-backed releases.
My work is especially focused on systems where correctness matters: complex business flows, persistence, API contracts, transactional boundaries, idempotency, concurrency, auditability and controlled modernization of existing software.
I prefer repositories that make four things easy to verify: what problem is being solved, where business authority lives, what has actually been tested, and what has not been claimed.
TypeScript · NestJS 12 · React 19 · PostgreSQL 18 · OpenAPI 3.1
A full-product insurance claims modernization case study with a governed API, responsive web journeys and provider-real validation.
- 90 REST operations across 76 paths and 16 operation families
- 22 productized web surfaces
- runtime reconciliation at 90/90
- OpenAPI + Postman contract governance
- JWT + RBAC, Argon2id, idempotency, concurrency controls, RFC 9457 and durable audit correlation
➡️ Explore InsuranceClaims
🌐 View the case study in EliasWorks
Laravel 12 · Livewire 3 · PostgreSQL · Filament 3 · Tailwind CSS
A complete e-commerce and business-management platform for a pastry shop, already deployed and functional.
It combines public catalog and checkout flows with back-office management for products, inventory, customers, sales, expenses, PDF invoicing and operational reporting.
🌐 Visit DulceHogar
🔒 Private repository · public production demo available
Kotlin · Jetpack Compose · Room · CameraX · ML Kit
A completed Android diagnostic tool that I currently use on a physical device for analyzing iPhone panic logs.
The app normalizes logs, extracts metadata and evidence, classifies panic families, applies diagnostic rules, ranks candidates, persists history locally and supports versioned JSON Rule Packs with validation, import and restore workflows.
🔒 Private repository · v1.0 completed and in real use
C# · .NET 10 · ASP.NET Core · EF Core · PostgreSQL · MySQL
A brownfield modernization of an electronic-invoicing and transactional-sales platform for Uruguay.
The work focuses on explicit Domain, Application, Infrastructure and Web API boundaries, provider-neutral persistence, transactional safety, idempotency, auditability, outbox workflows and controlled evolution of legacy behavior.
PHP · WordPress · WooCommerce · JavaScript · UI/UX
A real-world commerce modernization focused on mobile-first purchasing, cart clarity, locality and delivery flows, and safe evolution of an existing WordPress/WooCommerce platform.
➡️ Explore the repository
🌐 Visit ZoFloridane
- Backend & APIs: business rules, REST APIs, integrations and persistence
- Architecture: Clean Architecture, Ports & Adapters and explicit boundaries
- Legacy modernization: controlled migration without casually breaking working behavior
- Transactional systems: idempotency, concurrency, rollback, audit and outbox patterns
- Mobile applications: native Android with Kotlin and Jetpack Compose
- Frontend integration: React, Livewire and API-authoritative workflows
- Delivery quality: automated tests, CI/CD, exact-commit verification and release governance
Backend
C# · .NET · ASP.NET Core · PHP · Laravel · TypeScript · Node.js · NestJS
Frontend & mobile
React · TypeScript · JavaScript · Livewire · Kotlin · Jetpack Compose · WordPress · WooCommerce
Data
PostgreSQL · MySQL · SQLite · Room · Entity Framework Core · Prisma
Architecture & delivery
Clean Architecture · Ports & Adapters · REST · OpenAPI · GitHub Actions · Automated Testing · CI/CD
Understand the domain before coding.
Keep business authority in the correct layer.
Put external systems behind replaceable boundaries.
Make critical writes transactional.
Make retries safe.
Test negative paths, not only happy paths.
Tie CI evidence to the exact reviewed commit.
State limitations as clearly as capabilities.
🌐 Portfolio: eliasworks.uy
📧 Email: luisitohe@gmail.com
💻 GitHub: @LuisHdezE
Project descriptions are intentionally bounded to capabilities already implemented and evidenced in the referenced repositories.

