I build business applications from the data model to the interface and deployment. My core stack is Laravel, PHP, MySQL, and JavaScript, with hands-on work across WordPress, APIs, cloud operations, and .NET.
I care about the decisions around the code too: clear service boundaries, useful data models, reliable integrations, permissions, deployment, and maintainable handover.
Explore: Selected work · Architecture approach · Experience · Download CV
I am Garth Baker, a South African-born full stack software engineer based in the Netherlands.
My strongest lane is Laravel full-stack engineering: business systems, APIs, admin panels, reporting workflows, billing tools, deployments, and maintainable PHP/MySQL applications.
I am also a senior WordPress developer. WordPress is not my main product focus, but I can use it deeply when it is the right tool: custom builds, theme and plugin work, migrations, troubleshooting, performance fixes, hosting handovers, and client-ready delivery.
I have been building professionally since 2016, with a practical range that covers discovery, wireframes, responsive UI, backend integration, deployment, documentation, and handover.
I like building practical software that earns trust because it solves real operational problems.
Laravel Full Stack
|
Senior WordPress
|
Product Builder
|
Learning Edge
|
Core
PHP Laravel MySQL MariaDB JavaScript jQuery Vue.js HTML5 CSS Bootstrap
WordPress
Senior WordPress WooCommerce Custom plugins Custom themes Migrations
Platforms, Tools & Expanding Range
REST APIs Postman GitHub Actions Docker AWS Linux Apache IIS Flutter Dart C# ASP.NET Blazor Figma
| Project | Engineering focus |
|---|---|
| Budget Kicker | Laravel budgeting and invoicing workflows: relational data, customer journeys, invoice documents, subscriptions, and deployment automation. |
| CoverWeb | Hosting and domain operations: provider API integrations, administration tools, and modular service workflows. |
| Content platforms and developer tools | Private work across a Laravel CMS, structured content, permissions, editor interfaces, and development workflows. |
| .NET applications | Hands-on work with C#, ASP.NET Core, Entity Framework, and SQL Server alongside my primary Laravel stack. |
| Portfolio and CV | Selected work, architecture approach, career history, and a downloadable CV. |
Application source is private. The portfolio describes capabilities at a public-safe level.
| Signal | Detail |
|---|---|
| Professional experience | Full stack development from 2016 onward across Laravel, PHP, WordPress, responsive UI, Flutter, AWS, and client delivery. |
| End-to-end delivery | Comfortable moving from requirements and wireframes through frontend, backend, deployment, documentation, support, and handover. |
| Community footprint | Public Stack Overflow history across PHP, CSS, JavaScript, HTML, WordPress, and Laravel topics. |
| Builder mindset | Product ideas, reusable developer utilities, business workflow tools, and practical automation. |
- Build strong Laravel products with practical business value.
- Keep WordPress as a senior delivery skill for the projects where it wins.
- Turn repeated client/business workflows into reusable systems.
- Improve deployment, automation, billing, reporting, and API integration patterns.
- Grow C#, ASP.NET, and Blazor skill while keeping Laravel as the main strength.
| Area | My Approach |
|---|---|
| Business value | Start with the operational problem and the user workflow. |
| Architecture | Keep the first version understandable, then refactor toward clearer boundaries. |
| UI | Build interfaces that make decisions and next actions obvious. |
| APIs | Keep integrations predictable, testable, and documented enough to hand over. |
| WordPress | Use it pragmatically: fast delivery, clean customization, stable ownership. |
| Maintenance | Prefer code that future me, teammates, or clients can understand. |
These cards are regenerated by GitHub Actions on pushes to
main. They use public repository data only. Private repositories and organizations are not scanned, and repository source code is never written into the README.
| Platform | Link |
|---|---|
| GitHub | github.com/13garth |
| Full CV | 13garth.github.io |
| Blog | GarthBaker.co.za |
| linkedin.com/in/13garth | |
| Stack Overflow | stackoverflow.com/users/8125278/13garth |
| Budget Kicker | BudgetKicker.com |
| CoverWeb | coverweb.online |
Build useful software. Keep improving it.



