What can be learned from studying long gone development practices?
The article says:<p>&gt; Today, structured programming appears remarkably simplistic, great for writing tiny programs (it has an academic pedigree), but not for anything larger than a thousand lines.<p>Curious. I rather think that structured programming became so ultra-pervasive in any high level programming language younger than 50 years old or so[1], that we&#x27;ve lost the extra name for it. Practically every programming language that isn&#x27;t either pure functional (rarer than it seems), low level (i.e. assembly), or very very domain specific (e.g. SQL[2]) is a structural programming language.<p>Examples for &quot;structural programming languages&quot; are C, C++, C#, Java, JavaScript, python, Go, Swift, Scala, PHP, perl, Rust, D, ... You get the idea. If a general purpose language does <i>not</i> follow it, it&#x27;s something notable, like Haskell.<p>So rather, I think this is an example of something that was so utterly successful that it became absorbed into the general fabric of mainstream programming. It&#x27;s true that we don&#x27;t draw as many flowcharts as we used to, because we got more comfortable with everyday programming, but they are still how we think about code a lot, and for complex processes that we want to visualize we still do draw them.<p>[1] Not a scientific estimate. Substitute &quot;not very very old&quot; if you like.<p>[2] Funnily that stands for &quot;Structured Query Language&quot;, but not necessarily for significant reason: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;SQL#History" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;SQL#History</a>