Biggest point to hammer home home here is use MVC folder organization. Use a framework that already exists, if possible. Standardize your process for creating w

Biggest point to hammer home home here is use MVC folder organization. Use a framework that already exists, if possible. Standardize your process for creating webapps so you (and your team) can get to writing the code that actually matters as quickly as possible. Ideally you want to decide on; A) Your code style, file organization B) Your HTTP routing C) Your views or data format (JSON responses only?) D) Your database E) How you interface with your database F) How you maintain your database (migrations, etc.) G) Testing Pick these for yourself. Use the same processes repeatedly. Document the processes. This is where opinionated frameworks save huge amounts of time. You'll find the process that works best for you, but if every developer you meet has a process that is somewhat orthogonal at one level, you'll have to create a new one when you work together. This is a waste of time. One of the reasons Rails is so outstandingly popular is because it gave a common set of tools to backend developers and a set of patterns everybody could share. These sorts of questions about organization are the ones I had when I first built Nodal [1], and I was frustrated to find the best MVC solutions in the Node space didn't give me anything close to what I was working with coming from Django and Rails. That said - use what works for you. Bonus points if it also works for the other developers you're working with. ;) [1] https://github.com/keithwhor/nodal https://github.com/keithwhor/nodal