This was great to read - I'm the same age as you and changed majors away from CS about 10 years ago because of similar reasons to what you described. Being young and not knowing much about the world meant that I didn't have any passion for what I was building, and after getting some real life experiences under my belt, I've come back to learn programming again because, well, I just can't help myself. I've thought abo…
When and Why to Learn to Program
11–20 of 22 posts
Re: When and Why to Learn to Program
#12The rivers of nonsense questions coming into stackoverflow from well meaning people who are not able to describe the difference between a variable and a browser and who don't have the capabilities to care unless it solves their immediate problem at hand leads me to believe that not everyone should program. in fact, many people who do program should be politely asked not to. Stackoverflow needs a "entrence barrier" te…
As for the stats, is it really that suprising that newcomers ask more questions? I'd imagine those who have been programming for some time are more confident in their ability to research answers, check the usual resources (e.g. MDSN), read and understand open source code, and then use SO as a form of last resort.
Re: When and Why to Learn to Program
#13Aside from that, stuff like:
"Here's why I finally learned to code: I've been a web entrepreneur since I was eleven years old — for over sixteen years now..."
Makes me discount just about everything that was written. I just have a bitter taste left over from this massive ego leak.
Re: When and Why to Learn to Program
#14- Focus. Don't do it on the side, it would take too long. Treat learning to code as if it was your regular job(I tried to do 40-60hrs per week, I did about 2000hrs of coding in my first year)
- Don't hurry. Don't obsess about efficiency and how you use your time. You will waste tons of time on stupid bugs and knowledge you don't really need, that's just part of the learning process. Focus on putting in those hours week after week and you will see results.
- Work on a project. The only way to truely understand how things work is to actually use them. Don't hide yourself behind books, try to apply everything you learn asap.
- Give yourself permission to suck. This is really hard if you're older (I was 30 when I started to code). If you already have a career, you're not accustomed to be utterly clueless anymore. I had already forgotten how slow and painful it is to learn something from scratch. So give yourself a break and judge yourself the same way you would judge a stranger. Don't expect to become stellar in a matter of months just because you're smart. Hint: so is everybody else who is coding for a living.
Re: When and Why to Learn to Program
#15Good article about finding out how to get motivated to learn something, but this has very little to do with coding aside from the context of the goal. Aside from that, stuff like: "Here's why I finally learned to code: I've been a web entrepreneur since I was eleven years old — for over sixteen years now..." Makes me discount just about everything that was written. I just have a bitter taste left over from this massi…
Re: When and Why to Learn to Program
#16Re: When and Why to Learn to Program
#17Re: When and Why to Learn to Program
#18The rivers of nonsense questions coming into stackoverflow from well meaning people who are not able to describe the difference between a variable and a browser and who don't have the capabilities to care unless it solves their immediate problem at hand leads me to believe that not everyone should program. in fact, many people who do program should be politely asked not to. Stackoverflow needs a "entrence barrier" te…
I've made good money over the decades as a programmer, but the technologies come and go like presidential administrations. I'm always a newbie at something. That's part of the fun. I'm always the guy who "doesn't know the difference between a variable and a browser" in something despite simultaneously serving on an "experts committee" in something else. I've lost count of the number of times I've spotted a "related question" on the SO sidebar while grazing for useful info, thought, Oh, yeah, what IS the answer to that one?, clicked it, and been informed by SO that they won't allow it to be answered because the question is "not constructive". Hunh?? The answer would have been constructive. Stopping people from answering a question that others are wondering about: THAT's what's not constructive.
Oh, but what if people are allowed to ask dumb questions, where dumb means questions that you already know the answer to? Well, then, it might be hard for you to find answers to your "smart" questions, right?
It sounds to me as though the solution is to worry less about dumb questions and more about the dumb search technology they have for matching incoming questions to their answers. With better technology than a bunch of tags and a 1980s-quality search engine, they wouldn't have to put so much effort into blocking questions and could put that effort into providing more answers.
Re: When and Why to Learn to Program
#19I definitely also have a project in mind, but I don't know where to start aside from the HTML and CSS I've learned.
Re: When and Why to Learn to Program
#20What about the suggestion to learn Ruby? I've been trying to decide which language to start on... I thought JavaScript, since I know nothing about Ruby on Rails. I definitely also have a project in mind, but I don't know where to start aside from the HTML and CSS I've learned.