Same Care, Opposite Direction

I work on a fintech app. Every screen I build goes through legal review. Every error message has been argued over by three people. Every animation has to justify itself to a compliance officer who has never animated anything in his life.

This sounds like creative hell. And sometimes it is. But three years in, I've started to think fintech is one of the better trainings a future game developer could ask for. Here's what I mean.

What fintech teaches you

Every interaction is a contract. When a user taps "Send 5,000,000 VND," that tap is legally binding. You don't get to be cute. The button can't be ambiguous. The confirmation can't be cluttered. You learn to write UI that says exactly what's happening and nothing else.

That discipline transfers to games in a surprising way. Bad games are full of unclear interactions — buttons that don't make it obvious what they'll do, menus that hide critical info. Fintech beats that out of you. You learn to ask, of every screen: "If I were drunk and angry, could I still get this right?"

Edge cases are the job. In a game, if the player does something weird, the worst case is usually a funny bug. In fintech, the worst case is someone losing their life savings. You learn to think about every input as adversarial. What if they tap twice? What if their network drops mid-transaction? What if their phone date is wrong? What if they're on a 2014 Samsung running a custom ROM?

That paranoia, applied to games, makes you better at multiplayer netcode, save systems, and difficulty tuning. Games crash when the player does something the designer didn't imagine. Fintech devs imagine more.

Latency is moral. When someone in a remote village is sending money home, every second of loading screen is a tiny crisis. You learn that performance isn't a nice-to-have. A janky scroll is a broken promise.

Games have the same morality, even if the stakes are lower. A laggy game disrespects the player's time. The fintech instinct to obsess over startup time, scroll smoothness, and bundle size translates directly.

What fintech doesn't teach you

I don't want to oversell this. Fintech also breaks habits that games need.

Fun is unfamiliar. Three years of "remove unnecessary delight" can leave you unable to add necessary delight. When I started making games, I kept stripping out the juice — fewer particles, faster animations, less personality. My Flutter brain was running on autopilot, treating decoration as risk. I had to consciously rebuild the muscle to add feeling.

Permission to experiment is foreign. In fintech, you don't ship something to see what happens. You ship something because three layers of approval said you could. Games run on the opposite logic — ship the weird thing, let players react, learn what's fun. That posture shift, from cautious to experimental, has been the hardest unlearning.

Aesthetic vocabulary is thin. Fintech UI is built on a handful of patterns — lists, forms, cards, status indicators. After three years, you can build them in your sleep. But your visual library is narrow. Games demand a much broader vocabulary: HUDs, dialog boxes, world maps, inventory grids, dialogue trees. I've spent a lot of evenings just looking at games and trying to name what I see.

How I'm reconciling them

Here's the trick I've landed on: I think of fintech as my floor and games as my ceiling. Fintech sets the baseline of craft — nothing I ship can be sloppy, unclear, slow, or inaccessible. Games set the upper limit — the thing should make someone smile, surprise them, reward attention, feel alive.

Most of what I'm building lives in the middle. A side project might not need bank-grade reliability, but it benefits from the instinct toward it. A game prototype might not need fintech polish, but knowing what polish is makes the rough version less rough.

I think this is actually a competitive advantage. Most game devs I read about online didn't come from environments that taught them to be that careful. Most fintech devs aren't trying to make things fun. The intersection is small, and I don't think it's a bad place to stand.

The pipeline

If you're a fintech dev looking at games and wondering if the pivot makes sense, here's the honest version: the skills do transfer, but the attitude has to shift. You're not abandoning your training. You're inverting it. Same care, opposite direction. Instead of removing every unnecessary thing, you're adding every necessary delight.

The training stays. The posture changes. That's the pipeline.