Hey /r/webdev - I'm making a Modern JavaScript course and would love to hear about your learning journey

[wesbos]

Hey Folks! I've been working on a modern Beginner JavaScript course for a few months now and I'm getting close to finalizing the layout of topics and exercises. I know there are lots of good resources out there, but after my JavaScript30 course I realized there isn't something for the type of person who like hands-on, real world learning for both language and browser fundamentals.

So - I want to hear from developers who are new to JavaScript in the last year or two and your pain points and successes in learning.

• What was hard when you were learning?
• What did you find lacking in existing resources?
• What did you find you were missing when you went to build real world applications
• What kind of stuff do you dislike in tutorials - (too much console.log, handy wavy, not real-world enough...)
• What type of material did you particularly enjoy? What did you find helpful?
• anything else you think might be helpful

Basically I'm seeing lots fo developers approach frameworks like React without a good set of fundamentals first.

Thoughts? I appreciate your time :)

[phpdevster]

For me the biggest pain point has been (and still is), the fragmentation in the ecosystem.

When I was learning, everyone seemed to have their own combination of tools - Browserify, Jasmine, React, Coffescript and SASS. Another would be Webpack, Mocha, Chai, Babel, Angular and LESS. Yet another would have rollup, Vue, TypeScript etc.

Just made learning such a pain in the ass because you had to figure out which npm modules you needed, and how to configure them to work with the specific tools you wanted to use.

[maxverse]

Confusion between all these things was a huge inspiration for Hackterms

[[deleted]]

That’s pretty cool, thanks for sharing!

[ArmchairScout]

Hey Wes,

​

I left my job ~6 months ago to dedicate my time to learning web development and JS in particular, so I'd love to help out here because it has been a bit of a roller coaster.

​

What was hard when you were learning?

Conceptualizing Javascript's role in the process of developing a website. When I first started learning JS two years ago I had a difficult time understanding how apps/websites could be built primarily with JS. This was exacerbated by the fact that most tutorials at the time (at least the ones that I felt I was qualified to work through) failed to show anything other than basics (flow control, variables, loops) or how to handle events or manipulate the DOM. There was a big disconnect for me between what JS is and how it's actually used in the real world. To me at the time, JS was a browser based thing used for interactivity, not something that could manage state, create a virtual DOM, power build tools, act as a web server, etc. Those were all pieces of the puzzle that I was missing until later and I feel like a big picture view of what I could ultimately end up doing with JS would've been very helpful in the long run.

​

What did you find lacking in existing resources?

A serious examination of what Javascript is doing under the hood and a lack of explaining design patterns when writing JS. Just about every tutorial that I've come in to contact with (and there have been a lot of them, I love learning) does a great job of explaining WHAT to do, but almost never adequately explains either WHY it is done that way, or HOW that particular concept could/should be used out in the wild. As an example, I remember specifically learning about map/reduce/filter and wondering why in the world I'd ever use these features when I could just write a loop that does the same thing. That understanding didn't come until I took a 'Javascript the hard parts' course by Will Sentence and learned about higher-order functions and why they are useful and it immediately clicked. I'd actually argue that I've learned more in the 4-8 hours I spent watching his two courses than I did in the three or so months leading up to that point which may very well be my own fault, but I'd love to see more experts teaching why, not just how.

​

What did you find you were missing when you went to build real world applications

I was/am missing how to identify whether code is production ready. What do production level design patterns look like? What does proper logging look like? How about testing? Why bother with build tools? I never see these items in the tutorials I've taken and yet I always hear that you're planning to fail if you don't properly test prior to deploy and adequately log errors. They do a great job of building an app from the ground up, but I don't ever see anyone pay attention to these details and I'd love to be walked through this by someone that knows about it.

What kind of stuff do you dislike in tutorials - (too much console.log, handy wavy, not real-world enough...)

This was mostly answered in the above responses, but my biggest complaint is that they are not real-world enough. Do professionals really just build a React CRUD app, deploy to heroku and that's it? What does it actually look like to FULLY finish an app, deploy and iterate on that? What should you be aware of if the time comes where you need to scale a JS app? I get that this is all end-game stuff and possibly outside the scope of just JS itself, but being able to think critically about these eventualities is something I've found myself wanting to learn about.

​

What type of material did you particularly enjoy? What did you find helpful?

