IT, AI, and dev tooling insights from a Korean senior dev working in Southeast Asia.
One post per day. Mon = news · Tue = code · Wed = Indonesia · Thu = tools · Fri = debate · Sat = build · Sun = free.
I told my AI agent my blog looked like garbage. It loaded 54 real-world design systems, ran a comparative analysis, and rebuilt the entire theme with Linear.app's design tokens. Swapped between three AI models mid-task and learned which one handles structure vs. polish. 1,500 lines of CSS, 3 commits, one afternoon.
Three acquisitions in twelve months. Korean dev tools are no longer a fragmented market — they're a small oligopoly, and the API surfaces are starting to look the same.
Modern JavaScript runtimes have had structured state primitives for years. You probably don't need a 40KB dependency for what your app actually does.
Five years of quiet, distributed, community-driven tooling work. The results are starting to show up in the kinds of projects that get adopted outside the country.
It's a personal AI agent. It's not a product for end-users. With that frame, it works better than anything else I've tried. Here's what works, what doesn't, and when I'd reach for something else.
Two years of watching the field from Jakarta. The replacement threat was always a junior-developer story. The senior-developer story is the opposite of what most people are writing about.
Type at least 2 characters to search.
