Jieun
deserve what you want
8 posts
-
From a No-Traffic Startup to Global Scale: An Inversion Checklist
How do you get from a small no-traffic company to a global-scale service? Don't ask "how do I get there" — ask "how do I guarantee I stay stuck." Six traps, each as problem → fix.
-
Designing a Generation Pipeline — A 4-Axis Content Model, Queue-Based Scheduling, 3-Layer Attribution
Part 2 of an engineering log on building a Threads marketing agent: a content model decomposed into four axes, an idempotent publish worker, and 3-layer attribution where 90% of clicks were bots.
-
Designing a Crawler That Beats Three Tiers of Anti-Bot — From TLS Fingerprints to CDP Detection
Part 1 of an engineering log on building a Threads marketing agent: the bottleneck was never LLM generation — it was crawling. Tiering the strategy by which signal the anti-bot actually inspects.
-
Scaling QPS 10x in Production: 3 Strategies That Actually Move the Needle
"Make it faster" sounds vague. It isn't — it comes down to the same three moves: caching, database optimization, and pulling non-essential work out of the request.
-
There Was a Deadlock Hiding in AI-Generated Code — How We Replaced `unreadCount` with `lastReadAt`
42.8% HTTP error rate, 9 minutes into a load test, at 12% of the target TPS. The culprit was a single updateMany line written during AI-assisted coding.
-
Building a Reusable Load-Test Environment for a Messenger Service — Make-based IaC, Observability, and Auth Seeding
How many TPS can a messenger's send API survive, and where exactly does it break? A 7-node mirror of production, rebuilt on demand from a single Makefile target.
-
Why You Should Never Use KeyDB as a Pub/Sub Broker for Centrifugo
KeyDB's active-replica mode looked perfect for a symmetric dual-stack chat at 100K WebSocket connections. Then I found five years of hang and deadlock issues, most still open.
-
Building a Crash-Resilient, End-to-End Meeting Recording Pipeline in the Browser
A one-hour browser recording could push the JS heap past 300 MB, and a tab crash meant losing everything. Rebuilding it as a six-stage pipeline with five-minute savepoints.
