I’ve been creating software program for a few years now. Many years. I’ve realized quite a bit alongside the best way, and I dare to suppose that I’ve collected some knowledge about software program improvement value sharing with others. In some unspecified time in the future, you suppose “Yeah, I’ve bought a grip on this factor.”
And each on occasion, you could have some revelation that’s the fruits of what you’ve realized alongside the best way. I’ll always remember the second I understood dependency injection. Of course you’d need to move in an abstraction moderately 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, nevertheless it struck me all of a sudden that actually good software program design is all about preserving your choices open for so long as attainable—that you need to defer any selections to the final minute.
Now, this appears counter-intuitive. We’ve at all times been informed to plan every part out forward of time. That we shouldn’t begin the undertaking with out having thought of each element that may be thought of. That we have to determine it out now so there aren’t any surprises.
I can simply think about the dialog:
Engineering director: “How’s the planning occurring the brand new undertaking?”
Improvement lead: “Nice, we’re able to get began.”
Engineering director: “What database did you decide?”
Improvement lead: “Haven’t determined but.”
Engineering director: “Authentication?”
Improvement lead: “Not but.”
Engineering director: “Wait… what?!”
