Best Practices
When you start many small projects in different environments its good to have some templates and best practices, that lead you through the tedious setup steps. Without the foundation you forget or jump over e.g. writing nice unit-tests, just because you do not have the place to put the stuff.
The good
RoR gives a nice example when creating a new controller. Together with the controller itself and the basic operations routes and unittests are added to the project. Some goes for creating gems with bundler. You get places to put your version, your unit-tests, your modules and your documentation.
The bad
An example in the opposite direction is starting e.g. a c++ project from scratch. There are many things to setup, before real development can start:
- how to build
- which test framework
- how to get code coverage
- how to write javadocs
- how to reference dependencies
- how to ci