What I didn’t anticipate was that, nearly ten years later, I’d discover myself back in the developer’s seat, not nostalgically however virtually. Not dabbling however constructing a genuinely complicated robotics platform. And never by relearning each framework or language that had handed me by, however by working in a basically totally different method.
For me, that private shift is the clearest sign that one thing structural has modified in software program improvement.
How we used to design software program, and why
Once I began out, we have been firmly within the waterfall period. That wasn’t ideology, it was economics. Software program was gradual and costly to construct, so the one smart strategy was to suppose very laborious up entrance.
We wrote detailed specs as a result of we needed to. Contracts relied on them. Supply relied on them. Writing a very good spec was a specialist talent, and one I occurred to be fairly good at. I may visualise what the completed product would possibly appear to be earlier than it existed, foresee areas of complexity, and describe behaviour with sufficient precision {that a} group may construct in opposition to it.