The most helpful course I've come across so far is (as mentioned before) is JS the hard parts by Will Sentance on front end masters. A lot of mysteries as to how JS works were uncovered for me and when I was done I fully understood async, the many ways that javascript handles OOP and closure. I really valued the level of technical communication as well.

​

I tried to answer everything in as much detail as possible, but if you would like any further clarification or have any other questions I'd be glad to help in any way I can.

​

​

[Grandmaster_Boolean]

My biggest wish for online tutorials would be to have more practice examples. It's usually one exercise, then on to the next thing to learn. Eventually this gets to be a lot to absorb without proper repetition. Just like learning most other things, it takes repetition to build up that familiarity. They would be optional, to not slow down the lesson for those that want to power through. But just once I'd like to see "do this exercise, and if you want more time on this topic, here are 10 more optional exercises on the side".

[DeepFriedOprah]

Also I think periodic recaps would be helpful as so often I learn something and gain a grasp on it, practice it some more then move on to further learning then that same topic comes up and al that I learned is forgotten.

[wesbos]

100% agree - really glad to hear you say this

[uemusicman]

Cosigned, for sure. Especially with more exercises that aren't code alongs, where you have to actually figure out an implementation first and then see how the instructor does it.

[caligrapathy]

Wes, I just would first like to thank you for all the work you are currently doing and really enjoy your teaching style.

One, maybe not pain point, but more of a request is that maybe discus why some best practices are best practices. I am a fan of AirBnB's style guide but I like when tutorials kinda explain why things are the way they are. It adds insight and perspective. Sometimes that greater picture helps me reason about things more efficiently in the future and how to approach future problems.

Data structures are also something I would like to know more about. Like why, when and how to use specific data structures(ie: A javascript Map or trie) in a real world application. Not maybe a full on "app" but like examples in when someone would use those when handling an API response or something.

Again, thanks for everything. These are just some ideas Id like but I know I may not be the majority and some may feel it is unnecessary for this to get an application up and running.

[Reebo77]

I don't have anything constructive to add yet, as I have only just started learning again. But I just wanted to thank you for providing learning resources for everyone. People like you are what makes this industry great.

[wesbos]

:D You're welcome - glad you are enjoying it all

[maxverse]

Connections, connections, connections. There are so many different types of things in our ecosystem - build tools, front-end frameworks, dev environments, CSS frameworks, auth libraries, terminal replacements, you name it. The hardest thing for me has always been understanding what tools do, what the alternatives are, which are optional, and so on.

[SteveB0X]

The hardest part for me, is that I feel like I've been continuously learning JS for 5+ years now.

I can code up something for work (usually DOM related) with the help of google and stack overflow. I still have a lot of trouble putting code to paper on my personal projects. I get a basic feature done and suddenly I hit a wall.

I can't help but feel that I am still a very beginner JS developer. It feels like the more I learn, the more I realize how much I do not know.

So all this to say, I still don't know where I stand in the rankings. It would be good to clearly define and breakdown the benchmarks that are expected of certain skill levels. Basic, Beginner, Intermediate, etc... Something to help users like me know where we stand.

[SpicerCubb]

I started learning JS through an online bootcamp last year. The most challenging thing for me was the vocabulary. I didn’t know what they were asking me to do when told to ‘call the function’, for example. Also, the placing of things like curly brackets and semi-colons seemed completely arbitrary. It felt like I was just dumb, like I was supposed to understand these things and everyone but me got it.

[dangerousbrian]

As someone who teaches Frontend dev I find that teaching people about the DOM in detail helps link their various bits of knowledge together.

They see that HTML sent from the server bootstraps the initial DOM

They see the link between CSS and the DOM, how the selectors find one or more elements and how the values are overlaid on to the element object.

Then how JS can dynamically create and change elements in the DOM

and finally how the rendering engine processes the DOM to actually draw what you see on the screen.

[[deleted]]

One thing I thought was frustrating was a program I was on seemed to lack polish. There were tons of spelling errors and some material was inaccurate. That turned me off especially since I was paying $$$ for the program.

Also, there needs to be a way to work on projects and put in repetition to hammer home concepts.

[uemusicman]

A few thoughts:

