For a better looking HTML version of this page, click here
I'm a final-year software engineering student at the University of Newcastle. I build things - languages, tools, communities - and I'm just as interested in how software shapes the people around it as I am in the code itself.
A code-golfing language with a full interpreter, documentation and online playground. The goal was to make a language that's competitive on brevity without terribly being unreadable after the fact.
An array programming language designed in 2026. APL's ideas are genuinely good; the notation has just been a barrier since 1966. Valiance tries to fix that.
A code golf explanation assistant for answers on the code golf stack exchange. Lining up non-single-width characters can be very difficult. This tool makes it a breeze.
Spam-fighting tooling for the StackExchange spam handling volunteer team Charcoal. Significantly simplified the process of generating regular expressions (regexes) used to determine if a question/answer posted on the StackExchange network is likely to be spam. Provides a select-and-click method of regex generation, an improvement over handwritten regex. Incorporates fifteen regex-generation heuristics built from a decade of collective spam-handling experience.
A browser tool for adding private notes to StackExchange user profiles. This adds functionality StackExchange does not provide for moderation context that doesn't belong in public records.
Chromatura (AI-assisted)
A manual syntax highlighter for languages that don't have an LSP yet. Built with AI agent tools as a practical exercise in knowing when to write code and when to direct something else to write it.
Elected moderator on three StackExchange communities:
- Code Golf Stack Exchange - 8 months
- Language Design Stack Exchange - 3 years
- Generative AI Stack Exchange - 5 months
I'm finishing a Bachelor of Software Engineering at the University of Newcastle (started 2021). The academic side is done; I'm currently looking for a placement to complete the required industry hours.
The thread running through most of my projects is an interest in what programming actually feels like to do. A lot of languages and tools treat ergonomics as an afterthought - syntax gets inherited from whatever came before, friction accumulates, and nobody questions it. Vyxal came from asking what brevity looks like when you actually design for it. Valiance came from asking why array programming has to be so hostile to read. That question - what would this be like if someone had actually thought about the person using it - tends to be where I start.
On the AI side, I've been working through what agentic workflows are capable of in practice - less as a user and more as someone trying to understand where the feedback loop holds and where it doesn't.