There are so many frameworks, tools and layers of abstraction out there that I find it helps to dip down a layer and taste what life is like without framework o

There are so many frameworks, tools and layers of abstraction out there that I find it helps to dip down a layer and taste what life is like without framework or tool X. Ideally, it's quite painful and you immediately appreciate what the tool is getting for you. You also might learn that the tool would be very helpful for circumstances you do not currently face (e.g large scale software engineering when you are exploring via a side project), and hang out in the lower layer until further motivated to climb back up. Some concrete examples: - you are using THREE.js. Try out raw webgl to draw a square. Run frighted back to THREE.js' arms and have some appreciation for what it is doing for you - you are new to web development. Try working with the DOM directly. Then try something like knockout or angular that helps track dependencies between your view model and the dom. Then try out React. React has achieved wide-spread acceptance for a reason, I think it's the best pattern. But it's also the most abstract from the reality of what's happening underneath the hood, so taking steps up to the top can really help - you are playing with scikit-learn and throwing various models at a classification problem. try implementing basic logistic regression using only numpy arrays. Try to understand how you could adapt your implementation `fit`, `transform` and `predict` interface used by sklearn. A couple of recent articles that show this habit in practice: https://zapier.com/engineering/how-to-build-redux/ https://zapier.com/engineering/how-to-build-redux/ https://medium.com/@karpathy/yes-you-should-understand-backprop-e2f06eab496b https://medium.com/@karpathy/yes-you-should-understand-backp...