I do not want to weigh in on the issue as a whole, but rather shed some light on an aspect you as a single coder have probably not given much thought to: access

I do not want to weigh in on the issue as a whole, but rather shed some light on an aspect you as a single coder have probably not given much thought to: accessibility and maintainability. When I started using ruby on rails, adhering to all the conventions DHH came up with, especially the directory structure, felt like giving up a lot of control. And I, too, liked control. But I had an epiphany when I first had to work with other people's rails code: Never before did it take me so little time to dive into and familiarize myself with someone else's code. I was productive at day one, while my customer did not really expect any results for the first 4-5 days. So, if you ever plan on having someone else work with you on your code, or you need someone to take over maintenance of it, having a foundation that other people are already familiar with and where there is tons of documentation available, is a huge advantage. But even if you stay alone on this project. With all you have learned, it is possible that you will approach your next project in a completely different way. In that case coming back to your old codebase in 6 months or a year will be painful. Having a consistent framework for all of your projects helps mitigate this kind of pain a lot.