3 ms·

It sounds like you may not be "dumb", but maybe just a beginner who is struggling to get to the next level. Here are a few questions I'd ask first before you d

It sounds like you may not be "dumb", but maybe just a beginner who is struggling to get to the next level. Here are a few questions I'd ask first before you decide programming is not for you. 1. Do you work with other experienced and passionate programmers who can mentor you?(http://chadfowler.com/2011/02/24/be-careful-of-who-you-work-with http://chadfowler.com/2011/02/24/be-careful-of-who-you-work-...) 2. Do you know how to learn? A lot of people assume it just comes down to reading the material, I found this book explains the process quite well and it is put in the context of a software developer looking to attain mastery http://www.pragprog.com/titles/ahptl/pragmatic-thinking-and-learning http://www.pragprog.com/titles/ahptl/pragmatic-thinking-and-... 3. Have you "cultivated your gurus" so to speak? Putting up a post on HN is a great start, but continually involving yourself in discussions in the greater community will help you to tap into a source of experienced mentors even if you don't work with them. Find groups for topics you are interested in and then involve yourself, ask questions, learn, then contribute to the discussion yourself. 4. Have you considered getting involved in some open source projects? These are a great place to learn from others as well. In the end learning isn't generally as simple as just reading a few books for most people. I would consider starting with a few books on how to get your career development and your learning process on the right track and then go from there. Even if you do decide you're not cut out for programming, what you learn from those books will be valuable no matter what path you choose. The books I'd recommend: http://www.pragprog.com/titles/ahptl/pragmatic-thinking-and-learning http://www.pragprog.com/titles/ahptl/pragmatic-thinking-and-... http://www.pragprog.com/titles/tpp/the-pragmatic-programmer http://www.pragprog.com/titles/tpp/the-pragmatic-programmer http://www.pragprog.com/titles/cfcar2/the-passionate-programmer http://www.pragprog.com/titles/cfcar2/the-passionate-program... (will admit to not reading this one but I hear very good things) Yes I realize these are all PragPro books, what can I say, they are that good.

jrookie 16y ago
Thanks for you answer, you tackle some of the other things I've been struggling with for the last few years. 1. I work with other experience programmers but they are not really into "mentoring", I have been looking for someone online who can lead me on the path of the hacker. 2.Good point, sometimes I do feel like I don't know how to learn. Thanks for the link I will check it out. 3.This is one of my flaws...I'm not very confident in my abilities, and frankly I never feel like I have something good enough to contribute, this is also why I've never felt comfortable starting a blog or participating in open source projects.
- JonnieCache 16y ago
  >This is one of my flaws...I'm not very confident in my abilities Realise that lack of confidence is just another way of saying "knows his limitations." This is an asset that most people at your level don't have. If you want to learn some CS, here's a concept for you: Fail Fast https://secure.wikimedia.org/wikipedia/en/wiki/Fail_Fast https://secure.wikimedia.org/wikipedia/en/wiki/Fail_Fast This concept, like many CS concepts is often generalised by hackers to life in general. Practice makes perfect. What does practice mean? Doing things badly over and over again until you get better. Viewed in this light, failure is an asset. As long as you learn from it, you can see each failure as another step on the road to success. As I say, hackers generally take this attitude that failure is good. Strolling into an IRC channel or message board for a particular technology and professing your utter ignorance and incompetence concerning the matter will likely not be met with the derision you might fear. Most people are more eager to help the humble than the bullish. EDIT: Also read this book before you read any actual programming books. Don't worry when you don't understand parts of it. http://en.wikipedia.org/wiki/G%C3%B6del,_Escher,_Bach http://en.wikipedia.org/wiki/G%C3%B6del,_Escher,_Bach
  - jrookie 16y ago
    Thanks, I tried reading that Godel book and I couldn't wrap my head around it, I will give it a second shot though.
    - JonnieCache 16y ago
      I think the best thing to do when you get to the really dense sections is just to plough through. It reaches a critical mass of crazy notation and mindbending logic in the middle, but once you get past that it drops back to being relatively graspable again as he addresses different areas. At least for a while :) As I said, don't expect yourself to really understand all of it the first time you read it. Read it for the bits you do understand, not the bits you don't. Even if that turns out to only include the Carrol-esque dialogue, it's worth it.
- chernevik 16y ago

jrookie 16y ago

Thanks for you answer, you tackle some of the other things I've been struggling with for the last few years. 1. I work with other experience programmers but they are not really into "mentoring", I have been looking for someone online who can lead me on the path of the hacker. 2.Good point, sometimes I do feel like I don't know how to learn. Thanks for the link I will check it out. 3.This is one of my flaws...I'm not very confident in my abilities, and frankly I never feel like I have something good enough to contribute, this is also why I've never felt comfortable starting a blog or participating in open source projects.

JonnieCache 16y ago
>This is one of my flaws...I'm not very confident in my abilities Realise that lack of confidence is just another way of saying "knows his limitations." This is an asset that most people at your level don't have. If you want to learn some CS, here's a concept for you: Fail Fast https://secure.wikimedia.org/wikipedia/en/wiki/Fail_Fast https://secure.wikimedia.org/wikipedia/en/wiki/Fail_Fast This concept, like many CS concepts is often generalised by hackers to life in general. Practice makes perfect. What does practice mean? Doing things badly over and over again until you get better. Viewed in this light, failure is an asset. As long as you learn from it, you can see each failure as another step on the road to success. As I say, hackers generally take this attitude that failure is good. Strolling into an IRC channel or message board for a particular technology and professing your utter ignorance and incompetence concerning the matter will likely not be met with the derision you might fear. Most people are more eager to help the humble than the bullish. EDIT: Also read this book before you read any actual programming books. Don't worry when you don't understand parts of it. http://en.wikipedia.org/wiki/G%C3%B6del,_Escher,_Bach http://en.wikipedia.org/wiki/G%C3%B6del,_Escher,_Bach
- jrookie 16y ago
  Thanks, I tried reading that Godel book and I couldn't wrap my head around it, I will give it a second shot though.
  - JonnieCache 16y ago
    I think the best thing to do when you get to the really dense sections is just to plough through. It reaches a critical mass of crazy notation and mindbending logic in the middle, but once you get past that it drops back to being relatively graspable again as he addresses different areas. At least for a while :) As I said, don't expect yourself to really understand all of it the first time you read it. Read it for the bits you do understand, not the bits you don't. Even if that turns out to only include the Carrol-esque dialogue, it's worth it.
chernevik 16y ago