Shyunku shyunku

shyunku

When something catches my attention, I keep following it —
from the interface to the protocol, and from the product to the system underneath.

	Direction	What I tend to explore
🖥️	Applications	How an idea becomes an interface I can touch and test
⚙️	Systems	What happens behind an API, a real-time service, or a stream of data
🧰	Tools	Parsers, simulators, libraries, and automation for problems I want to understand
🧪	Rabbit holes	Games, cryptography, blockchain, and whatever feels worth taking apart

Project	What it is	Area
team.gg	A League of Legends platform that grew from match history into custom-team statistics, ROFL parsing, and AI-assisted replay analysis	Game Platform · Data Analysis
Fluid	A from-scratch exploration of React internals: virtual DOM, Fiber reconciliation, hooks, routing, and an in-browser JSX transformer	UI Runtime · Learning Project
Thread	One task-management idea followed across Electron, React Native, a Go sync server, and release and administration services	Productivity · Cross-platform
CushionBot	A Java Discord bot that expanded into per-server music, League custom-game coordination, recruiting, and activity monitoring	Community Tool · Automation

The stack changes from project to project. The pattern does not: find an interesting question, then follow it further than expected.

Applications & interfaces

Services & data

More technologies I have worked with

_{Still following the next interesting question.}