{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicv5g4mlgivlcvlio5liiehwas3sx6vcbyxtrnz474f3h57y2dk3u",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3mifn4pybcau2"
  },
  "path": "/post/48064950",
  "publishedAt": "2026-03-31T11:19:19.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Programming",
    "codeinabox",
    "48 comments",
    "https://piechowski.io/post/codebase-drag-audit/"
  ],
  "textContent": "submitted by codeinabox to programming\n150 points | 48 comments\nhttps://piechowski.io/post/codebase-drag-audit/\n\n> A client’s team spent a full week adding a CSV export to their admin panel. Two engineers, clear requirements, maybe a day of actual work. The rest of the time went to understanding existing code well enough to change it safely. That’s what I call **codebase drag** : when the codebase makes every task take longer than it should. It doesn’t show up in any dashboard or sprint report.",
  "title": "Your Engineers Aren't Lazy, Your Codebase Is Punishing Them"
}