4 ms·
Most of the time the answer is: "Because a human has to read and understand it".
by brainzap 8y ago
Most of the time the answer is: "Because a human has to read and understand it".
- tabtab 8y agoIndeed, software design is a lot like writing technical instructions. One should think in terms of writing for humans, not so much machines. But another key dimension is dealing with changes in requirements over time. One cannot over-value their forecasting/guessing ability, and have to hedge the design to some degree. Some of the GOF design pattern writing assumed too much regularity in future changes, for example. I'd like to describe counter examples that show how assumptions of future regularity can byte one in the proverbial output port.