Frameworkless Movement
I wrote my first web app with Django. And then Rails. These frameworks taught me how a web app should be structured (models, views, controllers, services, migrations, middleware).<p>Now, if I wanted to, I could build my own application without Django or Rails, as long as I had something to accept incoming HTTP requests, make responses, and a library to make DB calls.<p>But I wouldn&#x27;t have gotten to this point had I not learned Django and Rails first.<p>I think using a framework turns many &quot;unknown unknowns&quot; into &quot;known unknowns&quot;.<p>I can read my framework&#x27;s documentation and learn it has built in logging, so logging is something I need to think about when building a web app. It lets you filter sensitive data from logs, so that&#x27;s something I need to think about.<p>This is why I was building a type of application I didn&#x27;t build before, I would look for a framework I could use, or something like it.<p>I&#x27;d use go kit for building a microservice for example. I don&#x27;t get many of the concepts involved with building a microservice (circuit breakers, service discovery, etc) and hopefully the framework would help me learn them.