Bio

Computer Analyst by training and craft. 3DS Max artist by passion — Jack of All Trades by necessity. Game development was always there. Small projects, side builds, never quite off the table. Unreal Engine from day one — Blueprint only, thrown into a professional engine and loving every second of it.

Eight years building real-time trading interfaces. Not tweaking templates — forging frameworks from scratch to meet what financial markets actually demand: live data, zero latency, integrity that holds under pressure, their own Personal Jesus — the workflow each trader would swear by and kill for.

Production constraints don't negotiate. When the tooling to meet them didn't exist, it got built. Wheels got reinvented not for the exercise — but because moving forward required it. It was real opportunities.

That's where the habit of going deep comes from. You don't survive tight corners by staying shallow.

Prototyping forgives everything. The real reckoning comes later — when the project shifts to production, when tests need reconciling, when every shortcut taken in month two is still there in month eight waiting to collect.

Choosing clean structure early is the right call. It's also the harder one. And when the tooling to support that choice doesn't exist, the path gets narrow very fast.

Blueprint looked like the way out — fast, visual, forgiving. And it is, if you're comfortable letting data stay loose and structure stay soft. A lot of projects live there and ship just fine.

But if you want something that holds — something you can actually maintain, extend, hand off to yourself six months later without a headache — casual isn't an option. Tightened structure isn't a preference. It's the only path that doesn't close behind you.

The ecosystem was missing the minimal tooling needed to walk that path cleanly. Refusing to go messy meant stopping until it was there. It wasn't. So it got built.

tooTiny is what happens when you finally stop waiting for someone else to ship the thing you need.

These plugins are not side experiments. They are the infrastructure projects run on — and tools developers have longed to get. Correctness and clean editor integration are the baseline — not the goal. 

One developer. One community. One standard.