There are distinct schools of thought. "How to structure a program" is subjective but also divisive! Here are the major ones (that I'm aware of), making an eff

There are distinct schools of thought. "How to structure a program" is subjective but also divisive! Here are the major ones (that I'm aware of), making an effort to be inclusive: 1. Functional programming. It's possible I'm doing a "retcon" on several models here, but these are a fair start: 1.1. http://www.erlang.se/doc/programming_rules.shtml http://www.erlang.se/doc/programming_rules.shtml 1.2. https://www.seas.upenn.edu/~cis341/current/programming_style.shtml https://www.seas.upenn.edu/~cis341/current/programming_style... 2. C (the language) organization. Embedded, linux kernel, and many open source projects follow this pattern. O'Reilly books are a good start. 3. Java. There are so many competing strategies that the "no true scotsman" fallacy applies. Here's one that seems uncontroversial: https://www.udemy.com/java-design-patterns-tutorial/ https://www.udemy.com/java-design-patterns-tutorial/