I build the software a business actually runs on. Most of that has been full stack work in Laravel and PHP, with Vue, React and Next.js on the front of it, and a stretch of backend work in Java and Spring Boot on banking systems. The common thread is not a framework. It is that the systems have accounting in them, or money moving through them, or an operations team depending on them being correct on a Monday morning.
Right now I am the sole engineer on a multi-tenant ERP built to onboard more than 50 client tenants, replacing a legacy Microsoft Access system that a business had outgrown. Accounting, inventory, purchasing, sales, production, banking, permissions and reporting are all mine, from the schema up.
How the work got here
It started with client sites. Freelance Laravel work through 2022 and 2023, taken from the first conversation to handover with nobody else on the build, while I finished an Advanced Diploma in Software Engineering at Aptech.
Planet01 was the long chapter. I joined as an intern in February 2023 and left in June 2025 as a full stack developer. The main thing there was CTA World, a logistics platform I was the sole developer on: a Laravel superadmin portal and API with three separate Vue.js dashboards on top of it, real-time chat, and Stripe and PayPal for billing. Alongside it were a rider operations dashboard for Domino's, a catering platform end to end, and the frontend for a cryptocurrency trading platform. I also trained two interns.
Vaulsys was the banking year. Java, Spring Boot, Vaadin and Hibernate against Oracle, on financial infrastructure behind NayaPay, Pakistan's largest payment application, and then on the delivery team for RawBank, the largest bank in the Democratic Republic of Congo. Payment and cash flow modules, KYC workflows, payment gateway integration, and the production debugging that comes with systems where being wrong is expensive.
NatureTech is the ERP. It is the first system I have owned completely, and it is the one that pulled everything before it together: the Laravel from the client years, the correctness habits from the banking year, and the business side of a Bachelor of Business Information Technology I am taking alongside it.
How I work
I am comfortable owning a system end to end, which in practice means designing the schema, writing the business rules, building the screens, and then being the person who fixes it at four in the afternoon when an accountant finds an edge case in the ledger.
I prefer one general solution to nine special cases. On the ERP that shows up as a generalised CRUD controller every module is built on, so adding an entity costs a configuration rather than a controller. On the banking work it showed up as reading the data before writing the fix.