Systems that run, code that breathes, and decisions that make sense.
With nearly 15 years of hands-on experience, I’ve worked across stacks, platforms, industries, and weird edge cases.
Below are not just tools I’ve used — but spaces where I’ve delivered. I’ve outgrown tutorials. I build from understanding.
✅ Back-end architecture
I build systems that stay reliable under stress. From legacy cleanups to real-time APIs.
- PHP, C/C++, Node.js
- REST APIs, webhooks, CLI tooling
- SQL (MySQL, MariaDB, PostgreSQL)
- Auth flows, data migrations, process automation
- Version control with GIT
- Shell scripting (Bash, Powershell, CMD)
Some of these I’ve used since before GitHub existed.
💻 Front-end & interaction
I like clean UI, but I love functional UX. Built for users, not just pixels.
- JavaScript / TypeScript
- HTML5 / CSS3 / Tailwind
- Angular, Cordova/PhoneGap
- Dashboard interfaces, data visualisation, templating systems
I’ve been building front-ends since IE6 was still a thing.
🔐 Security & infrastructure
I’ve poked at systems since before it was cool.
Not a hacker, just very curious.
- Pen testing / white-hat background
- DNS, SSL, session flaws, injection logic
- Experience with neglected systems + quick hardening
- Familiar with uptime monitoring, server lockdowns, and common exploits
I was reporting vulnerabilities to sysadmins when I was still in high school.
🧠 Thinking in systems
I don’t just write code — I solve bottlenecks.
That might be a tool, a fix, or just the right decision at the right moment.
- Building developer tooling
- Understanding how tech connects to real-life processes
- Communicating clearly with non-technical people
- Working alone or embedded in teams (Agile/Scrum/light chaos)
Not on the list? That’s fine.
I learn fast. The tech always changes. The thinking stays.
Want to see how that applies to your project? Let’s talk.