» Tag
system-design
33 postsNetflix Unveils Slow-Fast Architecture for Notifications
Netflix built a hierarchical notification system inspired by Kahneman's fast/slow thinking model, decoupling long-term pacing strategy from real-time message selection.
Buzzword Driven Architecture: A TDD-Inspired Design Exercise
Inspired by TDD's red-green cycle, this lightweight exercise has teams sketch architecture, score tradeoffs, and catch over-engineering before writing any code.
Teaching AI to Read Compliance Papers, Not to Decide
A two-stage AI pipeline reads SMS compliance documents field by field, while a deterministic rule engine — never the model — makes every approve, reject or review decision.
CommitBrief — AI code reviews, right in your terminal
A provider-agnostic, local-first CLI that reviews your staged changes, a historic range, or a whole GitHub pull request. Zero telemetry, no server. Free and open source.
commitbrief.comThe Acknowledgment Gap in Event-Driven Systems: A Hidden Risk
Learn about the acknowledgment gap in event-driven systems and how to prevent message loss.
Human-in-the-Loop Is Not a Governance Strategy
Approval modals in agentic AI systems often provide the illusion of oversight, not real control. Here's what genuine human-in-the-loop design actually requires.
Execution Latency in a Polymarket Trading Bot: Four Layers
A breakdown of the execution layer behind a Polymarket bot with 11,717 trades: signal timing, EIP-712 signing, CLOB submission, and why the T-90 cutoff exists.
From Static Site to Open Source Intelligence Platform: WebiU 2.0
The WebiU 2.0 team explains how they turned a growing open source organization's static site into a data-driven platform, covering GitHub API limits, persistence and architectural trade-offs.
Sub-Second Execution: Inside a Polymarket Trading Bot's Design
A deep look at a Polymarket bot's execution stack across 11,717 trades: signal generation, EIP-712 signing, CLOB API calls, and on-chain confirmation latency.
Migrating à-la-carte billing to plans-only in four safe phases
A SaaS moved from per-feature billing to plans-only using an expand-migrate-contract approach across four phases, avoiding downtime. Practical lessons for engineers.
Layer-First Pattern Cuts LLM Overload in Map Generation
RidgeText stores map layers server-side instead of passing raw GeoJSON to the LLM, cutting tool-call context from roughly 125,000 tokens down to about 150.