In computer science courses at University, assignments written in OO languages such as Java had file systems similar to this:
- etc. ...
In writing some of my own projects, it seems like splitting up each class into a file is very trivial, especially when classes are very small. Are there other design patterns that circumvent having many files lots of small helper classes, or is this pretty much the only standard?