I'm Wes Bos, Ask Me Anything!

☺️
☺️☺️
☺️☺️☺️
☺️☺️☺️☺️
☺️☺️☺️☺️☺️
☺️☺️☺️☺️☺️☺️
☺️☺️☺️☺️☺️☺️☺️ Thanks!
☺️☺️☺️☺️☺️☺️
☺️☺️☺️☺️☺️
☺️☺️☺️☺️
☺️☺️☺️
☺️☺️
☺️

By far is how values get passed into functions.

const firstName = 'Wes';

function sayHello(name) {
  console.log(`Hello ${name}`);
}

sayHello(firstName);

Why is it name and not firstName?!

Seems to simple to anyone programming for a while, but it's often a cause for confusion in my students.

References (arrays, objects) VS values (strings, numbers) is another one.

Truthy/falsy was another one but I've got pretty good at explaining that :)

wesbos.com/uses/ :)

Just start! You'll figure it out along the way. Create small, focused tutorials on a variety of topics and you'll quickly figure out what ones do well and the ones people want more of.

Good luck - you should start today because I know tons of Spanish speakers take my courses and would probably rather something in their native language.

I didn't know what that was until just now - what a douche. It kills me to see people furthering stereotypes like this :(

What is #GoogleManifesto?

It's all about finishing things. I always loose steam on things right about 90% o the way through. That last 10% is the hardest, but well worth it.

Learning how to push through that has helped a lot. There are no secrets here - just having a bit to grit to double down and finish things.

When I've built at least 3-4 real world things in it. Most of the things I teach are lessons learned from me applying it in the field. I've been learning GraphQL for the 6 months or so, and just getting into a space where I feel comfortable enough with it that I'm starting to talk about it :)

It mostly boils down to:

1. Think of topics that need to be taught — like React or Node
2. Make a list of all the different areas of that topic that need to be learned - templating, data fetching, caching, image resizing, authentication, file uploads, realtime
3. Dream up an example application that is equal parts fun to build and real world enough that it would apply to your real work.
4. Research the crap out of the topic - even if it's something I've been doing for years I always research different possible ways of building the application, best practices, gotchas. I usually do this by reading all the docs of a project, reading blog posts from industry experts and watching conference talks on YouTube.
5. Build the thing we are going to build - I usually do this a few times and then refactor every line until I'm happy with it. I put a lot of effort into making the application easy to grok a few months later so you'll notice that I sometimes forgo dozens of small index.js files that can easily confuse and ruin a tutorial for you.
6. Once I'm happy with what we are going to build, I have a few industry experts code review it - make sure everything is up to snuff with best practices.
7. Then the hardest part is figuring out how to incrementally build the application in steps. Each video should be less than 20 minutes long, but we should also have something working by the end of it. Application development isn't always linear so this is something I've spent a lot of time on.
8. once it's all broken down into sections - I have rough notes on what needs to happen in each video and then I record!

It's a lot of work - this process takes 4-5 months.

My advice would be to not worry about process too much and just start creating things - you'll figure it out pretty quickly. What I do might not work for everyone :)

Yeah! Some ideas:

• Organize something small where you can help out and mentor a few students. Just meet at a coffee shop once a week and give them guidance.
• Help out on Slack/IRC/StackOverflow - this is how I got my start
• Look for someone who needs a mentor and just focus on them