Some lessons I’ve learned from experience.
1. Install Stuff Indiscriminately From npm
Become totally dependent on others, that’s why they call them “dependencies” after all! Lean in to it.
Once your dependencies break — and they will, time breaks all things — then you can spend lots of time and energy (which was your goal from the beginning) ripping out those dependencies and replacing them with new dependencies that will break later.
Why rip them out? Because you can’t fix them. You don’t even know how they work, that’s why you introduced them in the first place!
Repeat ad nauseam (that is, until you decide you don’t want to make websites that require lots of your time and energy, but that’s not your goal if you’re reading this article).
2. Pick a Framework Before You Know You Need One
Once you hitch your wagon to a framework (a dependency, see above) then any updates to your site via the framework require that you first understand what changed in the framework.
More of your time and energy expended, mission accomplished!
3. Always, Always Require a Compilation Step
... continue reading