Reverse, reverse.
To kick off the third week, the section today finished off orthogonality with a mention of its importance in documentation, proceeding to move onto reversibility.
Most decisions made for the first time turn out to not be ideal ones. Software from third party vendors only breaks once already installed, project requirements drastically change when the current MVP doesn’t sit right with users, and so on.
In an effort to guide the readers into making decisions with more sight, this passage was provided:
“The mistake lies in assuming that any decision is cast in stone — and in not preparing for the contingencies that might arise. Instead of carving decisions in stone, think of them more as being written in the sand at the beach. A big wave can come along and wipe them out at any time.”
For someone looking to potentially break into software engineering, this notion of reverse compatibility is something that can make or break a project or interview question before it even starts.
Are the decisions I’m taking now giving me enough freedom to make necessary changes in the future?
That concludes day 10. See you tomorrow!
#PathToSWE
