undefined | Better HN

0 pointsImustaskforhelp1mo ago0 comments

I feel like it is important to manage the risk and to clearly manage this debt. personally I try to stay safe from both debt and technical debt until there are sound reasons for both.

It is KISS stack for me personally (Keep it stupid simple)

I would still consider technical debt to be different than other forms of debt though, It feels way more of a tradeoff to me but perhaps all debt can be classified as such. Either way I think it makes for an interesting decision nonetheless.

0 comments

2 comments · 2 top-level

moron4hire1mo ago

Yeah, how you end up acquiring technical debt can mean a lot. If it's because the system is underspecified, then your technical debt is really a prototype. If it's because your team doesn't know what they are doing, you're kind of screwed either way. But if you have the right requirements and the right team and you know you're trading money today for time tomorrow, it can be the difference between meeting a deadline or getting canned.

kanwisher1mo ago

If the product fails all technical debt goes away. So using technical debt to prove out a product is very different. Cause often times you don’t have the money or resources to build correctly at first since you don’t know if the expected payoff will be there

j / k navigate · click thread line to collapse