โโโโ โโโโโโโ โโโโโโโ โโโโโโ โโโโโโ โโโโโโโโโโโโโโ โโโโโโ โโโโโโโ
โโโโโ โโโโโโโโ โโโโโโโโ โโโโโโ โโโโโโโ โโโโโโโโโโโโโโ โโโโโโ โโโโโโโโ
โโโโโโโโโโโโโโ โโโโโโโโโ โโโโโโโโโโ โโโโโโโโโโโโโโโโโโโ โโโโโโ โโโ โโโ
โโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโ โโโโโโ โโโ โโโ
โโโ โโโ โโโโโโโโโโโโโโโ โโโโโโโโโ โโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โโโ โโโ โโโโโโโ โโโ โโโโโโโโ โโโโโโ โโโโโโโโโโโ โโโโโโโ โโโโโโโโโโโโโโโ
i'm munkhsuld โ a 21-year-old developer from ulaanbaatar, mongolia ๐ฒ๐ณ operating at the crossroads of artificial intelligence, full stack engineering, and design.
still early in the journey, but i try not to get too attached to any particular tool or language. i care more about understanding how things fit together โ how data flows, how interfaces make complexity feel simple, how AI can actually be useful rather than just impressive.
i'm figuring it out as i go. what i try to hold onto:
- ๐ง understand the problem before reaching for a solution
- ๐ฏ honest about what i don't know yet
- ๐ฑ every project teaches me something the last one didn't
- ๐ learn โ build โ reflect โ repeat
AI Engineering โ building systems that let humans talk to their data
multi-agent pipelines, intent classification, LLM orchestration
Full Stack Dev โ end-to-end product ownership
from database schema to pixel-perfect UI
Design Engineering โ where logic meets craft
clean, responsive, performance-obsessed interfaces
Data Infrastructure โ pipelines, warehouses, dimensional models
making raw data actually useful for decisions
right now i'm working on decision intelligence โ AI-powered platforms that help organizations understand what's happening in their business. it's a domain i'm still learning, and there's a lot to figure out.
i'm curious about how language models can make data more accessible, how agents can surface useful context without being asked, and how to build things that feel genuinely helpful rather than just technically clever.
on the side: web3, design systems, and whatever rabbit hole is currently interesting.
software is a medium. the real work is understanding the problem well enough to model it simply.
i try to spend time thinking before typing. not always successfully โ but the goal is to know:
- what problem is actually being solved
- where the real complexity lives
- what the simplest honest version looks like
i'm drawn to the edges between disciplines โ AI and UX, data and design, engineering and product. that's where things get interesting, and also where i have the most to learn.
when i'm not building, i'm:
- ๐ reading about systems, cognition, and how organizations make decisions
- ๐ into movement โ physical discipline translates to mental discipline
- ๐ thinking about what it means to build technology from mongolia, for the world
- ๐ฎ occasionally disappearing into games or late-night side project rabbit holes