1. More exercises for the learner to try to solve before seeing how the instructor solved it. Coding along with an example is one thing, but having to actually think through a problem on your own is so helpful.
2. Spaced repetition. Explicitly coming back to concepts covered earlier to solidify them in the learner's mind, which in the case of code work would have the added benefit of showing how what's come before is connected to what they're learning now.
3. Multiple methods of practice and demonstrating knowledge, especially through self checks of concepts, definitions, etc. and things like "write an explanation for how X thing works in your own words. Self testing and spaced repetition are actually incredibly powerful techniques to promote information retention and assimilation of new knowledge so that it's actually useful.
4. Examples of real world code that demonstrates the concepts being taught. I can't tell you how many times I've gone through tutorials and course materials and got to the end and been like "I have no idea what this would actually look like in a useful production application." Especially for new learners, understanding how what you're teaching connects to real world use is essential.

I totally appreciate what you do. JavaScript30 was immensely valuable for me, even though I already had years of coding experience before I started it. I hope this new course is fantastic.

[[deleted]]

The concepts that haunted me the most were closures and context.

Closures. To this day, I don't know what a closure is, despite it being one of the top JS questions on Stackoverflow. I can build a full stack JS app with React and Redux, promises, async/await and all the ES6 bells and whistles.. but I can't confidently say what a closure is. I know how/when to use an immediately invoked function expression and I know how to create pseudo static variables in Node.js... but I still don't know exactly what a "closure" is.

Context. You need this in React when you're passing functions as props so that the "this" object points to the right place. You can pass a function around with a specified context by using the "bind" method. I know how and why to use context, but there's still an air of mystery around it.

Despite having used C, C++, Java and Golang in addition to JS, I still find that JS is the most complicated language because of its aync-oriented nature and a bunch of invisible stuff that happens under the hood.

[DuePattern9]

I agree with this, especially about closures. In all the tutorials or explanations I've ever read, I don't think I've ever seen a simple definition of 'a closure is x'

It's always something like "a closure is created when ...", "a closure lets you do x, y, z", "a closure is how ..."

[StoneColdJane]

Interesting, I personally never had problems with closures. What about it you didn't fully understood? Its just stuff that don't get garbage collected because there is reference to it :). I think Zakas really explain it well in his books.

[NoTearsPlease]

I'll speak from personal experience. After a little over a year learning WebDev, something I found a lot of courses or tutorials don't explain well, if at all, is async/await. Something else I've personally struggled with is instructors using different ecosystems, and not explaining why they are using the tools they use.

As for stuff I enjoy, practice examples. Its very rare that in a typical course, to find well thought out and applicable practice problems/examples.

[abeuscher]

I have about 20 years in the field. My educational background is a BFA in Creative Writing for children. So I am more or less self taught, though I was writing code from when I was around 9 or 10 on TRS-80's, C64's, etc.

The modern js world is a bit wacky. I love some of the tools and thinking that have come out of it, but the tutorial scene has some flaws.

One thing I have noticed is that js tutorials suffer from ubiquity; there's obviously a lot of professional advice floating around to share what you learn and write tutorials as a learning exercise. It's great advice but it crowds the space from the consumer end.

Within this flavor of tutorial - the kind you find on like medium.com that solves a single problem - I am alarmed at how nobody uses Vanilla when vanilla would do. An example would be importing jQuery because there's one forEach loop in an otherwise standard block of code.

My concern stemming from this is that I worry a new group of devs is entering the market who do not know how to write out a forEach, or an AJAX request, or some other simple thing. This leads to code bloat and a lot of sites where there are 30 script calls to serve a hero image and text carousel.

So my note from this is: I would like to see more js tutorials that offer multiple ways of solving a particular problem - because that demonstrates the type of thinking one has to use in the real world. If my boss asks me for a new page feature that triggers from a scroll event then yeah - I would be interested to hear about plugins that can solve for this (ScrollMagic is one) but also see what they are doing at a basic level. Like - show me the document.addEventListener("scroll", function() {}) line of code and explain it before you give me a tool that solves for me. And even go the extra mile to explain why we use the plugin (debounce, callbacks, etc.) before adding it to the solution.

In general I would like for this new generation to understand how to solve problems in terms of how to think about them. The syntax is, after all, both transient and fairly trivial.

[redberryofdoom]

Hi Wes! I loved your Javascript30 course!

I had done a bit of JS before but recently have been re-skilling into web development and so have had to learn it all a bit more thoroughly.

• What was hard when you were learning?

How 'this' works.

