A good solution applied to the wrong problem is still the wrong solution. Do not apply design patterns just because they worked elsewhere.
-
-
Replying to @DaveHogue
@DaveHogue ...Over-engineering for the sake of "future-proofing" creates more work, not less1 reply 0 retweets 0 likes -
Replying to @davecathcart
@davecathcart How far into the future do you future-proof for? Is there a Pareto Principle for time?3 replies 0 retweets 0 likes -
Replying to @DaveHogue
@DaveHogue …Better to embrace this fact. Keep it simple, and don't be scared to continually refactor code as requirements evolve.2 replies 0 retweets 0 likes
Replying to @davecathcart
@davecathcart and if we didn't create a "place" now, then the risk of unstructured, organic growth + complexity increases greatly.
3:12 PM - 12 Jan 2013
0 replies
0 retweets
0 likes
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.