coderdbc.com https://validator.w3.org/feed/docs/rss2.html Enums Are Convenient Until You Add a Value A Changelog Is for the People Upgrading An Alert Nobody Acts on Should Be Deleted Reproducible Builds Without Never Updating Updating Little and Often Beats the Big Bump Dependencies Are Code You Did Not Review Docker for Getting Everyone the Same Database One Command to Get the Project Running Being the Only One Who Understands It Is a Trap Asking for Money With Something to Point at Keep a Record Before You Need One Stopping a Query That Will Not Finish Moving Old Rows Somewhere Cheaper Checking Then Inserting Is Not Atomic There Is No Transaction Across Two Databases Keep Transactions Short and Lock in One Order Teaching Yourself to Read Query Plans Page 40,000 Should Not Be Slower Than Page One Counting Everything Is Surprisingly Expensive Isolation Levels Explained by What Breaks An Index Is a Trade, Not a Free Win The Migration Stopped in the Middle Where the Four Hundred Milliseconds Went Nothing Changed, Except Everything The Upgrade Was Minor According to the Version Number One Page, Four Hundred Queries The Pool Was Full of Connections Nobody Closed Learning to Read What the Database Decided Debugging in Production Without Making It Worse What the Slow Query Log Is Actually Telling You Search That Is Good Enough Before It Is Clever Two People Editing the Same Record Exporting a Million Rows Without Running Out of Memory Half a Batch Succeeded. Now What? Never Store Money in a Float Versioning an Api Is a Promise About the Past Transactions Explained Through Things That Went Wrong A Health Check That Only Returns 200 Tells You Nothing Logs Are Written for the Night You Are Woken Up Every Feature Flag Needs a Date It Will Be Deleted Folder Structure Is a Bet on How the Code Will Change A Retry Loop Is a Denial of Service Waiting to Happen Store It in Utc and Argue About Display Later The Only Http Status Codes You Will Use Most Weeks Adding a Feature to Code You Are Afraid to Touch Your First Integration Test Is Mostly About Setup The Build Fails Only in the Pipeline The Column Type Is a Constraint You Get Free Making the Business Case for Boring Work Wrap the Sdk Before It Wraps You