Writing

When a Solana transaction fails, the logs often show a code instead of a clear answer. I built an open diagnosis skill and a live explainer so you can paste a signature and get a readable cause and fix.

I build from Yangon. Here is why Solana still makes sense when your passport and bank make ordinary work harder than it should be.

I write instructions the way I write product contracts: inputs, outputs, and failure cases. Notes from building Vectra briefs, PixelBrief brand kits, and spend review tools.

I studied English at Pathein University, then taught myself to ship software. Now I am doing a BSCS at University of the People while publishing products from Yangon.

From Yangon, public code and writing are the levers I can actually pull. Why I ship on GitHub while aiming for remote roles and a funded MSCS or PhD.