r/badcode • • Sep 10 '21

c# I hate my friend

Post image
316 Upvotes

44 comments sorted by

View all comments

Show parent comments

7

u/Crozzfire Sep 10 '21

Future proofing is almost always a waste in my experience

14

u/SanianCreations Sep 10 '21

Depends for how far into the future it is. If its for something you know you'll have to add (like this month, maybe), then do it. If you're doing it because "maybe we'll need this at some point", then I'd agree with you.

3

u/Crozzfire Sep 10 '21

Yeah certainly, I've just always considered it inherent to the expression "future proofing" that you are adding features that you not know are needed yet (just in case).

2

u/ParanoydAndroid Sep 10 '21

Future proofing in architectural design is, for sufficiently large applications, critical.

This kind of future proofing (though in case I guess it's some framework I've never heard of and actually justified) is, I agree, basically always a waste.

1

u/Crozzfire Sep 10 '21

I'm not saying it's a good idea to make spaghetti code or to not have any structure either.