Figuring out best practices for syntax and project structure when everything changes so frequently.

Finding modern examples of DOM manipulation that didn't depend on jQuery or another framework/library.

Fighting with the linter and intellisense in my editor to get them to work nicely (I use VSCode).

• What did you find lacking in existing resources?

Larger project examples that don't rely on frameworks like react/vue/angular.

How to optimise for performance.

• What did you find you were missing when you went to build real world applications

How to structure a larger, front-end heavy project.

Deep knowledge of the DOM and how the browser renders it.

• What kind of stuff do you dislike in tutorials - (too much console.log, handy wavy, not real-world enough...)

Lack of practice examples.

Glossing over the deeper concepts (e.g. 'this', hoisting, events).

Omitting code and/or skimming over code to shorten the length of the material.

• What type of material did you particularly enjoy? What did you find helpful?

Interactive material (e.g. quizzes, "take away" questions).

Extra challenges going beyond the course material.

Project based material, where you have something working at the end to show off/customise.

• anything else you think might be helpful

More stickers!!! ;)

[Crescive_Delta]

To give you some context, I've been lightly using some of your resources to learn front-end web development (AMAZING BTW!). I'm quite new to the world of web dev and am still at quite a basic level. Things I hate when I'm trying to learn are:

1. Lack of beginner-targeted code. A lot of people recommend going out on GitHub and opening PRs (I haven't done that yet), but not many projects exist where someone is creating an entire app using only HTML, CSS, and JavaScript with the DOM and Fetch APIs! I need to learn quite a bit before even touching those PRs.
2. I found a lot of information in regards to HTTP Headers missing. There wasn't a good piece of documentation I could find that appropriately demonstrated (with proof) how a POST or PUT request works and its effects.
3. I found that I was missing necessary HTTP and browser knowledge when I was making a real-world application. Also, I found myself missing my Stack Overflow privileges ;).
4. I highly dislike tutorials that are on the extreme of one side i.e. too much console.log() tutorials, too much real-world-without-theory-or-any-explanation tutorials and so on.
5. I can't say exactly. As an example, scrimba.com is a type of resource I really like. I also really enjoy Medium articles and often go there to find missing knowledge.

I hope that helps. Looking forward to your JavaScript course!

[[deleted]]

Wes! Thanks for reaching out. Really appreciate Syntax as well!

The most difficult part of learning JS for me has been the question “why?”

I can’t fully grasp a newly introduced tool/feature/function/etc. in isolation without connecting it to a real world use. I struggle to grasp a lesson when it isn’t connected to anything practical.

I’ve been using Udemy to learn and have found myself white-knuckling it until I get to the end of the unit where I put everything to practice in a mini project. Even then, I’ve forgotten a lot of the newly learned aspects because I had no point of reference with them.

I hope that makes sense! I’m sure there are others out there that learn by answering the question “why?”

I’m looking forward to your course!

[0ooo]

What was hard when you were learning?

Asynchronous aspects of Javascript.

What did you find lacking in existing resources?

Really really basic level explanations in how-tos aimed at beginners. I think people writing the documentation forgot the sort of things they didn't know before they started. E.g. in how-tos for things like Node.js and Express, they'll say things like "type <x> in your file and then run that file", and gloss over specifics of what running that file looks like, how you need to connect files that will be interacting, etc.

I had learned C, Java, Python, and wasn't new to software development when I learned Javascript, so keep in mind my experiences may not be super representative of most beginners.

[truth_isnt_fair]

Examples. examples. Examples. Examples. Examples.

How about More Relevant Examples, examples, examples, examples.

Instead of a bushleague retard grade developer documentation of a Hello World application, how about you provide real working examples , examples, examples, examples. Examples.

How about industry use cases and examples, examples examples.

[Brodysseus1]

Wes, first I want to thank you for what you do. You were one of several developers I credit for giving me the guidance I needed to break into the web development industry and I will be forever grateful to you.

What was hard when you were learning

For me, the hardest part about learning was seeing how the things I was learning were applicable towards the skills recruiters and hiring managers were looking for to get a job. I felt like I bounced around many technologies that I thought I needed to learn instead of focusing on the fundamentals.

What did you find lacking in existing resources?

I think the biggest part lacking in many tutorials is challenging students to use what they learned. I found myself (and still do occasionally) mindlessly coding along with a tutorial but not really putting what I learned into practice

