The is a lot of wisdom in that article > It’s possible to discover what works without knowing why it works, and then to put that insight to use immediately, as

The is a lot of wisdom in that article > It’s possible to discover what works without knowing why it works, and then to put that insight to use immediately, assuming that the underlying mechanism will be figured out later. > Our accounting could reflect the fact that not all intellectual debt is equally problematic. We often talk about the technical debts we are accumulating when creating something new. But what sometimes can be worse is when one forges ahead without the proper understanding, extrapolating from familiar but possibly not applicable precedence. The complexity of modern tech makes it all but impossible for even most of us here to fully understand how our computers work - a very different situation from the time Woz was able to hold all moving parts of the Apple design in his head. We have to rely on stuff we don't understand and it can be an emotional challenge with different individuals reacting very differently. Avoidance leads to a crawling speed and attempts to reinvent the wheel when the simplest sufficient solution calls for a four wheel drive. Deliberately closing eyes is also not uncommon - believing in the magic of the solution with no regard to the laws of nature. Overly broad deep diving, studies and investigations is another anti-pattern. As is being overly conservative - my current project technical debt is way too much code as we did not fully understand the framework we build upon and feared to make the required small innovations. Finding the right balance here as an individual or finding common ground as a team is challenging.