5 ms·

I think it best to learn how to code by working on an actual project. You seem to already have a project in mind, and I think that would be a fine project. Bre

by tjr 15y ago

I think it best to learn how to code by working on an actual project. You seem to already have a project in mind, and I think that would be a fine project. Break it up into steps. First write a program that opens a file, reads the book titles and displays them on the terminal. Then write a program that makes some sort of network connection; maybe download the HTML contents of a website. Etc., etc., until you've learned how to do the various subtasks involved with your project, and then assemble it all together. I'd suggest that Python would be a good language to start with. I personally like the O'Reilly book Learning Python, though there are many options.

anthonyb 15y ago
From experience, I'd definitely second the 'actual project' part, particularly around breaking it down/picking the right level of project. Ideally you want something that you can pull off in a day or two, then apply what you've learned to the next project, or extend your first project so that it does more. plug: It's the tack that I took when writing Quick and Easy Python (http://manning.com/briggs/ http://manning.com/briggs/) - small bits, building on each other.
stevenp 15y ago
Agreed. I'm self-taught and have been working in the industry for 12 years now. The way I got started was that I had a project I needed to do, so I figured out what I needed to know to get it done. The same is true with my iPhone app -- I knew nothing about Objective-C when I started it, and it's 3 years old now. Learning for the sake of learning is fine, but learning how to build something you want to build and really seeing it come to life is a pretty phenomenal way to learn.
- conradev 15y ago
  I also agree. I tried reading a book on Objective-C, read the first two chapters, and ditched it for the iPhone SDK. I messed around, and tried making some ideas come to life. It took me a couple months, but eventually I was fluent in Objective-C.
troels 15y ago
FWIW, I think that is subjective. Some people learn better that way, but I don't think it's a universal truth. People are individuals when it comes to learning.

by tjr 15y ago

anthonyb 15y ago

From experience, I'd definitely second the 'actual project' part, particularly around breaking it down/picking the right level of project. Ideally you want something that you can pull off in a day or two, then apply what you've learned to the next project, or extend your first project so that it does more. plug: It's the tack that I took when writing Quick and Easy Python (http://manning.com/briggs/ http://manning.com/briggs/) - small bits, building on each other.

stevenp 15y ago

Agreed. I'm self-taught and have been working in the industry for 12 years now. The way I got started was that I had a project I needed to do, so I figured out what I needed to know to get it done. The same is true with my iPhone app -- I knew nothing about Objective-C when I started it, and it's 3 years old now. Learning for the sake of learning is fine, but learning how to build something you want to build and really seeing it come to life is a pretty phenomenal way to learn.

conradev 15y ago
I also agree. I tried reading a book on Objective-C, read the first two chapters, and ditched it for the iPhone SDK. I messed around, and tried making some ideas come to life. It took me a couple months, but eventually I was fluent in Objective-C.

troels 15y ago

FWIW, I think that is subjective. Some people learn better that way, but I don't think it's a universal truth. People are individuals when it comes to learning.