Notes on development, infrastructure, security, and what's worth shipping.
// featured
FEATURED
I default to Laravel for backends because the docs are excellent, the core stack is mostly first-party, and my dependency tree stays easier to reason about than a typical npm micro-package pile—without pretending PHP is immune to supply-chain attacks.
Read Full Article →// filter
Mobile Development
Jul 19, 2026
Flutter is my default for iOS and Android because Google built it for one codebase across platforms—and it pairs cleanly with a Laravel API. Includes toolchain steps and honest tradeoffs.
Read Article →
Laravel
Jul 18, 2026
Follow-along: Sanctum API, versioned routes, Form Requests, API Resources, and a Flutter token client—ownership rules that keep products maintainable.
Read Article →
Laravel
Jul 17, 2026
Install broadcasting/Reverb the modern way, start the server, broadcast events, wire Echo, and deploy with a reverse proxy—plus when Node is still the better fit.
Read Article →
Laravel
Jul 16, 2026
install vs update, commit the lockfile, MFA on publishers, and a post-incident checklist—with real Packagist / laravel-lang references.
Read Article →
Laravel
Jul 15, 2026
Practical scale: kill N+1s, add indexes, queue heavy work, cache hot paths, and measure before you rewrite.
Read Article →
Mobile Development
Jul 13, 2026
A practical decision matrix for Flutter vs React Native—updated for how both ecosystems actually ship today, without tribalism.
Read Article →