rockerest’s avatarrockerest’s Twitter Archive—№ 11,522

  1. …in reply to @kylegalbraith
    kylegalbraith ThePracticalDev Always the caveat with this advice: but optimize for unknown changes. Every time a system is designed rigidly for the problem at hand, it hamstrings future changes. I've seen it happen innumerable times. If a system is designed to handle change/expansion well, it's good.