A good solution applied to the wrong problem is still the wrong solution. Do not apply design patterns just because they worked elsewhere.
@davecathcart How far into the future do you future-proof for? Is there a Pareto Principle for time?
-
-
@DaveHogue …Better to embrace this fact. Keep it simple, and don't be scared to continually refactor code as requirements evolve. -
@davecathcart Slightly different for design (sometimes), because we often need to design "places" for things we know will be added later. -
@DaveHogue I like that. I've been calling it a design ARC where I know something may need to scale or be facilitated, so design around that -
@mustefaJ I like that phrase "design arc" - I need to find a way to incorporate it into my practice. Thanks! :)
End of conversation
New conversation -
-
-
@DaveHogue …requirements change so often that any code written for something that *might* happen usually turns out to be a waste of time…Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@DaveHogue these days I'm of the opinion that you should only code for your immediate needs (still make it clean & maintainable, of course)…Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.