4 ms·
In my 25+ years of experience, any code you write today, however beautiful you think you wrote it, will get stale in a few years and has to be changed/enhanced
by neeleshs 2y ago
In my 25+ years of experience, any code you write today, however beautiful you think you wrote it, will get stale in a few years and has to be changed/enhanced to adapt to the new reality.
With experience, you learn to find balance between pragmatism and purity more often than not. You will still not always be right.
It is all still a mix of skill, experience, team and external factors.
- deleted 2y ago[deleted]
- hinkley 2y agoWhen I’m working in lower-case c clean code, the amount of friction due to regrettable decisions made before everything became clear is unfortunate but manageable. When we have decisions that aren’t just regrettable but daunting (how on earth am I going to unravel this warren of pain and stupidity enough to get this thing to do what it’s supposed to do and only what it’s supposed to do??) then the full weight of the sins of the past hits, and we start making proclamations and resolutions about Never Again. You don’t have to run away from the falling axe or ban axes. You need to not be there when it falls. And in the context of software what that looks like is very difficult to explain without ascribing unnecessary or even misguided qualities to the differences. We keep describing analogs, symptoms or harbingers of the real problem, and those fall down or distract.