I think it's easy to go in circles with the concept of "future proofing" and definitely see it as over-engineering a lot of the time.
Counter-intuitively I think it can also legitimately harm the future when it really is just over-engineering.
I see future-proofing as making sure to not close the wrong doors at the interface level, and to keep technical debt under control. Nitty gritty code cleaning has some value, but I wouldn't call it future proofing in and of itself.
How’s it going, I'm a Adam, a Full-Stack Engineer, actively searching for work. I'm all about JavaScript. And Frontend but don't let that fool you - I've also got some serious Backend skills.
Location
City of Bath, UK 🇬🇧
Education
10 plus years* active enterprise development experience and a Fine art degree 🎨
I think it's easy to go in circles with the concept of "future proofing" and definitely see it as over-engineering a lot of the time.
Counter-intuitively I think it can also legitimately harm the future when it really is just over-engineering.
I see future-proofing as making sure to not close the wrong doors at the interface level, and to keep technical debt under control. Nitty gritty code cleaning has some value, but I wouldn't call it future proofing in and of itself.
I think this sums it up better than I could have, thanks Ben.