Core backend
Primary production stack: PHP / Laravel. Additional production depth: Node.js / TypeScript, and Python on Odoo.
- PHP
- Laravel
- CodeIgniter
- Node.js
- Express
- JavaScript
- TypeScript
- Python
- REST APIs
- GraphQL
- Laravel Horizon
Technical capability
Backend technologies I use in production
My deepest production stack is PHP and Laravel, with additional production experience in Node.js and TypeScript. I also work on the frontend when a feature crosses the API boundary.
Data stores
Databases and search used behind production services.
- MySQL
- PostgreSQL
- MongoDB
- Redis
- Elasticsearch
- Sequelize
Integration and architecture
How services exchange data, and what keeps that correct when a provider does not cooperate.
- Webhooks
- Data synchronization
- Data normalization
- Retries
- Idempotency
- Reconciliation
- CRM Systems
Payments and third-party platforms
Payment providers and external systems integrated in production.
- Stripe
- Midtrans
- Salesforce
- Odoo
- Firebase
- Trello API
- GitLab API
Cloud and deployment
I've provisioned AWS and Google Cloud compute, configured Debian/Ubuntu, and deployed applications with Docker or a native PHP runtime. I've also set up GitLab Runner to build and deploy applications automatically after merges.
- Docker
- AWS
- AWS Lambda
- AWS S3
- Cloudflare
- Cloudflare R2
- Google Cloud Platform
- Linux
- Debian
- Ubuntu
- GitLab CI/CD
- GitLab Runner
Evidence
Monitoring
Tools used to investigate errors, releases, and production behavior.
- Datadog
- Sentry
- New Relic
Testing and code quality
Testing depends on what the codebase has. On Leadplus, PHPUnit tests were routine ticket work across adapters, GraphQL mutations, and sync and dedupe commands, with provider APIs mocked and the pipeline requiring tests and PHPStan to pass before merge. Funraisin runs on CodeIgniter 3 with no automated test suite, so there I verify changes by reproducing the issue on demo and bugfix branches and attaching before-and-after evidence to the ticket.
- PHPUnit
- PHPStan
Mobile and desktop
Client applications built against APIs I also worked on.
- Dart
- Flutter
- Electron
Full-stack capability
Frontend work used to complete features that cross the API boundary.
- React
- Vue
- Next.js
- Blade
- jQuery
- Bootstrap
- Tailwind CSS
How this site verifies itself
A Playwright smoke suite runs against a production build of this site. It checks:
- Every page renders its title, description, and canonical URL without a console error
- Every social preview image is a real 1200 by 630 PNG, checked from the file header
- The résumé PDF is A4 with no Type 3 fonts, which older ATS parsers misread
- Every page fits a 320px screen without horizontal scrolling
- The diagrams enlarge and scroll by keyboard, and the copy-email button announces success or failure once
Exploration, not production depth
I'm currently exploring Go and Rust, but they're not included above because I haven't used them in production yet.