04 / A BIT ABOUT ME

Rhys.
Usually building.

Systems engineer working in Rust, Go and TypeScript across real-time systems, trading infrastructure, AI and products.

I’m Rhys. I build the systems underneath products that need to react to the world in real time.

Over roughly six years, that has taken me from running an online game platform to building real-time data services, blockchain infrastructure and automated execution systems. Rust, Go and TypeScript are my main tools. I’m comfortable moving between the parser, the service architecture and the interface someone uses to make sense of the result.

I like owning the whole problem: working out what matters, building the first version, finding where it breaks, and making it dependable. My experience spans individual engineering work, technical leadership, product decisions and keeping live systems running. The interesting part is how those responsibilities influence each other.

Rust · Go · TypeScript · Systems · Product

See what I’ve been building

90,000: monthly active users on a game platform I co-owned and technically led
3+ years: of blockchain history covered by a backfill pipeline I built
25+: monitoring products built around real-time market and wallet activity

Core engineer / consultant

Corvus Labs

I built a Rust wallet-intelligence and trade-execution product that evolved into an enriched WebSocket API. The work centred on turning raw Solana activity into structured, real-time data that other developers could actually use.

That included a pipeline backfilling more than three years of blockchain history, plus the Go backend MVP and Svelte/Vite foundation for a customer-facing node dashboard. My involvement extended into code review and quality assurance as the product developed.

Lead engineer

Alphaline Trade

I built more than 25 Discord-based monitoring products, turning wallet, social, volume and market activity into real-time alerts. The original services were written in TypeScript; I later re-architected the production codebase in Go around its ingestion, parsing and analysis workloads.

The work also grew into a Rust platform combining multiple trading modes with a dedicated social-data pipeline. It brought together the parts of engineering I enjoy most: understanding a noisy domain, building the machinery underneath it, and making the result useful to someone waiting on an answer.

Architecture through delivery

Independent systems work

My contract work has included geographically distributed Rust execution workers, transaction and event parsers, and a trading platform spanning ten decentralised exchanges. Alongside the backend systems, I built the dashboards and interfaces needed to operate them.

Other projects have covered wallet provisioning, live market feeds, automated order execution and historical strategy evaluation. The recurring challenge is coordinating fast-moving data with decisions that have consequences, while keeping the system understandable enough to change.

Co-owner / technical lead

Online game platforms

Earlier, I co-owned and technically led a Minecraft platform that reached 90,000 monthly active users over a 30-month run. I worked across product direction, technical delivery and live operations, including persistent game systems and a large virtual economy.

One particularly enjoyable constraint was building custom interactive experiences through resource packs, GLSL and assets, without requiring client mods. Running a live world also meant paying attention to what players actually did, then using that behaviour to guide what we built next.

Speed matters. So does knowing what your system is actually telling you.

I’m drawn to problems where performance, correctness and product judgement meet. A fast event feed is only useful if its consumer can understand ordering, gaps and recovery. A small inference runtime needs a clear measurement boundary. A tracing tool needs to preserve the difference between evidence and an attractive guess.

My instinct is to make those boundaries explicit: measure the thing that matters, give uncertain states a proper representation, and keep enough context to explain a decision later. I want the resulting product to feel simple because the difficult engineering has been thought through.

I learn by building and by pulling ideas apart. The notebook is where I work through systems papers, implementation choices and arguments I want to test. It is also where I put the qualifications that a headline or a benchmark number cannot carry on its own.

Read the engineering notebook

My work connects systems engineering with small, focused products. These projects show the problems I’m interested in:

MICROJEV: a learned decision runtime in Rust, with roughly 100K parameters and an allocation-free hot path.
Wallet Tracer: funding attribution across Base and Solana that keeps uncertainty visible.
Pacewise: an iOS project using live heart-rate input, BLE and state machines for adaptive run/walk coaching.
buildlog: a development diary and shareable record of coding-agent work, currently in development.
didyouknow: interactive explanations of maths, systems and everyday questions for the web.

I publish this portfolio and open notebook as Rhys, with the handle @rswlol. The case studies describe each project and its limits; the notebook explores the engineering decisions behind this kind of work.

FIND ME ON THE INTERNET

Follow the work in progress.

@rswlol