The Cathedral Builder Who Forgot the Foundations
There was a stonemason in Santiago (not a famous one, not the kind they write plaques for) who spent forty years carving granite for the cathedral restorations. My grandfather knew him, or claimed ...

Source: DEV Community
There was a stonemason in Santiago (not a famous one, not the kind they write plaques for) who spent forty years carving granite for the cathedral restorations. My grandfather knew him, or claimed to, which in Galicia amounts to the same thing. The man had a saying that I never understood until this year: "O rápido nom é o que mais corre, é o que sabe onde vai." The fast one isn't the one who runs fastest. It's the one who knows where she's going. I've been thinking about him lately, this mason nobody remembers, because something is shifting in how we build software, and it has the same shape as his proverb. The decade we spent running For twenty years, the software industry has been sprinting. Agile told us to stop drawing blueprints and start laying bricks. Ship the thing. Learn from the rubble. Iterate. The manifesto was a corrective, and a necessary one: before Agile, teams spent eighteen months writing specifications for software that was obsolete by the time anyone opened an IDE.