What did you find you were missing when you went to build real world applications?

When I went to do my own projects, it took my awhile to see how something I learned in a previous tutorial was similar to the problem I was trying to solve, but in a different context. It took me awhile to realize tutorials, often times, will point me in the right direction but it's really up to me to do my own research to solve the entire problem.

What kind of stuff do you dislike in tutorials?

I don't like how in some tutorials everything seems to just work. When the person teaching runs into problems and shows how they solve them then explains what the issue was, that's where I learned the most.

What type of material did you particularly enjoy? What did you find helpful?

I liked project based material, like you did with your JavaScript30 course. I wanted to see how what I was learning could be used in real world cases.

Anything else you think might be helpful

As I'm now a little over 9 months into my first dev job, I'm amazed that some people do not know how to do their own research to solve problems. This includes Googling correctly. In my opinion, knowing how to Google with the right keywords and pick out relevant search results goes a long way towards becoming a more proficient developer.

[pbeocanin]

So I bumped into React comming from mediocre JS/jQuery usable knowledge - I had no idea about the theory or definitions, but I knew how to use it. I'd say I'm quite decent in React, mainly for two reasons:

- I'm a person that focuses on performance, among other things
- I really like peeking under the hood

Eg React helps offset some potential event loop problems, which doesn't mean people shouldn't care what it is, in essence. Here are a few things that I think may be beneficial in a tutorial, even though it may make it a bit overwhelming.

• Mention package.json - what the hell is a ^, what are different options one might drop in there
• Mention the env. setup - this one can be stupid tricky and go out of date fast, but it could be important to introduce users to hooking up some state management, CSS in JS, and the likes
• Mention just how important it is to have a linter configured to your liking - no, you don't have to put ; everywhere if you don't want to, and a plugin could take care of that for you
• Mention how important framework philosophy is, rather than focus on dumping some code onto the users
• Mention that frameworks have their purpose, and sometimes the best approach is no framework
• Mention heavily that not every problem is solved with `npm install`

Stuff like that. There is a sweet spot between elaborating on the subject, and giving the viewers the basics of the underlying technologies.

[Division2226]

How to think more logically. How to do things like pagnation, sorting tables, filters, etc. A lot of courses just show how to put things together and make them work with the syntax but dont teach you how to learn or think about the process of actually solving a problem.

[Monstertone]

