I think technical debt in the right places is fine. You have to know when it's OK to cut corners and when it's not. Novice software developers will sometimes th

I think technical debt in the right places is fine. You have to know when it's OK to cut corners and when it's not. Novice software developers will sometimes think that all technical decisions are equally important, but that's not the case. Some technical decisions are way more important than others. For example, I've found that anything related to the general architecture of your app is very important and you should almost never cut corners in those areas - This includes decisions related to what framework you will use, the structure of your URLs/links, how your app will use/reuse components, database engines, etc... These are fundamental engineering decisions and if you rush those, you will likely suffer for many years. On the other hand, I found that it's generally OK to hack together the contents/features of individual pages within an app - If you mess up one page, you can always rewrite it fairly quickly. Software is like a tree - If some of the leaves become diseased and start falling off - That's OK; so long as the tree's trunk is healthy and sturdy, the leaves can grow back quickly. If the trunk is rotten and the whole tree falls down - You will have to start again from scratch... If it doesn't crush you on the way down.