Skip to content

re: ⏳ Is Future Proofing just Overengineering? 🤹 VIEW POST


I think "future proofing" code is an idea that appeals to all of us when we are starting out, but it's almost always the wrong thing to do. You don't know what the future brings, and you are adding functionality that's not being used, making it harder to read your code. Chances are, the future that you imagine will never come, and you've added complexity for no good reason.

My personal opinion is that when you see code that's "for future use", delete it.

code of conduct - report abuse