The modern software engineer throws away the requirements specification because the computers he commands are fast and the people he negotiates with are slow. He ignores archival science because his business records are digital and the musings of a geriatric archivist are not compatible with PostgreSQL 18. He adopts the posture of an industry thought leader on X but has never read a standards document in his life. He believes he has little in common with the Roman aqueduct engineer but finds himself in management meetings pleading for more byte-sized stones for the stone god.
Lawyers are informed by ancient case law and bankers leverage trade instruments with roots in medieval Italy. Why is the software profession so exceptional that replacing hundreds of years of engineering wisdom with blog posts on agentic workflows is considered best practice?
Comments
The modern software engineer throws away the requirements specification because the computers he commands are fast and the people he negotiates with are slow. He ignores archival science because his business records are digital and the musings of a geriatric archivist are not compatible with PostgreSQL 18. He adopts the posture of an industry thought leader on X but has never read a standards document in his life. He believes he has little in common with the Roman aqueduct engineer but finds himself in management meetings pleading for more byte-sized stones for the stone god.
Lawyers are informed by ancient case law and bankers leverage trade instruments with roots in medieval Italy. Why is the software profession so exceptional that replacing hundreds of years of engineering wisdom with blog posts on agentic workflows is considered best practice?