Learn, don’t apply
Learn new libraries, npm packages, and development methodologies, but don’t apply them to your current projects until best practices are formed. This might take some time, hence the next rule…
Wait one year
Don’t implement any library, package or methodology for a period of one year after it’s initial release. The hurry to implement the latest & greatest is a big factor in contributing to your fatigue. Just hold the brake, and wait.
Avoid projects that seem like they do magic even under the strongest of temptations, until you actually learn what is going on behind the scenes. Understand what is going on with your code, and code you utilize. That understanding will help ease your mind’s fatigue.
Avoid implementing large libraries or developmental methodologies that would be crucial to the core of your project if they have few past GitHub issues or lack community involvement. If implemented, the support will lie solely on your knowledge and findings, so be aware. Give back to community projects wherever possible to ease other’s fatigue.
Do upgrade libraries, packages, and platform updates that contain only bugfix or non-breaking updates, however wait a couple weeks before doing so to make sure the version is stable. Don’t update code containing breaking updates if you don’t understand those updates or what is involved with the update process.
Written by Mark O. Shust, a Magento Certified Developer & Architect in Cleveland, Ohio.
Follow me on Twitter @markoshust
- Previous Post:
← Create and deploy a NodeJS Express app with Docker
- Next Post:
Making Docker for Mac Faster with the Overlay2 Filesystem →