Expertise
Disciplines, told as craft.
No percentage bars — skills aren't quantities. Each discipline is described by what it means in practice and the principles that guide it.
- 01
Full-stack engineering
From schema to pixels.
Designing and building complete products — data model, API, interface, and deployment — as one coherent system.
- Next.js
- React
- TypeScript
- Node.js
- Express
- NestJS
- Laravel
- Vue
- PHP
- Python
- FastAPI
- Flask
Principles
- Own the whole path from request to render
- Make the happy path boring and the failure path clear
Works closely with: APIs · Databases · Systems architecture
See it in projects - 02
Systems architecture
Shapes that survive change.
Choosing boundaries, contracts, and trade-offs so a system can grow without being rewritten.
- Monorepos
- Strangler migrations
- Multi-tenancy
- RBAC
- Audit logging
- WebSockets
- MCP
Principles
- Draw the boundaries before the boxes
- Prefer reversible decisions
Works closely with: APIs · Cloud & infrastructure · Enterprise integrations
See it in projects - 03
APIs
Contracts people can trust.
Designing clear, versioned, well-documented interfaces between systems and between teams.
- REST
- WebSocket
- JWT / refresh cookies
- Zod
- Sanctum
- Webhooks
- OpenAPI-style docs
Principles
- Be conservative in what you send
- Errors are part of the contract
Works closely with: Full-stack engineering · Enterprise integrations
See it in projects - 04
Databases
Data that stays true.
Modelling, migrating and tuning relational data so it remains correct as requirements evolve.
- MySQL
- Oracle (read-only integration)
- SQLite
- Prisma
- Eloquent
- Migrations
- ChromaDB (vectors)
Principles
- Constraints are documentation that executes
- Migrate forward, always with a way back
Works closely with: Full-stack engineering · Systems architecture
See it in projects - 05
AI automation
Intelligence with guardrails.
Applying language models, retrieval and agents to real workflows — observable, bounded, and honest about limits.
- Ollama (local LLMs)
- Anthropic API
- ChromaDB
- Sentence-Transformers
- RAG
- Gmail / WhatsApp automation
- Python
Principles
- Automate the tedious, keep humans on the decisions
- If you can't observe it, you can't trust it
Works closely with: Computer vision · Enterprise integrations
See it in projects - 06
Mobile development
Software that travels.
Mobile applications that stay fast, offline-tolerant, and pleasant to use one-handed.
- Flutter
- Firebase Cloud Messaging
- Mobile APIs
- PWA / service workers
Principles
- Design for the worst connection
- Thumb reach is a layout constraint
Works closely with: APIs · Full-stack engineering
See it in projects - 07
Cloud & infrastructure
The ground beneath.
Running services reliably: reverse proxies, process supervision, TLS, backups, and observability.
- Linux
- Nginx
- PM2
- systemd
- Let's Encrypt
- Docker Compose
- cron
- NAS backups
Principles
- Automate the deploy, rehearse the rollback
- Least privilege everywhere
Works closely with: Networking · Systems architecture
See it in projects - 08
Networking
Packets, paths, and policy.
Understanding how traffic actually moves — DNS, TLS, proxies, firewalls — so failures are diagnosable.
- WebRTC
- Reverse proxies
- TLS
- Relay / signalling servers
- 09
Enterprise integrations
Making systems talk.
Connecting ERP, HR, finance and operational systems with reliable, auditable data flows.
- Tally (HTTP/XML)
- Oracle ERP via MCP
- Google Workspace APIs
- Excel / CSV pipelines
Principles
- Idempotency first
- Reconcile, don't assume
Works closely with: APIs · Systems architecture · AI automation
See it in projects - 10
Computer vision
Teaching software to see.
Turning camera and sensor streams into structured, privacy-aware information.
- OpenCV
- face_recognition
- Python
- Geolocation checks