923 Days Ago I Typed “How to Make a Website” into Google (My Journey Learning to Code)

923 days ago, it was day 1 of learning how to code.
I was consuming Pieter Level’s “How to Bootstrap a Business” presentation.
And something stopped me.
He said,

“To build your idea, you should learn to code yourself.
Just open Google and write, ‘How to make a website.’
The biggest thing in coding and business is learning how to learn. Or learning how to figure things out yourself.”

Just Do It
I’d never considered that.
Back then, I wanted to build a map of the world’s best surf spots and provide cheap flight and beachfront hotel discounts to them.
So 923 days ago, I did what Pieter said.
I literally typed “How to build a website” into Google and began learning to code.
Here’s a recording of me literally doing it on day 1.
Check it out.

I did this for 3-4 days. But I began to feel constrained or stuck.
Like, I didn’t know what to learn next.
So I asked a friend.
She was so excited about what I was doing!
She told me to learn HTML, CSS, Bootstrap, Javascript and jQuery. And to do it using Treehouse.

So that’s what I did.
I’d take a tutorial.
Then I’d code on my project for as long as I could and slowly I’d become completely stuck.
Like in this photo when I couldn’t figure out how to show multiple surf spots without the code being un-godly long (Javascript loops!).
At that point, I’d take another tutorial.
Once I’d figure out how to keep going, I’d continue coding the project.
Rinse. Repeat.

In case you want to learn to code too, here’s the exact tutorials I took at Treehouse:

HTML BasicsCSS BasicsBootstrap BasicsBeginning Javascript TrackjQuery Basics

Learning How to Use a Database
After getting stuck because I my code was getting crazy long
my friend told me to check out Firebase for my first database.
I Googled around and found this Firebase tutorial playlist by The Net Ninja.
I watched each video, did the full tutorial and slowly figured out how to create, read, update and delete (CRUD) items in a database.

This was completely game-changing.
I remember feeling like I could build forever at this point.
Here’s a PNG of what the project started to look like.
I still needed to Google how-to’s for almost everything, but I could build and build and build.
It was so empowering.

Learning How to Use APIs
A few weeks from here, I wanted to add a map with pins to my site.
This was my first time engaging with an API.
I learned how to do this from this YouTube tutorial by Brad Traversy.
From that one tutorial, I added a map with surf spots and places to stay right next to the waves.
I was so amped on it. I remember wanting to show everyone I know.
Here. Check it out in this GIF!

It’s worth mentioning, Brad is my favorite online teacher by far.
I’ve taken every YouTube tutorial he has online. And I’ve bought multiple of his Udemy courses.
Any course Brad makes is worth its weight in gold.

Feeling Unstoppable, Then Getting Stopped
Once I figured out how to plug into APIs I felt unstoppable.
With all the knowledge above, I coded and built Surf Trip List for 9 months.
Here’s a video of me explaining the end product if you want to see it.

It’s a story for another time, but life changed and I gave up on Surf Trip List.
If I’m honest, I got pretty depressed at this point too.
I felt like a total failure.
I kept starting other projects, but I couldn’t finish them.
I remember wanting to build a project with the languages I knew.
But I felt constrained.
Like it’d be super hard to build a large project with only Javascript.

When Stuck, Build for Someone Else
Finally, I decided to build a project for someone else (a blog for my fiance) as a forcing function to learn React.
At this point, I had a full-time job.
So I’d learn for an hour here or an evening there.
I took the React Docs tutorial (three times lol) and read through the docs multiple times too.
And I took Brad’s MERN Front to Back Udemy course and all his React related courses YouTube. Here’s the best one to start with.
I should have filmed some of this.
But like I said, I just needed to complete something here. I wasn’t in the mind space to share the journey then.

Learning NextJS
As I went, I learned React wasn’t great for SEO.
So I did some research and found Guillermo Rauch’s NextJS.
NextJS is incredible.
It’s a React framework for static sites.
It’s server-rendered, so it’s crazy fast and optimized for SEO.
I read the docs and took this tutorial (which is so good, btw).

Learning Tailwind CSS
At this same time, I learned about Adam Wathan and Steve Schoger’s Tailwind CSS.
It’s basically Bootstrap on steroids.
It’s a CSS library that you can customize as much or little as you want.
Here’s the tutorial I used to start.
I even bought Tailwind UI for all the pre-built components and templates, and it sped up my dev process at least 2X.

Ready to Go! Well Almost…
So I had my fiance’s blog all set up (with placeholder content).
Here’s a screenshot of it.
My plan was to convince her to write the blog in Markdown.
(And push it up to Github with git CLI commands. lol)
Which yeah… would never have happened.

Learning Sanityio
Luckily, my buddy Dylan Jhaveri saw this and told me about Knut Melvær’s Sanity.
Sanity is a customizable CMS (like Wordpress) that serves up content to the DOM with the perfect amount of flexibility.
I worked through their docs to understand it and used this Next/Sanity template by Shaswat Saxena to re-start my project with Sanity.
Here’s a screenshot of the Sanity Studio I set up for my fiance’s site:

