Jeremy on the divide between the core languages of the web, and all the tooling that exists to produce code in those languages:
On the one hand, you’ve got the raw materials of the web: HTML, CSS, and JavaScript. This is what users will ultimately interact with.
On the other hand, you’ve got all the tools and technologies that help you produce the HTML, CSS, and JavaScript: pre-processors, post-processors, transpilers, bundlers, and other build tools.
Jeremy likes the raw materials side the best but acknowledges a healthy balance of both worlds is a healthy mix.
I think a great front-end developer is hyper-aware of this split. Every choice we make is a trade-off between developer productivity and complexity management and the user’s experience. The trick is to punish the user as little as possible while giving yourself as much as you can.
