Maybe helpful to split into 2 parts: code functionality = asset, code maintenance & debugging = liability. So you must balance the 2. Writing less code minimiz

Maybe helpful to split into 2 parts: code functionality = asset, code maintenance & debugging = liability. So you must balance the 2. Writing less code minimizes the liability side. Combined with a "YAGNI" stance, you can minimize your codebase total liability while writing the least amount of code required to do the job.