Hey! My name is... over there ↑ and
I'm a Software Engineer from the UK.
Every project is an opportunity to create an impact. It begins with a clear target and the deliberate application of skill, honed over years of practice.
I don’t just aim to complete the task at hand; I aim to build a clean solution that initiates a chain reaction - making future development more scalable, more maintainable, and much faster.

Returning to the classic .io game MooMoo.io, I was intrigued by the massive prevalence of script kiddie hackers. This curiosity led to a deep dive into reverse-engineering the game's obfuscated code and network protocols. The result is a modular, high-quality utility script that adds quality-of-life features the few non-hackers while strictly adhering to the game's Terms of Service by avoiding unfair advantages. The project is built based on a Microkernel architecture, demonstrating a focus on readability and extensibility. By intercepting real-time game data through a WebSocket Proxy, the mod dynamically injects and manages its UI without interfering with the game's core loop. This project showcases deep practical skills in reverse engineering, defensive programming, and creating a seamless user experience within a third-party application.
Born from a need for a simple, pure CSS nesting converter, this project evolved into a personal challenge: could a basic utility be elevated to an 'Awwwards-level' website using only vanilla HTML, CSS, and JS? The result is a free, open-source tool that showcases advanced front-end techniques, from performance and accessibility to modern CSS features, all without a framework.
As part of a university group project for NEXT, I co-developed a dynamic, gamified career quiz application. I led the front-end and design efforts, ensuring the UI/UX aligned with NEXT's brand guidelines, and also provided crucial back-end support. Key contributions include designing and developing core pages, creating web scrapers in both JS and C# (using Playwright) to gather live job data, and implementing accessibility features. This project was an exercise in agile development, remote collaboration, and rapid adaptation to client feedback. It reinforced the importance of clear communication and proactive planning in a team environment. Despite a tight deadline and the challenge of learning Blazor, we successfully delivered a functional and well-received product.
Returning to the classic .io game MooMoo.io, I was intrigued by the massive prevalence of script kiddie hackers. This curiosity led to a deep dive into reverse-engineering the game's obfuscated code and network protocols. The result is a modular, high-quality utility script that adds quality-of-life features the few non-hackers while strictly adhering to the game's Terms of Service by avoiding unfair advantages. The project is built based on a Microkernel architecture, demonstrating a focus on readability and extensibility. By intercepting real-time game data through a WebSocket Proxy, the mod dynamically injects and manages its UI without interfering with the game's core loop. This project showcases deep practical skills in reverse engineering, defensive programming, and creating a seamless user experience within a third-party application.

Born from a need for a simple, pure CSS nesting converter, this project evolved into a personal challenge: could a basic utility be elevated to an 'Awwwards-level' website using only vanilla HTML, CSS, and JS? The result is a free, open-source tool that showcases advanced front-end techniques, from performance and accessibility to modern CSS features, all without a framework.

As part of a university group project for NEXT, I co-developed a dynamic, gamified career quiz application. I led the front-end and design efforts, ensuring the UI/UX aligned with NEXT's brand guidelines, and also provided crucial back-end support. Key contributions include designing and developing core pages, creating web scrapers in both JS and C# (using Playwright) to gather live job data, and implementing accessibility features. This project was an exercise in agile development, remote collaboration, and rapid adaptation to client feedback. It reinforced the importance of clear communication and proactive planning in a team environment. Despite a tight deadline and the challenge of learning Blazor, we successfully delivered a functional and well-received product.
