◉ OnlineEngineer · BuilderIIT GuwahatiIndia

Yash Garg

— Systems architect

I build systems that ship, interfaces that surprise, and ideas that shouldn't work — until they do.

Read YASHIMAGATORU →
SCROLL↓

Five months
in the arena.

I joined Matiks on February 23. The next day, my first pull request was up. What I built, what I learned, what hurt, and what I am carrying forward.

Read the field note →
23 FEBSTARTED
101AUTHORED DAYS
140PULL REQUESTS
YASHIMAGATORU manga cover
NEW DROP
READ THIS FIRST

Stop scrolling like a normal person.

YASHIMAGATORU is live.

A cursed genius, a chessboard with god issues, and reality getting bullied by code. This is the next click. The portfolio can wait.

How I think about building.

I sit at the intersection of systems engineering, product thinking, and interface craft. I don't separate the technical from the creative — the best systems are both.

◈01

Systems Engineering

Rust streams. Caching layers. Cost engineering. I think in throughput, latency, and failure modes — then build systems that hold up under real conditions.

RustTokioSpring BootRedisAWS
⬡02

Product Architecture

BFF patterns. GraphQL migrations. Clean contracts. Shaping systems around user journeys — not around accidental technical sprawl or legacy convenience.

GraphQLRESTTypeScriptNext.js
◎03

Interface Design

Tactile UIs. Meaningful motion. Delight in the details. Software that feels alive — that rewards exploration and makes you feel something without knowing why.

ReactFramer MotionAnimationUX
⬙04

AI Products

Agentic interfaces. Voice-first apps. AI coworkers. I build the parts of the future that are technically possible right now but nobody has shipped yet.

LLMsVoiceAgentsAI-native UX
⬣05

Game Mechanics

Engagement loops. Reward systems. Interaction design with real stakes. Co-founded a game dev collective in college. Never really stopped thinking in levels.

Game DesignInteractionUnityEsports
◇06

Experiments

Weird ideas. Ambitious concepts. Things that shouldn't work but kind of do. The lab never closes. Half the best ideas look unreasonable until they ship.

EverythingAnythingWhatever's interesting

Missions, shipped.

Not just what I built — but what changed because of it. Click any dossier to read the full build story.

The lab.

Where ideas live before they become products. Some of these are building. Some are concepts. Some are just too interesting to ignore. Hover to see the detail.

◇IMAGINING01

Voice-Driven App Builder

Talk to it. It builds. Not prototypes — actual deployable apps. The IDE as conversation, the computer as collaborator.

VoiceLLMIDECode Generation
◎CONCEPT02

AI Coworker by Email

An AI colleague you CC on tasks. It picks things up, follows up, keeps context across threads. Async intelligence.

AIEmailAgentsAsync
◇IMAGINING03

AI Teacher with a Blackboard

Not a chatbot. A visual thinker. It draws diagrams, writes proofs, solves problems with the physical metaphor of teaching.

EducationVisualAISpatial
◎CONCEPT04

Agentic Airline Interface

A conversational layer over airline e-commerce that actually knows your preferences, history, and intent.

AviationAgentsUXPersonalization
⚡BUILDING05

Debate Rooms

A space where ideas get contested. AI-assisted argumentation, structured discourse, real intellectual stakes.

SocialAIDiscussionDiscourse
◎CONCEPT06

Social Feed of AI Chats

What if your feed was a conversation? Share an AI exchange. React with a counter-argument. Build on each other's thinking.

SocialAICommunityContent

— the lab never closes —

How I build.

Not generic values. Real builder principles — the ones that actually shape decisions when things get hard.

01

Software should feel alive.

Interactions should have weight. Transitions should have memory. If a UI doesn't make you feel anything, it's not finished yet. The emotional quality of software is part of its correctness.

02

Architecture should reduce chaos, not rename it.

The goal isn't to move complexity somewhere new. It's to eliminate it. A microservice that hides the wrong abstraction is worse than a monolith with a bad name. Good systems get simpler as they mature.

03

Interfaces should reward curiosity.

The best UIs have layers. Surface-level for the casual. Depth for the explorer. Design for the second visit, not just the first. The things you discover on your own are always more memorable.

04

Product quality includes emotional quality.

Users don't just evaluate features — they feel software. A system that works but feels bad is still failing. Performance is a feature. Delight is a feature. Personality is a feature.

05

Build weird things. Ground them in craft.

Weirdness is valuable when backed by real skill. The most interesting ideas sound unreasonable until they ship. The craft is what makes them land — what separates a toy from a tool.

What's occupying the stack.

Real-time status. What I'm working on, thinking about, and excited by right now.

yash@headquarters ~ status▌
BUILDINGThe next chapter: systems, AI-native products, and things that probably shouldn't exist
EXPLORINGAgentic UX patterns, voice interfaces, edge computing primitives
OBSESSINGPerformance engineering, interaction design, the gap between demos and products
OPEN TOAmbitious engineering problems where systems, product, and interface quality meet
LOCATIONIndia — between IIT Guwahati nostalgia and whatever comes next

$ last updated: July 2026 · open to ambitious problems

Let's build

something.

If you're working on something ambitious, weird, or genuinely difficult to describe in a single sentence — I want to hear about it.

Smart people building hard things. That's the only filter.

yashgarg.wtf — built with Next.js, Framer Motion, Three.jsIIT Guwahati · India · 2026