Current work
Dumadine
Multi-tenant hospitality system built for live venue operations across ordering, kitchen flow, inventory, and accounting.
Senior software engineer focused on scalable product systems
I build production software that stays workable as systems grow.
I work across frontend, backend, data, and delivery with a focus on maintainability, reliability, and clear system structure. The goal is not just to ship features. It is to keep products moving without the codebase collapsing under its own weight.
Current focus is Dumadine, a multi-tenant hospitality platform covering ordering, kitchen operations, inventory, and accounting workflows shaped around real operational use, not demo-friendly assumptions.
Strongest areas: React and TypeScript applications, Node.js APIs, PostgreSQL-backed systems, and delivery foundations that hold up under ongoing product pressure.
Engineering stance
System health drives delivery speed
Most teams do not slow down because they lack ideas. They slow down because the system becomes harder to change.
AI usage
Used to reduce drag, not replace ownership
I use AI to accelerate exploration, drafting, refactoring, and review support. Architecture, tradeoffs, correctness, and production accountability stay with me.
Where I am strongest
Shipping once is easy. Keeping the system usable after that is the real work.
Maintainable architecture
Designing boundaries that stay understandable, testable, and changeable as the product grows.
Scalable frontend systems
Building React and TypeScript applications with disciplined structure across state, data flow, and UI so feature work does not decay into churn.
Backend reliability
Building APIs and workflows with strong operational behavior, failure awareness, and recovery paths from the start.
End-to-end delivery
Working across application code, infrastructure, CI/CD, and operational tooling so systems hold together beyond isolated feature work.
Working stack
Tools are useful. Judgment is what keeps them from becoming a pile of disconnected choices.
This is the current working surface, not a ceiling. I can pick up new tools quickly when the requirements justify them, but I do not treat tool count as proof of engineering quality.
Frontend
-
React -
Vue -
TypeScript -
Next.js -
Astro -
Vite -
Tailwind CSS v4 - shadcn/ui
- Design tokens
-
Figma - TanStack Query
-
Zustand - Jotai
-
Redux
Backend and data
-
Go -
Node.js -
PHP -
Express - REST APIs
-
OpenAPI -
PostgreSQL -
Prisma - Drizzle ORM
-
Redis - WebSockets
Platform and delivery
-
Docker -
Terraform -
GitHub Actions - CI/CD
- Render
-
Cloudflare -
AWS ECS, S3, RDS, ECR, EC2, Route 53 -
Azure ADF, ADLS -
Grafana -
Prometheus - Loki
- Resend
- Mailchimp
AI tools
- ChatGPT
- Codex App
- Claude Code
- Cursor
- OpenClaw
- OpenRouter
- CodeRabbit
Testing and verification
-
Vitest -
Playwright - Go test
- API integration tests
- Snapshot tests
- Regression checks
Architecture
- Feature-based architecture
- Modular systems
- Layered / Clean architecture
- Monorepos
- Event-driven flows
- Observability
- Scalable frontend systems
Selected proof
A smaller set of work with enough substance to evaluate.
I would rather show fewer projects with real constraints, technical decisions, and operational shape than a long list of shallow summaries.
- Unifies POS, QR ordering, kitchen operations, inventory, and accounting in one browser-based product.
- Supports different venue models across cafes, hotels, and workspaces without splitting the platform into separate forks.
- Built around modular domains, real-time workflows, and production observability needed for ongoing operational change.
What you will find here
Current work, selected projects, and how I approach engineering.
This site is meant to show what I am building, how I think, and what kind of engineering work I do best.
- Now: what I am actively building and improving
- Work: selected projects with enough detail to judge scope and execution
- Workflow: how I structure delivery and use AI without giving up engineering ownership