I’ve discovered firsthand a counterintuitive truth - the best way to learn web development is abstractions on down, not core primitives on up.
I'm convinced that the best way to learn web development is abstractions on down, not core tech on up— A$AP Hashim (@hashim_warren) November 2, 2019
Imagine learning how to engineer a car before learning how to drive. You need a mental model of how things are supposed to work.
So you know that to prioritize or skip
When I worked at a coding bootcamp, I witnessed students build three production quality apps in 12 weeks by using a framework like ASP.NET, and a front-end component library like Bootstrap. The brilliance of this approach is a learner can focus on mastering what’s important, what’s unique, and what’s difficult, instead of wasting time solving trivial problems, or fiddling with infinite options.
Have you seen the stats? Only 4% of learners who use online tech courses ever finish the course they purchased. I believe part of the reason for those failure rates is that well-meaning instructors swamp students by starting them off with the basics, then building knowledge up. That’s not the best way to learn. You need to taste a cake before you can attempt to bake one. And after that, you should follow a good recipe, before you try to master ingredient selection and preparation.
Gatsby gives you both a delicious cake to taste, and a good recipe for baking your own! Let’s explore how:
If you are experienced with using the command line, you can use Gatsby’s CLI and the
gatsby new command to spin up a React project for you. Then you can get started creating pages by dropping JSX-based templates in the “pages” folder. And Gatsby handles the routing for you!
When the TypeScript project adopted Gatsby for their site, it was in part because team members who are not familiar with React could participate in page creation by learning JSX, which is a templating language that favors HTML. Also, when my colleague at Gatsby, web designer Lennart Jörgens, started building Gatsby starters he was excited that a little JSX knowledge was all he needed to be productive. From there he learned React and GraphQL quickly, and even joined Gatsby’s core team.
But what if you’re not familiar with running Node or working on the command line, as the method above requires?
Gatsby Cloud can auto-provision your site with a starter template and content sourced from a headless CMS. No command line needed.
You can immediately begin publishing content through a friendly CMS interface, then inspect both the templates and composed files in your git repo to see what’s going on. From there you can tinker with your site by changing, extending, or copy-pasting components.
And because Gatsby development relies on a modern, git-based workflow, you can branch your project, screw it up, and roll it back without consequence. With Gatsby, you can play, which is essential for rapidly learning difficult subjects like programming.
Now, compare that smooth learning experience I outlined to the pain I ran into when I attempted to adopt React the first time. I just wanted to build React-based “blocks” for Gutenberg, the new visual editor for WordPress. Before I could even see words on a screen I had to wrap my head around a mess of tooling, dependencies, and conventions I’d never encountered before. Frustrated but determined, I purchased a course on webpack, but quickly found myself trapped in the third realm of configuration hell.
I wish I’d have started my journey with create-guten-block or the Advanced Custom Fields block builder, two tools for rapid Gutenberg development. That way, I could have started learning with something functional to break apart and study. Abstractions on down…
I’m excited that I am now learning React not just to extend an editing experience for one CMS, but to build general websites and apps. A Gatsby project is a React project, so the React ecosystem can be used on a Gatsby site. Mastery of Gatsby gives you transferable skills - you are not confined to just one framework.