Do you write React or Vue?

I will write Vue or React when the application is a true SPA. For most server-rendered applications with interactive bits, Livewire 4 + Alpine + Flux 2 is the right answer — one engineer, one stack, one deploy. If you tell me what the application is doing, I will say honestly which stack matches.

Are you available freelance?

Yes — one engagement at a time, fully present. Full-stack engagements typically run 2-6 months because the surface is broader than a backend-only or frontend-only engagement.

What is your hourly rate?

Bespoke, scoped per engagement, written into SOW before contract. Full-stack engagements are typically priced as fixed-scope-per-phase rather than hourly.

Do you do design as well as code?

I do practical design — palette, typography, component vocabulary, responsive layout — within the engineering engagement. I do not do brand identity or marketing-site visual design; for those I partner with a brand designer the buyer brings to the engagement.

Will I get the source code?

Yes — in a Git repository you control, deployed to hosting the team chooses. There is no lock-in to my infrastructure. The handover runbook documents how to deploy and operate without me.

Full-Stack PHP Developer | Laravel + Livewire

Full-Stack PHP Developer — Laravel 13 + Livewire 4 + Tailwind 4

A full-stack PHP developer builds both the server-side and the client-side of a web application — backend, database, API, frontend, deploy — all from one engineer. I work as a senior full-stack PHP developer on the Laravel 13 + Livewire 4 + Flux 2 + Tailwind 4 + Pest 4 stack. Single principal, end-to-end, no handoff between backend and frontend teams because there is no team — there is one engineer who scopes, builds, deploys, and supports.

What "full-stack" actually means in 2026

The "full-stack developer" title gets overloaded. Some agencies use it to mean "the contractor who will write whatever we throw at them". I use it more narrowly: backend (Laravel 13 + PHP 8.4), database (PostgreSQL / MySQL / SQLite), frontend (Livewire 4 + Flux 2 + Alpine + Tailwind 4), API (Sanctum REST or GraphQL), deploy pipeline (Forge / Vapor / custom), test suite (Pest 4), CI (GitHub Actions or GitLab CI). Not React, not Vue, not a separate SPA framework — Livewire 4 + Alpine + Flux is the right answer when one engineer is doing both halves and the page-shape is form-heavy.

My stack — Laravel 13, Livewire 4, Flux 2, Tailwind 4, Pest 4

Laravel 13. Eloquent, Blade, queues, schedulers, Fortify, Sanctum.
Livewire 4. Reactive components without a JavaScript build for the form-heavy admin surface most internal apps need.
Flux 2. First-party UI vocabulary that matches Livewire 4's component story.
Tailwind 4. CSS-first config via @theme; no separate tailwind.config.js.
Pest 4. Feature and unit tests, browser tests where the surface justifies them, Pint-enforced style.

Frontend without React — why Livewire + Alpine + Flux is the right answer

Most buyers I see hiring a "full-stack developer" hire two halves of an engineering team — one Laravel backend developer, one React frontend developer — and pay for the handoff between them. Livewire 4 + Alpine + Flux 2 collapses that handoff back into one engineer for the page shapes Livewire is good at (forms, admin surfaces, internal tools, dashboards, table-and-detail flows). React is the right answer when the application is a true SPA (Figma, Notion, Linear). Livewire is the right answer when the application is server-rendered with interactive bits — which is most internal applications.

Who hires me as a full-stack PHP developer

SaaS founders building an internal admin surface and an external customer-facing application by the same engineer (same data model, same deploy, same test suite). Agencies needing a senior to anchor a Laravel + Livewire build behind their account-management surface. Operations teams whose internal tools live in a 2018-era PHP application that needs a refresh by someone who can do all of it.

How a full-stack engagement is scoped

Same shape as the Laravel and PHP pages: scoping call, written specification, two-week sprints, Pest tests alongside features, handover with runbook and 30-day support window. The full-stack flag changes one thing: the deploy pipeline (Forge / Vapor / custom server) is part of sprint zero, not bolted on at the end.