A lot of "best development practices" exist as ways to ensure that multiple developers can all easily pickup a new project and collaborate on it successfully wi

A lot of "best development practices" exist as ways to ensure that multiple developers can all easily pickup a new project and collaborate on it successfully without conflicts. Yeah, go hog-wild and do whatever makes you happy as a solo act, so long as you do things securely and protect your users. By definition, there's no conflict between developers possible. You might pay a price later if you do things your way and get too successful, but that's a better problem to have than being too late to market with your great idea just because you were trying to do things "the right way".