AI workflow ဆိုတာဘာလဲ
AI workflow ဆိုတာ trigger, data, AI step, approval, output တွေကို ချိတ်ထားတဲ့ automation flow တစ်ခုပါ။
Read note →Notes
Knowledge notes, build logs, and things worth writing down.
Using Astro content collections to build a knowledge base
Content collections turn markdown files into typed, queryable data. Here's why they're the right architecture for a blog or notes section, and how to set them up from scratch.
Read note →Design tokens that actually survive theme switching
Getting dark/light themes right is harder than swapping background and foreground colors. Here's what breaks, what the FOUC problem is, and how the token system in this portfolio handles it.
Read note →Why I use GSAP over CSS animations for portfolio motion
CSS animations are fine for hover states. For anything that needs to feel alive — sequenced, staggered, timeline-driven — GSAP wins every time.
Read note →Building a terminal aesthetic with CSS — no images required
The grid background, monospace everything, dashed borders, glowing dots — all of it is pure CSS. Here's how the visual language of this portfolio works.
Read note →Building AI memory systems that actually work in production
Most AI memory implementations fail because they treat memory as retrieval. Real memory is about what gets recorded, what gets forgotten, and what gets surfaced at the right time.
Read note →Prompt engineering that holds under real-world conditions
Most prompt advice is optimized for demos. Production prompts face adversarial inputs, model drift, edge cases, and context limits. Here's what actually works.
Read note →On shipping small tools that stay useful
Most side projects die because they try to become products. The ones that survive stay small, solve one thing precisely, and resist the urge to grow.
Read note →Using TypeScript as a configuration language
JSON configs break silently. YAML configs have footguns. TypeScript configs give you autocomplete, validation, and refactoring — for free, with no extra tooling.
Read note →Static vs dynamic rendering: how to actually decide
The Next.js default is to reach for SSR. The right answer is usually SSG. Here's a framework for deciding which rendering strategy to use for each page.
Read note →Terminal UX principles that apply to any interface
Terminals have survived for 50 years because they get a few things exactly right. These principles aren't just for CLI tools — they make any interface better.
Read note →