I lead the technical side at TechInsects, and still write most of the code myself.
Nine years in, that means Laravel backends, SaaS architecture and code review most weeks. I started full-stack in PHP and Vue, and added React Native and Flutter when the work called for it, not because the stack was interesting, but because those products had to ship on phones.
For five years I also taught software engineering at IST, alongside the client work. That's the part of my background I'd point to first: it's why I write documentation people can follow, and why I can explain an architecture decision to someone who doesn't write code.
Nine years in, the hard part was never the code.
My master's is in Information Security from NUST, so auth, tenancy and data isolation get settled early rather than patched in after somebody else's audit. Most of what I do now is deciding what a system shouldn't do.
A preventive healthcare platform live on both app stores, running patient records, doctor sessions and an admin portal as one system.
Offline-first farm management for livestock, health records and finances, built on my own time. Live on the web while the Android build is in closed testing.
Four country sites consolidated into one Laravel application and a single admin panel, replacing separately maintained static builds.
FoodClickFood deliveryAug 2025 – Jul 2026Flutter · Laravel · Firebase
EAZ TravelsTravel2026 – PresentLaravel · Filament · LivewireCase study soonShowing 2 of 2
Which one fits depends on what you already have: a team, a spec, or a system that's about to be tested. The scope meter shows how much of a build each one covers.
Drop me into a team that has developers but nobody setting the direction.
From an empty repository to live on both app stores: backend, dashboard and mobile app designed as one system.
A second opinion on what you've built, before the cost of being wrong goes up.
Dots mark single teaching semesters · hover any bar for dates
ISC² CC, the formal side of the security work: access control, network defence and incident response.
Solid backend. Clean APIs. Technical leadership that actually ships. If that's what your project needs, start here. I reply within a day.
I sit at UTC +5, a full overlap with European working hours, and your morning if you are in the US.