Stay with the defaults

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the architecture category.

Last Updated: 2023-12-03

Many frameworks and libraries offer defaults - e.g. default folders to store data etc.

In general, go with them.

Case in point, I made a mistake in going against the Rails defaults with webpacker, installing to app/webpacker instead of app/assets. I wanted the small win of more logical naming, but it came at the cost of broken integrations - e.g. installing actiontext was very difficult, costing me half a day in mucking around.