What Software Engineering Really Is: Beyond Writing Code

A software engineer and writer argues that the profession is best understood as a form of engineering where code is simply the material, not the craft itself. Unlike doctors, lawyers, or civil engineers, software engineers lack a physical referent that pushes back and signals when they are wrong, making the work uniquely abstract. The core of the job, the author contends, comes down to four activities: decomposing fuzzy problems, modeling reality into data structures, navigating tradeoffs, and managing the entropy of systems that decay over time. Poor decisions in software, particularly around modeling and naming, can silently shape years of future development, which is why experienced engineers appear to obsess over details that seem trivial. The piece concludes that software engineering is defined less by technical tools, which change each decade, and more by the ongoing act of deciding under uncertainty with compounding consequences.