Technical Debt Is Like a Tetris Game
fluentcpp.com
Technical Debt Is Like a Tetris Game
1–10 of 122 posts
Re: Technical Debt Is Like a Tetris Game
#2Re: Technical Debt Is Like a Tetris Game
#3The art is to find the sweet spot.
Re: Technical Debt Is Like a Tetris Game
#4Might actually be the best metaphor I've seen on this topic
Re: Technical Debt Is Like a Tetris Game
#5I tend use the "Leaning Tower of Pisa" metaphor. If it leans too much, the tower will fall down. If it doesn't tilt at all, you won't sell tickets to tourists. The art is to find the sweet spot.
Re: Technical Debt Is Like a Tetris Game
#6I tend use the "Leaning Tower of Pisa" metaphor. If it leans too much, the tower will fall down. If it doesn't tilt at all, you won't sell tickets to tourists. The art is to find the sweet spot.
I dont know about that... Eiffel tower is vertically straight and sells a lot of tickets.
Re: Technical Debt Is Like a Tetris Game
#7Re: Technical Debt Is Like a Tetris Game
#8Re: Technical Debt Is Like a Tetris Game
#9The only thing that works with technical debt is to aggressively uncover and strike down any short term incentivisation from an organization perspective, and to set in absolute concrete terms what the irrevocable code maintenance policy is, and punish those who don't follow it. Everything beyond that, TD measurement tools and TD backlogs (which you interlace at a minimum ratio) are just details.
But the last thing that'll help you is talking about Tetris in front of your client / PO / boss / whatever. Just call it "maintenance work". And if they're hostile to even that, it means they're stupid enough that you can just do it anyway and call it something else and they'll never know.