Owning the issue is one thing, but being able to fix issues with a reasonable amount of resources is another. To me code created like this smells like technica

Owning the issue is one thing, but being able to fix issues with a reasonable amount of resources is another. To me code created like this smells like technical debt. When bugs appear after 6 months in production - as they do, if you didn't fully understand the code when developing it, how much time, energy and money will it cost to fix the problem later on? More often than I like I had to deal with code where it felt like the developer did'nt actually understand what they were writing. Sometimes I was this developer and it always creates issues.