Practical software notes from a Korean programmer and software architect in Indonesia — Laravel/Vue SaaS projects, DevOps, AI agents, and the Korea to Southeast Asia tech bridge.
I write from hands-on software work: Laravel SaaS projects, DevOps, Windows utilities, AI automation, and the operating constraints of building from Indonesia.
A short path through the core argument of this site: agents need maps, automation needs proof, and tools need exit paths.
One post per day. Mon = news · Tue = code · Wed = Indonesia · Thu = tools · Fri = debate · Sat = build · Sun = free.
A short AI-generated diff can cross validation, request, persistence, and test boundaries. Review the named code entities, the evidence, and the rollback seam—not only the lines that changed.
An exactOptionalPropertyTypes error is often an ownership decision left undocumented. Use a narrow boundary, type tests, runtime tests, an exact lockfile, and a rollback path to turn strict TypeScript into a maintainable migration.
Shinjae Kang
Read
A cautious Vue 3.6 Vapor Mode adoption pilot for Laravel and Vue SaaS teams: isolate one route, measure it, and keep a rollback path while Vapor remains unstable.
Shinjae Kang
Read
Grok 4.5 is now available on the xAI API with pricing and reasoning controls that make developers pay attention. The real adoption test is whether it survives your local coding-agent harness.
Shinjae Kang
Read
Wrangler 4.108.0 added a quiet branch for agent-driven static Pages deploys. The operational lesson is simple: an AI deployment is not complete until the target platform, URL, resource ownership, and rollback path are verified.
Shinjae Kang
Read
TanStack Table v9 beta added web workers for row models, then immediately shipped sorting and cell-order fixes. Treat that as a migration boundary, not a free performance switch.
Shinjae Kang
Read
The first merge gate catches obvious AI coding mistakes. A repeatable review harness catches the slower failures: drift, missing rollback paths, weak tests, and agent changes that look fine until production maintenance begins.
Shinjae Kang
Read
A low-cost observability pattern for agent crons using logs, artifacts, summaries, and delivery checks before adding paid monitoring tools.
Shinjae Kang
Read
Why automation only compounds when it closes the loop with metrics, review, and next actions instead of simply generating more output.
Shinjae Kang
Read
A practical contract for giving coding agents repository context, edit boundaries, verification steps, and rollback paths before they touch code.
Shinjae Kang
Read
Why coding agents need compact repository maps, ownership boundaries, and verification paths more than bigger context windows.
Shinjae Kang
Read
A practical test for adopting beta libraries: prove the rollback path, migration cost, and ownership model before they enter production.
Shinjae Kang
Read
A field note on why rendered UI is not enough, and how to verify AI-generated interfaces against behavior, accessibility, and maintenance risk.
Shinjae Kang
Read
A production checklist for cron jobs that proves useful artifacts exist, are fresh, and can be consumed downstream after the process exits.
Shinjae Kang
Read
GLM-5.2's MIT-licensed open weights at one-sixth the cost of GPT-5.5 isn't a benchmark story — it's a cost-structure story. Here's what it means for your architecture decisions this week.
Shinjae Kang
Read
Five cron patterns that look healthy while silently failing, with checks for stale files, empty outputs, partial JSON, and missing delivery.
Shinjae Kang
Read
A 2026 frontend survival guide for replacing unnecessary JavaScript with modern CSS features while keeping behavior accessible and maintainable.
Shinjae Kang
Read
Why a green cron exit can still mean failed work, and how to verify agent jobs by checking useful output instead of process status.
Shinjae Kang
Read
A field report on changing an LLM backend cleanly: where provider abstraction helps, where costs shift, and what still needs verification.
Shinjae Kang
Read
How to detect zombie AI agent pipelines with freshness checks, artifact validation, and downstream proof instead of trusting running processes.
Shinjae Kang
Read
Why model portability matters more than benchmark wins when AI coding tools must survive cost shifts, outages, and real legacy codebases.
Shinjae Kang
Read
A pragmatic guide to choosing AI agent frameworks by operating model, integration cost, lock-in risk, and production failure modes.
Shinjae Kang
Read
What actually breaks when you run AI agents on cron 24/7 — zombie tasks, subagent black holes, and the architectural patterns that make autonomous pipelines reliable.
Shinjae Kang
Read
How to move AI agents from demos to production by adding checkpoints, logs, artifact proof, budget limits, and human-readable recovery paths.
Shinjae Kang
Read
OpenCode hit 160K GitHub stars and dethroned Cursor as the #1 AI dev tool. Claude Fable 5 launched with record benchmarks — then got suspended 3 days later. Here's what actually matters for your workflow.
Shinjae Kang
Read
Z.AI's GLM 5.2 (744B MoE, 1M context, MIT license) tops open-weights benchmarks and runs coding agents at frontier level. Full breakdown.
Shinjae Kang
Read
How a Hugo blog adopted a token-driven design system from real references, turning brand choices into reusable CSS and publishing rules.
Shinjae Kang
Read
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.
Shinjae Kang
Read
Modern JavaScript runtimes have had structured state primitives for years. You probably don't need a 40KB dependency for what your app actually does.
Shinjae Kang
Read
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.
Shinjae Kang
Read
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.
Shinjae Kang
Read
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.
Shinjae Kang
ReadBrowse by theme.
Type at least 2 characters to search.
