Build Log
Breaking Down "Sometimes Fast, Sometimes Slow" With Numbers
Four runs under identical conditions varied by less than 1%. What was unstable wasn't the server — it was the observation conditions.
ReadDEV.LOG · 2026.10.15
A dev log, written while building
Hands-on notes on services, infrastructure, automation, security and AI — the problems I ran into while building them, and how they were solved.
Build Log
Korean web fonts were 73% of our first-visit payload
We were loading 11,172 characters to render 647 of them. Splitting the font by character range cut first-visit payload from 3,131KB to 558KB.
ReadBuild Log
Getting a Static Blog Indexed by Search
If it's all in the build output, you're done. But miss something, and it just quietly stays missing.
ReadBuild Log
Build Log
Build Log
Build Log
Build Log
Build Log
Build Log
Build Log
Breaking Down "Sometimes Fast, Sometimes Slow" With Numbers
Same conditions: <1% varianceFour runs under identical conditions varied by less than 1%. What was unstable wasn't the server — it was the observation conditions.
Build LogKorean web fonts were 73% of our first-visit payload
First load: 3,131KB → 558KBWe were loading 11,172 characters to render 647 of them. Splitting the font by character range cut first-visit payload from 3,131KB to 558KB.
Build LogGetting a Static Blog Indexed by Search
22 sitemap URLsIf it's all in the build output, you're done. But miss something, and it just quietly stays missing.
A Collection of Missteps (DevToolStack Dev Log #7)
5 missteps → 0 haltedFailures that throw an error and die get fixed fast. The expensive ones were the kind that silently did the wrong thing.
Running a MacBook as a 24/7 Server (DevToolStack Dev Log #6)
181 deploys · 2 fails · 1–14sI put the admin panel and a tunnel on a single MacBook at home. Not one port is open, and readers never notice when it's off.
Why I Turned AI Review Back Into a Manual Step (DevToolStack Dev Log #5)
Median review: 64s · 23 commentsI dropped the nightly automated run and turned auto-triggered review into a button instead. This isn't less automation — it's cutting only the parts that cost money.
Putting AI Inside the Pipeline (DevToolStack Dev Log #4)
600s timeout → 88s · one line on lengthOnce I decided to use a subscription I was already paying for instead of an API key, the way to hook up AI was almost entirely decided for me. Instead of the admin calling an API, it runs the logged-in CLI as a child process.
Why Astro + Payload + Cloudflare (Building DevToolStack #3)
3 requirements cut 5 SSG candidates to 1It has to show up in search, I need to publish from my own admin, and I need to be able to reshape the screens however I want. Those three requirements decided almost the whole stack.
Why I Turned Design Mockups Into Requirements (Building DevToolStack #2)
Mockups → 5 rule documentsI drew the screens first, and still got told twice that it "looked completely different." A screen you build "roughly similar" doesn't look similar at all.
Why I Decided to Build This Blog Myself (Building DevToolStack #1)
5 of 6 requirements outside publishingI scrapped my first plan — pushing posts into Google Blogger — before writing a single line of code. Once I wrote out everything I actually wanted in a table, none of it turned out to be possible on someone else's platform.