@mraeburn.linkBoards see tech as risk; leaders should treat it like a balance sheet. Make technical debt visible: quantify backlog in effort and ops cost, prioritise by ROI and change‑risk, and fund a steady 'amortisation' budget. Conversations become trade‑offs, not blame. #technicaldebt #technicaldebt
@mannypalachuk.bsky.socialTechnical debt won't clear itself during normal workflow. You need dedicated hunt time. Swarming Sprint or Pinpoint Sprint — which one does your shop need right now? Drop it below.
@mannypalachuk.bsky.socialThe team didn't create the technical debt.
The absence of a system that made it visible created the debt.
@akritiko.bsky.socialEvery OSS project has that one issue open since 2019, 'investigate flaky test,' 47 comments, 0 fixes.
Basically the project's haunted house. Nobody goes in.
@mannypalachuk.bsky.socialThree types of tickets are hiding in your queue right now. Age Rogue. Time Rogue. Super Rogue. Each one exposes a different weak point in your prioritization. Save this and go find yours.
@mannypalachuk.bsky.socialA team that tolerates 90-day-old tickets will eventually tolerate 120. Then 180.
The tail trains your team what normal looks like.
@mannypalachuk.bsky.socialMost service desks aren't working the wrong tickets — they're working them in the wrong order. The fix: highest priority first, oldest to newest. Which one does your team run? Drop 1, 2, or 3 below.
@mannypalachuk.bsky.socialThe age rogue is old and forgotten.
The time rogue is heavy with hours and going nowhere.
The super rogue is both. Know which one you're hunting.
@mannypalachuk.bsky.socialGuess before you look — how old do you THINK your oldest open ticket is? Write it down, then go check your PSA. Comment both numbers, your guess and the real one. I want to see how far off people usually are.
@mannypalachuk.bsky.socialYou can argue with a number.
You can rationalize a count.
You cannot rationalize a picture that shows you exactly what's been living in your system.
@makyoai.bsky.socialReading that postmortem was the first time it felt less like a preference and more like a diagnosis.
What does your codebase remember that you don't?
#AI #vibecoding #technicaldebt #softwarearchitecture #buildinpublic
@mannypalachuk.bsky.socialEvery service queue has three kinds of tickets hiding in it, and most owners can only see one. Age Rogue, Time Rogue, Super Rogue — save this and find yours. Full framework: ITServiceRunGuide.com
@endrilickollari.bsky.socialDebtDrone CLI v2.2.0 is now available 🚀
Explore the release and start scanning your repositories locally:
github.com/endrilickollari/debtdrone-cli/releases/tag/v2.2.0
@makyoai.bsky.socialThe bottleneck moved from writing software to understanding it. Where's yours?
#AI #vibecoding #technicaldebt #softwaremaintenance #buildinpublic
@fastruby.ioThe tell for tech debt is not a broken build. It is estimates quietly stretching and a few tests marked skip so the suite stays green. go.fastruby.io/7hl #TechnicalDebt
@alangnixon.bsky.socialThen you have to add #TechnicalDebt which causes thousands more lines of code to be spewed out in order to fix the thousands of original lines. This is already happening in real time as 'coders' struggle to get something that works.
@makyoai.bsky.socialTechnical debt used to compound at the speed of developers. What's it compounding at now?
#AI #vibecoding #technicaldebt #softwareengineering #buildinpublic
@mannypalachuk.bsky.socialThere are three types of tickets hiding in every service queue — most owners have only noticed one. Age Rogue, Time Rogue, or Super Rogue: which one is living in your system right now? Tell me below.
@programmerhumor-io.bsky.social