2 ms·

I've found that designing for extensibility is wrong more often than right. The code doesn't stretch the way you expect, and then it strains against other bound

• jmadsen 11y ago
  that's not quite what I mean. saying, "I think it will need feature X, which will require parameter x_id, so I'll add x_id = 0 now" is wrong. writing (just as an example) a function that takes an config array as its param so you can later build out, instead of passing a_id, b_id, c_id...."oh, crap, how long a list will this be?" in the early build is the type of thing I mean. Writing extensible code more often than not causes you to write smaller, tighter, more testable components. Writing in this style is what I'm trying to say. Many less experienced devs would not do this and end up with long procedural code because they feel it is wasted time for something they aren't anticipating.