WRITING ARCHIVE
2020
90 published posts.
- The Armenian Thread in System of a Downmusic
- Psycho — Obsession, Performance, and the Point Where Desire Becomes Loopmusic
- A Clean Checkout Is the Build Test That Matterswriting
- Backup Size History Can Reveal Missing Datawriting
- V133A Was Safe Because the Power Feature Could Not Rewrite Golden Mainwriting
- Secure Boot and Flash Encryption Should Not Be Burned into Prototype eFuses Casuallywriting
- Trunk Ports: The Part of VLANs I Initially Misunderstoodwriting
- How We Learned to See Geometryperspectives
- Five Devices and Twenty Devices Are Different Testswriting
- Packet Drops Are More Actionable Than Raw Bandwidthwriting
- Image Storage Growth Is Different from Runtime Data Growthwriting
- Cloudflare Tunnel Reaches Caddy but Still Returns 502writing
- Where the user interface Analogy Breaksperspectives
- Recovery Tests Are More Valuable Than Backup Countswriting
- ALDO2 and ALDO3 Became Named Product Railswriting
- Rollback Has to Include Persistent-State Compatibilitywriting
- Where the unexpected system behavior Analogy Breaksperspectives
- What Intelligence Really Isperspectives
- Dramatic Theme — When a Soundtrack Knows It Is Closing a Scenemusic
- Rolling Back Code Is Not the Same as Rolling Back Datawriting
- Metric Relabeling Can Be a Memory Optimizationwriting
- One Deadlock Is Worth Recordingwriting
- Terraform Stacks vs Workspaces Is a Lifecycle Design Choicewriting
- tcpdump on a PBX Taught Me to Trust the Wire Before the GUIwriting
- Monitoring Tax: Why Exporters Need Resource Budgetswriting
- How Much Prometheus Is Too Much for an 8 GB Machine?writing
- Violent Pornography — Consumption, Repetition, and the Machine-Like Side of Desiremusic
- How We Learned to See Communication Technologyperspectives
- A WS2812 on a 3.3 V GPIO Needs a Real Logic-Level Decisionwriting
- Attack — Urgency That Refuses a Gentle Introductionmusic
- Page Cache Is Not a Memory Leakwriting
- BYE Handling Is Part of Resource Correctnesswriting
- Streamline — Loss, Distance, and the Finality of Not Getting Another Conversationmusic
- Why 99.9% Uptime Does Not Tell Me When to Wake Someone Upwriting
- The Rotary Encoder Makes Lists Work Without a Touchscreenwriting
- Self-Titled Rawness vs Toxicity Precisionmusic
- Provisioning Failure Needs a Recoverable Pathwriting
- Where Should a Message Wait for an Offline Node?writing
- A Growing Queue Is Growing Work Debtwriting
- A Mobile NOC Dashboard Should Show Decisions, Not Every Metricwriting
- Removing Text and Social Features Also Reduces the Security Surfacewriting
- Least-Privilege Backup Receipts Let Operators Verify Without Reading the Backupswriting
- Obscured by Clouds — When Atmosphere Becomes the Subjectmusic
- Infrastructure Configuration Deserves Code Reviewperspectives
- What Computation Really Isperspectives
- Where the central processor Analogy Breaksperspectives
- Where Does the Cell-as-Computer Analogy Stop Working?perspectives
- The Philosophical Problem Hidden Inside Evolutionperspectives
- Overview vs Drill-Down: One Dashboard Cannot Do Both Wellwriting
- I-E-A-I-A-I-O — Memory, Nonsense, and the Strange Persistence of Soundmusic
- Another Brick in the Wall, Part 3 — When Isolation Stops Feeling Accidentalmusic
- Cirrus Minor — Stillness That Feels Larger Than the Scenemusic
- Cloudflare KV, Durable Objects, Queues, and D1 Fail Differently Because Their Consistency Models Differperspectives
- Charging Records Are Easier to Trust When I Trace the Event That Created Themwriting
- V132A: Turning Clear Audio into a Preserved Release Assetwriting
- Audit Logs Matter Because Secret Reads Are Security Eventswriting
- What Mathematics Really Isperspectives
- Heartbeat Freshness Is More Useful Than “Container Running” for Voice Workerswriting
- Automatic Rollback and Fleet Rollback Solve Different Failureswriting
- Container Network Errors Matter More Than Throughput Alonewriting
- The Device State Machine Is Part of the Product Contractwriting
- Port 5044 and the Difference Between Log Generation and Log Transportperspectives
- A SIP Load Balancer Needs Dialog Awareness Somewherewriting
- How We Learned to See Complexityperspectives
- timerfd Gave Me 21–26 Ticks When I Needed About 50writing
- Forest — Family Language, Authority, and the Question of Who Gets to Leadmusic
- 32x32 MIMO Made More Sense When I Stopped Counting Antennaswriting
- How We Learned to See Climateperspectives
- A Source-Ownership Manifest Solved the 'Who Owns This Container?' Problemwriting
- Working Set Is More Useful Than a Single Memory Numberwriting
- Worker Heartbeat Age Catches Silent FreeSWITCH Failurewriting
- AEC Starts with a Truthful Reference Signalwriting
- An AEC-Off Run Is a Control Experiment, Not a Product Settingwriting
- Retention Needs Both Time and Size Limitswriting
- Album Art as Family Collaborationmusic
- The Philosophical Problem Hidden Inside The Immune Systemperspectives
- The Backend Can Be Down Without Making the Phone Uselesswriting
- Incident Response Starts Before the Incidentwriting
- What Feedback Really Isperspectives
- Resolved Notifications Are Part of the Incident Lifecyclewriting
- Blameless Does Not Mean Cause-Freewriting
- Where the continuous production migration Analogy Breaksperspectives
- Multiple Paths Do Not Create Free Reliabilityperspectives
- How We Learned to See Numberperspectives
- Reconstructing V115 as a Known-Good Behavioral Controlwriting
- pgvector HNSW Can Return Fast Answers That Are Operationally Wrongperspectives
- ATWA — Distance From the World Without Complete Indifference to Itmusic
- The Happiest Days of Our Lives — Why Institutional Cruelty Often Hides Behind Routinemusic
- Context Switches and Interrupts Explain Some Invisible CPU Costwriting
- Up the Khyber — Rhythm as a Landscape Rather Than a Song Formmusic