> That said, the long list of academic references originally posted may be of little practical value for most software developers. In many cases because what t

> That said, the long list of academic references originally posted may be of little practical value for most software developers. In many cases because what they contain has been integrated (in whole or in part) into the normal order of business. Some of the big threads: Structured programming. Even C and C++ constrain their goto statements to the same function. Most other languages have similar constraints or limit them to things like named loops/breaks. So you'll learn structured programming just by learning anything but assembly or old-school BASIC and FORTRAN (where there is some structured programming, but also a lot of unstructured programming). Concurrency, Milner and Hoare's works have influenced many modern languages. CSP influenced or formed the basis of many modern concurrency systems. Go and Erlang/Elixir (anything on BEAM) are fairly mainstream languages that draw on it at least in part.ure* understanding of it because implementations aren't pure implementations of it for whatever reasons). Even many of the type systems stuff. Type inference is used by many modern languages, generics/polymorphism is also used by most modern statically typed languages. Even Go finally got on the generics train. So yeah, you don't need to study these papers to benefit from them, many (most?) modern languages are directly or indirectly influenced by them.