I build websites and backend systems that actually work. Started with "why won't this button center", now I'm architecting full-stack projects and debugging at 2am like it's normal. Business Computing student who codes more than sleeps.
Yeah, I'm basically always building something. Check the repos for proof.
Real distribution from my GitHub repos. Turns out I write a lot of JavaScript.
Every interaction below is intentional.
I don't just write code. I architect solutions that teams rely on. After shipping real projects under pressure, I've learned what separates "it works" from "it scales." I think in systems; how one decision ripples through a codebase, how a UI flow changes user behavior, how backend choices impact frontend experience.
In production, things break. I don't panic. I trace. I fix. I prevent. I've reduced error rates by 40% through better validation. I believe this has improved my systematic thinking.
I focus on the problem we are solving first, then explain how the technology supports that goal. My aim is to bridge the gap between technical systems and real business needs.
I started saying "why won't this button center?" Now I am working towards building pragmatic applications. That hunger doesn't stop. I read code. I debug production. I learn from failure. Your team gets someone who doesn't coast, someone who knows there's always a deeper level to understand.
Real projects. Real impact. Real code.
Loading projects from GitHub...