React’s Context API
As always, I built until I got stuck.
I hit a place where I needed a tool to help manage semi-complex interactivity on the site (in coding terms this is the ability to more easily manage state).
In Lehman terms: If you click on this button, have the code change these elements inside these four different files.
Changing the state of elements inside numerous files gets messy. So you need a state manager.

After some Googling, I found React’s Context API (it’s React’s version of Redux, which I had heard of before).
I took this Brad Traversy tutorial and learned the Context API. Start at 15.00.
Here’s a photo what I ended up with inside my code:

Ability to Build Forever
After this point, I felt like I could build and build and build again.
I’d still Google simple things (and always will), but I could flow.
And after many nights and weekends (since I have a full-time job) I finished my first React project!
My fiance’s site still has placeholder content…
But check it out in this GIF.
I’m super stoked on how it looks and works anyways.

After that, I built my most recent project — a whole other site called Remote Dev Jobs.
This is totally under construction, but it’s been amazing to hack on a project again.
It looks like this so far. Here’s the GIF.

And with all that, I feel empowered to take on projects that seemed too big previously.

So to sum my journey learning to code!
Summary of Tutorials

HTML BasicsCSS BasicsBootstrap BasicsBeginning Javascript TrackjQuery BasicsFirebase CourseGoogle Maps APIReact Docs’ TutorialReact DocsMERN Front to Back UdemyReact BasicsNextJS DocsNextJS Docs’ TutorialTailwind CSS TutorialSanity DocsContext API Tutorial

Summary of Learnings

Take a tutorial. Once you’ve learned a little, build your own project from what you learn.

Build until you feel a constraint, then learn more. Don’t learn just to learn.

Once you understand a language’s keywords, you’re set. Code until you’re stuck. Then Google keywords for whatever you need.

I’ve been stuck for 7 days on one problem multiple times. Ask people online. They will help.

You can do it.

Thank you for reading! I’m not going to lie. This took a while to put together.
If you’d like to say, “Thank you” please retweet the first tweet of the thread on Twitter.
That would be the most meaningful way to say, “Thanks”.
Yew, yew!
– Ryland

SEO with SSR vs. Prerendering – Pros/Cons of each?

Content writer here. I’m writing a blog post for a client about the SEO considerations of three JavaScript frameworks: Angular, Vue.js, and React.
I’ve been reading up on this topic all morning. It seems that Angular defaults to client-side rendering, which is bad for SEO, but you can configure it to use server-side rendering by using the Angular Universal library.
Or, you can use Prerendering tools (e.g. Prerender.io) to render the static HTML and deliver it to web crawlers for you. From what I understand, this is a nice alternative because it’s less resource-intensive than setting up your own server, which you need with Angular Universal.
Can someone with more webdev chops than I have tell me some of the other SEO pros/cons of each?
Thank you!

50+ Best Free PowerPoint Templates 2020

Not everyone can afford to buy premium PowerPoint templates to create their slideshows. But, that doesn’t mean you have to settle for a default template. There are dozens of incredible free PowerPoint templates to try out! A great thing about the design community is that there are designers out there who willingly share their amazing…

How to Make a WordPress Website

Do you want to know how to make a WordPress website? Good choice! WordPress is the most flexible and popular website platform out there. Creating a WordPress website is easier than you might think. You don’t have to spend lots of money, hire a developer, or learn to write code. In this complete WordPress for…

How To Help Your Clients Get More Backlinks Through Design

There are certain truths when it comes to what helps a website rank in search. Google wants to see: Mobile-first design Fast page speeds Top-notch security User-friendly navigation Trustworthiness and expertise … among other things. It also wants to see high-authority websites link back to your website. And if your clients aren’t obsessed with getting…

24 Best jQuery Image Sliders

Add a full-featured and easy-to-implement jQuery image slider to your website to help you keep the attention of your website traffic.  CodeCanyon offers some of the best jQuery image sliders available on the web for a one-time low payment. Slider Revolution is one of the best selling jQuery image sliders available on CodeCanyon. Images are…

Community Resources, Weekly Newsletter, And Boosting Skills Online

Improvement is a matter of steady, ongoing iteration. If you’ve been around for a good while, you’ll know that Smashing has been through a good number of changes in the past: a new design, a new layout, a new technical stack, and so much more. Still, it was always done with quality content in mind.…

A Smashing Guide To The World Of Search Engine Optimization

Search engine optimization is essential to most websites. The industry is worth more than $70 billion a year, and it’s only going to grow. It has specialists, sub-specialists, thought leaders, dedicated publications, fantastically complex tools, and constant uncertainty at its heart. As Bob Dylan says, it’s just a shadow we’re all chasing. All the more…

Smashing Podcast Episode 22 With Chris Coyier: What Is Serverless?

Today, we’re talking about Serverless architectures. What does that mean, and how does it differ from how we might build sites currently? I spoke to Chris Coyier to find out. Show Notes Chris’ microsite The Power of Serverless for Front-end Developers Chris on Twitter ShopTalk Show podcast Weekly Update “Setting Up Redux For Use In…