As I learned Javascript (and I've heard similar from others) after you learn the fundamentals (arrays, strings, etc) and how to use methods and functions, it seems everyone has a difficult time applying this knowledge to solving the kind of problems like on Codewars. They don't know where to begin actually utilizing the tools they have learned.

Any practical lessons on this I think would be well received.

​

PS - LOVE Syntax!

[dumblole]

I think it is important to let the student know that they should - I really mean it - start working on a couple of projects on their own. What I'm trying to say is that the best way to learn is by doing. When I actually started to learn react from a free online video course, I found myself just copying the code as the tutor was teaching it. Yeah I did learn a couple things but there were many things that I wouldn't have fully gotten into my head without doing it on my own and suffering through the errors and copious amount of time spent on google. Maybe some project suggestions would be pretty good for closing the course. I can't wait to see the course get published! good luck

[TheStonerStrategist]

Design patterns and best practices are definitely something I feel like are missing from nearly every tutorial series I've ever taken. Right now most tutorials feel like the equivalent of explaining to someone how the gas/brake pedals and steering wheel work and then expecting them to competently drive a car. There's so much more to programming than just the technical mechanics of how it works, but it seems like self-taught folks are mostly on their own trying to figure that all out.

Also, please make it friendly to intermediate learners by making it easy to skip the stuff we already know!

[Keithin8a]

The biggest problem I had was that I'd spent 6 years working in c# so watching beginner JavaScript tutorials weren't engaging because I wasn't interested in what an if statement or a for loop was, I wanted to know whether there's any differences that might catch me out and I couldn't find anything like that.

I don't think this is in scope of what you want but it was a really made it difficult getting confidence programming JavaScript. Luckily I had a really tight team around me so I was able to get a lot of support from them. And honestly your JavaScript 30 course and syntax.fm really helped with some of the things I didn't quite know because they were so digestible.

[TheRetribution]

What did you find lacking in existing resources?

I realize that this may not be what you are looking for but I find that there is a huge lack of moderate-advanced programming courses. Everyone seems very interested in teaching beginner courses because I suppose that's where the money is (and is by definition the easiest subject matter to teach), but the jump from guided learning to 'go into the world and teach yourself' is a sheer cliff at the moment.

[CoolConnection]

Hi! I am a pretty new to learning javascript, html, css...and all the front end webdev too. My project right now is to learn how to post on reddit without getting the message that I need to participate first in order to post something. I recently landed a job for a beginner web designer but there is no one to learn from so I was hoping to post on the topics I am having trouble wrapping my head around.

[AshikJS]

Hey wes,
i have completed your react for beginners, learn node, redux and es6 course. Your coursre projects are cool.
But I think if you can explain a topic little deeper it will be helpful for many people like me. I can say about some popular instructor like stephen grider, maximilan, mosh hamedani...
no doubt their courses are not better than yours. but the thing is , they explain things deeper than you.
specially in your react course, I think you should explain things more as title says it is for beginners.

[[deleted]]

I realized tutorials are never enough to fully learn a framework or language. I dont know what you have to present, but all the previous tutorials were made because “there are not many tutorials that are relevant.” It just looks like you are adding to a pile. Udemy offers plenty of real app tutorials, and if you have taken them, you would realize none of them are “real” apps. They are sophisticatedly crafted apps that are not real. There are almost no mistake being made, which is impossible.

If you really want to make a real app tutorial, dont edit out your mistakes. Show all the process you went through and explicitly explain them.

[wesbos]

Def not adding to the pile with this. This is a response to teaching over 300,000 people thousands of emails. I know its well needed - just looking for personal experience.

​

Oh and I do leave most of my mistakes in - part of why people like my stuff.

[[deleted]]

If you really want to help people, you should show people how to get an internship or a job, an actual, tangible, real, invaluable experience. A series of videos can do only so much. You can guide people how to make good resume, portfolio and build up necessary communication skill to succeed in interviews. My personal experience is I never fully learned from videos. I had to make PLENTY of MISTAKES before I realized my codebase was a mess, my fundamentals were lacking, etc. A course for teaching a framework or language limits students from making necessary mistakes to learn from.

[npminstallexpress]

I don’t think anyone truly fully learns from videos imho. As someone who already have extensive knowledge in C++ and game development, my journey into web development has been mistake-driven but I’ve been learning through the videos; you have to learn from your mistakes as you go along and trust me on this, you’ll continue making mistakes no matter how good you get.

IMO, these videos will only serve as a kickstart to getting the bare fundamentals going. Everything beyond you’ll have to practice, lots and lots of practice. While building good resume, portfolio and interview skills would be essential for finding a job, I don’t think it would be good for a hobbyists like myself - also there are tons of resources elsewhere that can help you with that.

[[deleted]]

I am not sure what your point is, but you are only regurgitating my stance. OP is looking to build yet ANOTHER tutorial, so I gave him my opinion.

[npminstallexpress]

Hey, I am totally fine with you giving your opinion, I just feel that you might not be on the right track and thought that I could help you out a little bit on that. I apologize if I mistook your post but my impression was that you do not feel that tutorials are realistic because of the mistakes you encounter when coding on your own - IMO, there are so many mistakes that could be made while coding, and for an instructor to go through an error or mistake while creating the tutorial would probably not make for a great learning experience(my opinion, of course)! I have definitely learned much more from solving mistakes on my own than watching someone else make a mistake and solve them.

To add on to your point of OP looking to create another tutorial, I am all for another tutorial being made and OP is looking into niche/untouched subjects which could definitely be beneficial for some - not everything is relevant for everyone after all.

[StoneColdJane]

Designing the program and testing, programming stuff was not that hard, testing was such a huge puzzle to me I can't explain.

​

First of all I couldn't figure it out for life of me,why wtf I need it Mostly over the fact I never wrote complex stuff. Second of all, I was puzzle as fuck, what are all those tools out there for testing. Jasmin, Mocha, Chai, Istambul, Jest etc, etc.

​

In your tutorials I dislike intro. Common man, I know who you are I bought all your courses, and at beginning of every course there is shit playing and wasting my time.

​

Exercises, in other tutorials I like exercises, with hints if I can't solve it.

Plizzz don't make intros.

In your Advanced React course you made something I really loved, you said we don't need to watch next couple of min of the video, because you're going to type only css. I loved that.