Quote (J_B @ Jul 24 2012 12:13am)
you don't get to learn building projects that interest you
you need to understand some basics before you try harder stuff or it will get messy and you'll develop bad habits or just miss out on concepts entirely
I'll have to disagree as well. I learned by having a die-hard passion for it, and the patience to learn it. I thought of things I would like to try, and I did them. Sometimes it took days, some took a few weeks... But I always completed them, and later went back for optimization as I learned more.
I have never taken a class, and yet on Friday I will be rolling out some software I began construction back on July 9th to my entire department and being compensated several hundred dollars in addition to my base salary in the process.
I learned how to do it, by loving to do it. Loving the process of debugging, loving the cigarettes smoked trying to decide the best programmatic approach to a theory, and especially loving the moment when your finished with a complete product...
There doesn't have to be a cookie-cutter path, just make your own.
Quote (PumblesMumbles @ Jul 24 2012 06:16pm)
Dead wrong imo.
Start out by tinkering around on small things on your own. Find something that's like what you want, copy it, and tweak it until it does what you really want. As you make small changes, you'll be able to start learning from a smaller point. As you work on more and more parts of the project, your understanding will grow. Keep it up and you'll eventually be a master on the whole system.
I completely disagree with this as well. Make it yourself. If its too complex? Make a simpler version. My first programs were literally the traditional "Hello World"... followed by InputBox fun... all the more growing as I went until the point I'm at now where trying to think of things to create is the hard part... not creating them.