I must be stupid

Hi Crafty!

Dealing with errors (bugs, broken code, etc.) is the main job of a developer. Let me tell you how I spent my first month working as a software developer: I picked 5 problems to solve from a list shared by the rest of the team. The first problem took me a week and a half to solve, the second one took a week, the last 3 took a week and a half among them. So, I would say to you, try to feel comfortable when dealing with errors (setbacks, mistakes, bugs, etc.), because that is going to be your life as a developer. Developers get paid for solving problems.

When you are doing a tutorial, you should address 30% to 40% of your time in doing the tutorial, and the rest of the time in building your own version of it. When you start building something by yourself is when you will face the concepts you don't yet master.

How I will approach this tailwind tutorial that seems to be difficult is:
1) Start by coding along with it.
2) After the first error happens, stop, analyse what is happening, and read all the error messages.
3) Try googling for the error messages or undesired behaviour.
4) If no solution is found, restart the tutorial from the point in which it was working (here is where using Git is helpful).
5) As a last resource, as for help. The idea is that you build confidence in yourself about finding solutions to problems.

Remember: you will get paid for solving problems. As a personal rule, If I spend less than a week trying to solve a problem, I'm not trying enough.