I sympathize with the reflex, really. I never used frameworks because they seemed like a lot of overhead for some small problems, and then you had to keep migr

I sympathize with the reflex, really. I never used frameworks because they seemed like a lot of overhead for some small problems, and then you had to keep migrating, updating, etc.; that is, instead of solving a problem I had to keep solving it, over and over. Dismissing the maintenance of your solution, whatever it is, is unwise. And certainly the churn of the framework faddishness was not appealing to me. Why learn something and then simply discard all of it for the next cool new thing? Still, I got roped into a toy project. Got set to use Flask, because it seemed simple. Bought the book, got my environment set up, felt nervous but a little excited ... only to find that my partner decided that we were suddenly switching to Django. When I mentioned that I had invested the time in this (and my own money for the book) to start, I got a little "Agile up" speech, which is apparently the equivalent of "git gud." So I can see how someone might want to reject frameworks entirely: quite a lot of their in the field use seems to be churn. However, I still think a stable, mature framework would be valuable so long as upgrades are painless and infrequent, as part of a shared lingo for describing a possible solution to a problem. As a "hustle," no, that sort of thing is a huge turnoff to me, but I do not want to discard the concept entirely.