The latest articles on DEV Community by Aschwin Wesselius (@aschwin). https://dev.to/aschwin https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F127529%2Fdbd747ee-9ec2-47f6-81f4-f202c7fbce43.jpg https://dev.to/aschwin en Aschwin Wesselius Fri, 16 Aug 2019 14:27:58 +0000 https://dev.to/aschwin/impact-of-technical-debt-on-health-5op https://dev.to/aschwin/impact-of-technical-debt-on-health-5op <p>As soon as a developer writes one line of code, it needs to be dealt with later. It either gets deleted or maintained.</p> <p>In case it gets maintained, a developer gets confronted with it later, time and time again. It could be you, it could be your (future) colleague.</p> <p>We now understand that choices we make today will impact the quality of the system and the project later. The better we make these choices, the less technical debt we incur.</p> <p>Often we know we could do better, when more time or budget would have been provided. We cut corners.</p> <p>Each time we see bad (or less optimal) code we get the urge to improve it. At least I do. If the application is bad, the urge is huge. If the application is horrendous the urge is getting even painful.</p> <p>My question is, is this anxiety healthy? I reckon, no form of anxiety is healthy and being exposed to such technical debt each day is very unhealthy.</p> <p>If I see such bad code I want to change it. I want to change it now, until it is out of my sight. But I can't. Do you relate?</p> anxiety legacy technicaldebt health