40 Reasons Why…
Starting from scratch is no longer practical. There are too many best practices for any individual to track. The era of starter kits is here.
You Need a Starter Kit
That’s over 40 decisions. I couldn’t fit them all on a single Powerpoint slide. This list is so long that most teams overlook dozens of important concerns. I’m consulting front-end developers all over the world and see a common theme: Automated testing is extremely rare. As is minification, cache busting, bundle splitting, linting and more.
All too often, developers are choosing the path of least resistance. This means most of the concerns above are ignored.
It’s a classic problem: Cutting corners in the short-term slows us down in the long-term.
The first step toward a solution is simple: Schedule a team meeting with a simple agenda:
- What are our JS pain points?
- Would we benefit from a JS starter kit?
- Would we benefit from a demo app?
But in reality, each team has unique needs and opinions, so most teams benefit greatly from creating their own starter kit. By all means, explore a few boilerplates that are popular for your library or framework of choice. But I suggest starting from scratch, using your favorites as inspiration. This assures you understand how it all works.
Inspired? I’d love to see what you build!