Same. I spent so long building Django apps and trying to solve problems that StackOverflow told me were inherently difficult, only to find out that Rails has built-in solutions.
This isn’t even a criticism of Django; the things that Django does, it does very well. But there are a lot of things that it doesn’t do that a mature web app will eventually need to handle.
My biggest issue with rails is that the convention it forces you into feels like it's not really a one-size-fits-all solution. I typically build sites that are a one-page or 2-3 page JS app running on an API, as opposed to the more traditional idea of backend paths that return html views. And it seemed like rails wasn't well-suited to that, which was why I didn't stick with it.
Yeah me too. I am still sad thinking about the number of hours I spend messing with python environments and versions because I was told it was the “quick and easy” option for solving this or that small problem.*
Also worth mentioning Michael Hart’s intro course, which is a really shockingly well done way to ramp up from absolute zero, even for someone with very little code experience.
His book is what got me up to speed in 2015. I was visiting Chiang Mai and binged through the whole thing over a few days and then spent the next week cloning various personal projects I'd written with JS backends.
In under two weeks of opening Michael Hartl’s Rails Tutorial, I was already more productive with RoR than with the stack I'd been using professionally for 3+ years.
I just didn’t know how much faster building web apps could be.