Managing the code base

Our code base has started growing. We have taken the first steps in addressing the monolithic architecture problem and we have a pretty good file structure so far:

Current src/ directory structure

Although good enough for now, we should rethink our approach and create rules if we want to make this project bigger.

Quick wins

When a new developer joins the project, it may be a little challenging for them to understand our code base. Let's address a few easy fixes.

To start with, where is the entry file for our application? It's in the root directory. However, there is no clear entry point in the source (src/) directory. This is okay, but it would be handy to have it close to the story and examples...