I’ve been growing software program for a few years now. Many years. I’ve discovered rather a lot alongside the way in which, and I dare to assume that I’ve collected some knowledge about software program improvement value sharing with others. Sooner or later, you assume “Yeah, I’ve obtained a grip on this factor.”
And each every now and then, you may have some revelation that’s the end result of what you’ve discovered alongside the way in which. I’ll always remember the second I understood dependency injection. Of course you’d need to cross in an abstraction fairly than create an implementation!
I had the same revelation this week. I’m certain there are many sager builders amongst you who’ve already figured this out, however it struck me all of the sudden that basically good software program design is all about holding your choices open for so long as potential—that you need to defer any choices to the final minute.
Now, this appears counter-intuitive. We’ve all the time been informed to plan all the pieces out forward of time. That we shouldn’t begin the challenge with out having considered each element that may be considered. That we have to determine it out now so there are not any surprises.
I can simply think about the dialog:
Engineering director: “How’s the planning happening the brand new challenge?”
Growth lead: “Nice, we’re able to get began.”
Engineering director: “What database did you choose?”
Growth lead: “Haven’t determined but.”
Engineering director: “Authentication?”
Growth lead: “Not but.”
Engineering director: “Wait… what?!”
