Senior Full Stack Developer

PHP has been my core backend language throughout my career. I've worked across multiple versions — from the PHP 5 era all the way through PHP 7 and 8 — so I've seen the language mature significantly and I understand how modern PHP differs from the older patterns. Most of my PHP work is through frameworks like Laravel and CakePHP, but I'm also comfortable with vanilla PHP when the situation calls for it — understanding how things work under the hood rather than just relying on framework abstractions. On the modern PHP side, I'm familiar with features like typed properties, match expressions, named arguments, enums, and fibers introduced in PHP 8. At this point PHP is less of a skill I think about and more just the language I think in for backend work.

Laravel has actually been my primary framework for most of my career. I used it across multiple jobs before my current role, where we're on CakePHP. So I have years of hands-on Laravel experience — APIs, Eloquent, queues, Artisan, the works — and my current CakePHP work just added another framework to the mix.

MySQL is my primary database — I've used it extensively across most of my projects, both through ORMs like Eloquent and CakePHP's ORM, and with raw SQL when I needed more control. I've also worked with PostgreSQL, though less frequently.

I've worked with WordPress on the development side — building and customizing themes from scratch, as well as writing custom plugins. That includes working with WordPress hooks and filters, custom post types, custom taxonomies, the WP REST API, and integrating third-party services via plugins. I'm comfortable with the WordPress template hierarchy and how to structure themes properly, not just drop a page builder on top of a theme.

I have solid Bootstrap experience across multiple versions going back to Bootstrap 3. I've used it professionally on client projects for building responsive layouts, component-driven UIs, and customizing themes via Sass variables. I've seen the evolution of the framework firsthand — from Bootstrap 3's older grid system, through 4's flexbox rewrite, to 5's removal of jQuery dependency. These days Tailwind is my preferred styling approach, but I'm fully comfortable jumping into a Bootstrap codebase and I understand its conventions well. A lot of legacy projects still run on Bootstrap, so that experience is practical.

Tailwind has become my default for styling across projects. I've used it extensively with Vue.js — building responsive layouts, custom component styles, and design systems using Tailwind's utility classes. I'm comfortable with things like responsive prefixes, dark mode variants, and extending the config for custom design tokens. My most recent project, an Applicant Tracking System built with Vue 3 and CakePHP 5, used Tailwind throughout the entire frontend — from layout to form components to data tables.

Git is just part of my daily workflow at this point — branching, merging, rebasing, pull requests, resolving conflicts. I don't think about it much anymore, it's just how I work.

My Shopify experience is on the theme development side — working with Liquid, Shopify's templating language, to customize and build out storefronts for client projects. That includes modifying existing themes, building custom sections, working with Shopify's object model for products, collections, and cart, and integrating third-party scripts and apps into the theme layer. It's a fairly specialized skill set and I've applied it in a professional context, so I'm comfortable navigating the Shopify ecosystem and delivering what clients need on the frontend.

My Node.js experience spans a few different use cases. On the API side, I've built REST APIs using Express, handling routing, middleware, authentication, and connecting to databases. I've also used Node.js for scripting and automation tasks — things like build scripts, data processing, and tooling. And on the full-stack side, it's naturally part of my Next.js work, where Node powers the server-side rendering and API routes. I'm comfortable with async patterns in Node — promises, async/await, and understanding the event loop well enough to avoid common pitfalls like blocking the thread.

I've been working with Vue.js for a while now — both Vue 2 and Vue 3. I've used it to build SPAs, reusable component libraries, and full-stack apps paired with Laravel and CakePHP backends. I'm comfortable with the full ecosystem — Vue Router for navigation and Pinia for state management, and Vuex before that.

I've worked with React and Next.js across both professional and personal projects. My focus has been on building full applications integrated with backend APIs — handling things like authentication flows, data fetching, state management, and dynamic routing. With Next.js specifically, I've leveraged its file-based routing and API routes to keep the stack lean. My primary frontend framework is Vue.js, so I bring a strong component-thinking mindset to React as well — the mental model transfers well, it's mostly syntax and ecosystem differences.

I've used TypeScript both professionally and on personal projects. I'm comfortable beyond just basic typing — I've worked with generics, utility types, and more advanced patterns when the codebase calls for it.

I've worked with Flutter on professional client projects, building full mobile applications that consume REST APIs. That includes working with Dart, building widget trees, managing state, handling navigation, and wiring up HTTP clients to backend services. Flutter's component model actually has some parallels to Vue — everything is a widget, composition is the main pattern — so the mental model wasn't too far off from my frontend experience. I'm not a Flutter specialist, but I'm capable of working in a Flutter codebase and delivering production-ready mobile features.

I've used Laravel Livewire professionally on client work — building reactive interfaces without leaving the Laravel ecosystem. It's a great fit for projects that need dynamic UIs but don't warrant a full Vue or React frontend.