Application foundation
The default runtime baseline for serious Laravel products: modern PHP, current Laravel, strict static analysis, and language features that keep business code explicit.
Chosen for long-lived maintainability before convenience.
Technical Skills — PHP 8.5 & Laravel 13 Stack
Tools I use every day and why.
Modern PHP and Laravel tooling selected for correctness, clarity, performance, and production behavior.
Default stack standard
Production stack, grouped by operational responsibility.
Each block maps a technical area to the tools and decision rules I use before a Laravel system reaches production.
Laravel backend services
Framework services selected for observable production behavior: queues, broadcasts, API auth, search, billing, feature flags, code style, and automated test feedback.
Everything is added because it earns its operational cost.
Data layer
Datastores I use when the product shape justifies them, with PostgreSQL and Redis as the usual default for transactional systems and queue-heavy applications.
Schema, indexes, cache keys, and query plans are part of the design.
Infrastructure and delivery
Deployment and observability tools that keep releases repeatable, rollback paths visible, and production issues diagnosable without guessing.
Local, staging, and production should behave like the same system.
Architecture standards
Patterns I reach for when complexity demands a name and a boundary, not ceremony for its own sake.
The architecture has to help the next developer make a safe change.
Quality gates
Automated checks that keep changes reviewable before they reach production, with fast local feedback and stricter CI enforcement where it matters.
The standard is simple: prove behavior, measure risk, then deploy.