Hi, I'm Kamlesh Paul — a lead software developer who spends most of his time in Laravel and Next.js codebases, and writes down whatever was annoying enough to be worth documenting.
- published articles
- 43
- topic areas
- 3
- writing here
- since 2024
What I Do
I build and ship web applications end to end: database schema, API layer, front end, and the deployment pipeline that puts it all on a server. Most of my professional work sits in the Laravel/PHP and Next.js/TypeScript ecosystems, with a lot of time spent on the unglamorous parts — queues, background jobs, CI pipelines, zero-downtime deploys, and self-hosting on plain VPS boxes instead of managed platforms.
Why I Write Here
Almost every article here started as a problem I hit in real work. When the answer took me three hours of scattered docs, GitHub issues, and trial and error to piece together, I write it up so the next person spends ten minutes instead. That's also why the tutorials lean heavily on complete, copy-pasteable configuration rather than fragments — the missing detail is usually where people get stuck.
What I Write About
Laravel & PHP
Queues on constrained hosting, FrankenPHP and Octane, passkeys and authentication, scheduled backups, API documentation, and packages worth adding to a real project.
Next.js & React
App Router patterns, server actions, WebAuthn, push notifications, background jobs with BullMQ, and the SEO details that are easy to get wrong.
Deployment & Infrastructure
Self-hosting on a VPS, Docker rollouts, GitHub Actions pipelines, zero-downtime deploys with PM2, SSL setup, and hardening a server against the usual noise.
Developer Tooling
Editor setup, managing multiple Git identities, open-source alternatives to paid tools, and small workflow improvements that compound.
Editorial Standards
A tutorial is only worth reading if you can trust it. These are the rules I hold myself to:
- Every tutorial is written against code I actually ran, not paraphrased from documentation.
- Version numbers are stated explicitly, because a Laravel 10 answer often breaks on Laravel 12.
- Posts carry a published date and, where the stack has moved on, an updated date.
- When something is a workaround rather than a recommended practice, the post says so.
- Corrections are made in place. If a reader points out a genuine error, the article gets fixed.
Tech Stack
Connect
Corrections, topic suggestions, and work enquiries are all welcome — the contact page explains which channel suits which.
Start reading
43 articles on Laravel, Next.js, and deployment.