Code as Leverage

There is a specific kind of friction that comes from building software in Myanmar.

The internet here is good enough to push a Solana app at 3 a.m. The passport in my drawer is still heavy enough that many job posts are not really written for me. Both facts are true at the same time.

This is how I work with that tension.

The local default vs the public default

A lot of career advice around me is local and stable. Get a safe job. Teach. Leave if you can. Almost nobody tells a kid from Pathein Township that he can ship a public repo, enter a Superteam or DoraHacks build, and get paid in stablecoins without waiting for a visa.

That path is real. It is also incomplete. Global teams still optimize for candidates who are easy to payroll, easy to schedule, and easy for finance to understand. I do not always match that template.

So I ask a practical question: do I only apply into systems designed around someone else, or do I grow public surface area until the work can find me?

Why leverage is the right word

Code compounds. A bounty repo becomes starter code for the next one. A README keeps explaining me while I sleep. A post like this still argues for me months later.

From Myanmar, code and content are the levers I can pull without needing a perfect banking relationship first. So I stack them. Projects go on GitHub. Writing points back to the work. Over time that becomes a public record that acts like a portfolio and a recommendation letter at once.

How hackathons and bounties compound

Superteam Earn taught me this the hard way. Early submissions lost. Later ones got closer. Eventually I started winning more often because I understood what sponsors actually needed, not only what the brief said.

The prize money mattered. The compounding mattered more. Patterns from one Solana build showed up in the next. Agent loops, wallet flows, and UI scaffolding stopped being one-off experiments.

DoraHacks has the same shape for me: ship, publish, learn in public, move to the next build.

Jobs, research, and graduate school

I am not against jobs. A strong remote or full-time engineering role would teach me things I cannot invent alone. I am open to that now.

I am also aiming for a fully funded MSCS or PhD. I do not want graduate school to be an escape from a thin portfolio. I want to walk in with shipped systems, honest writeups, and a clear research direction around blockchain, agents, and security.

Independence is useful. Structure is useful too. Right now I am building enough public proof that either path is available.

One sentence version

I treat every serious line of code as leverage I can keep. If you searched for Sithu Nyein because you care about Solana builders from Myanmar, start with the repos. The story only matters if the work holds up.

Sithu Nyein, Yangon