Great tip, I totally agree with you. In fact, the problem is that tutorials always work. They are meant to work out of the box. This means that by following them, you only experience the good stuff of a technology.
Real life is different though. To become really good at something (whatever that is), you have to build something. This is the only way to get errors, problems and bugs that, when solved, really teach you something.
I mean, everyone is good at following tutorials that work. The game-changer is always to learn how to solve stuff that doesn't work.
Great tip, I totally agree with you. In fact, the problem is that tutorials always work. They are meant to work out of the box. This means that by following them, you only experience the good stuff of a technology.
Real life is different though. To become really good at something (whatever that is), you have to build something. This is the only way to get errors, problems and bugs that, when solved, really teach you something.
I mean, everyone is good at following tutorials that work. The game-changer is always to learn how to solve stuff that doesn't work.
That's a great way to word it, tutorials always work!
Building things, has made a huge difference in how I write and understand code.
Solving stuff that doesn't work, I think that might be a good definition of what exactly a developer does!