I write code across several languages, build and run my own hardware, and figure out problems as I go. Still learning — always have something on the go.
A mix of languages I've picked up through real projects — not tutorials. Each one taught me something different about how software actually fits together.
Most of my Lua work has been in Roblox Studio — writing placement systems, GUI logic, and server-client communication. It made me think seriously about event-driven code and what happens when players try to break things.
Started with HTML because I wanted to make things visible on a screen. Grew from there into layouts, responsive design, and learning what makes a page actually usable — not just technically correct.
Python is what I reach for when I want to get something done without overthinking it. I've used it for automation, messing with APIs, and prototyping ideas quickly. It reads well and gets out of the way.
Java pushed me to think in a more structured way — proper classes, interfaces, and thinking ahead about how pieces fit together. It's verbose but that verbosity forces good habits early on.
Most of my Node work has been building Discord bots — event handling, persistent storage, modular architecture. Also used Node-Canvas for generating images on the fly. It's where my JavaScript actually does something useful.
I've built several custom PCs from scratch and run my own servers at home. Understanding what's happening physically — components, thermals, compatibility — changes how you think about the software running on top of it.
A handful of things I've actually finished and put to use. Each one came with its own problems to figure out.
Tracks who invited who in a Discord server — including edge cases like deleted or expired links. Keeping accurate counts across a live server is trickier than it sounds. Added a leaderboard, persistent storage, and built it modular so adding features later wasn't painful.
Generates a custom image when someone joins a server — avatar, username, server info, all composed at runtime using Node-Canvas. Mostly an excuse to get into image manipulation through code, and it ended up looking pretty good.
Set up a Pi as a proper web server running Nginx and Docker. Containerised a few services, got reverse proxying working, and kept it running reliably on hardware that costs less than a takeaway. Good way to learn what production actually means.
Various systems built in Lua — placement mechanics, interactive GUIs, server-side validation. Working in Roblox means your code runs in front of players who will actively try to exploit it, which forces you to write more defensively than you would otherwise.
Software made more sense once I started understanding the machines it runs on. Building and maintaining hardware is part of how I work.
Put together several machines over the years — gaming rigs, a home server, a dev box. Picking parts, doing the build, troubleshooting when something doesn't POST. You get faster at it and you stop being precious about it.
Comfortable moving between Windows, Linux, and Raspberry Pi OS. Installed and configured enough systems to know where things go wrong — partitioning, drivers, getting hardware properly recognised. Nothing exotic, just practical familiarity.
The home server is the main one — running services in Docker containers behind Nginx, accessible remotely, generally just staying up. Small hardware with real constraints is a good way to learn what actually matters in system design.
I don't mind not knowing something when I start. Most of the projects on this page began with figuring out something I hadn't done before. Getting things working, then understanding why they work — that's the habit I've built up.
Whether you've got a project in mind or just want to talk about something you're building, feel free to reach out.
[email protected]