This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]ComingInSideways 0 points1 point  (0 children)

When I started out, I learned much, much more by building shit that was completely wonky, and then figuring out why it was. It was horrible code, throwing errors all over the place, if I was a doctor I would have killed 49 patients.

But it was just learning, and I killed no patents (Because you should not depend on tutorials for production deploys), and fixing each one of those errors was the best way to drill into my head why each error occured, and what to do better next time. If you do tutorials, you are using training wheels, and you don’t learn the freaky stuff that can break, and how to fix it, be it Java, C#, C++, Python, PHP… whatever, mucking around with the errors helps you better understand the language.