Live data from Hacker News

How I Became a Programmer in ~12 Weeks

mattdeboard.net

181–190 of 190 posts

Re: How I Became a Programmer in ~12 Weeks

#181
post #150

Oh John, I wouldn't call him a pilot, you know, he flies people in his small airplane and gets paid for it but he doesn't know how to fly helicopters or jets and he didn't study fluid dynamics, so he's a "Cessna pilot".

"You're more of a wing wrangler."

Re: How I Became a Programmer in ~12 Weeks

#182
post #164

Earlier quoted context omitted.

>> why do veterans seem to do so poorly What are you saying that we do poorly at? Your comments are more "confounding" to me than any war situation I was ever in.

You do poorly at kicking ass & making bank in civilian life. This is a tricky subject, of course (any statistics from 2001 and on are basically worthless because all the suicides and whatnot from Iraq & Afghanistan trash the data), and there are all sorts of correlation/causation problems (maybe the people who join would do poorly in the first place - these days, most of the graduating class of Harvard heads to Wall…

Don't confuse work ethic with motivation. I know a number of successful veterans who are kicking ass and making bank in civilian life. I also know a ton who are just 'retired' and enjoying their low-key life with friends and family.

You can't switch from studies and causation/correlation to just stating without citation that they suck at kicking ass.

Re: How I Became a Programmer in ~12 Weeks

#183
Let me say that in my opinion, Matt DeBoard has certainly earned the title of "programmer." Welcome to the club, Matt, and you have my appreciation for the hard work you put in. It sounds to me like you're going about it in the right way; I encourage you to keep it up, and I encourage others to do the same (that is: find a way that works for them, not necessarily copy your approach). Please pay no attention to the negativity. As spacemanaki and others have pointed out, Matt is not a complete programmer yet, and he has more to learn. But I think he knows that, and remains open to learning, which is the important point. I've got more than 12 weeks under my belt, but I still feel like I'm learning all the time. My thoughts are summed up by the character of chef Gusteau in the movie Ratatouille: "Anyone can cook." This very pointedly does not mean "everyone can cook" -- it takes a combination of interest, aptitude, and long study to become a chef, and most will not make it -- but it does mean that there is no one route to achieving competence, then expertise, then mastery.

Re: How I Became a Programmer in ~12 Weeks

#184

The amount of negativity in this thread is depressing. I think a lot of people either didn't read the article or just skimmed it. For those of you who are citing Peter Norvig's essay, I also thought of the essay when I read this; it's one of my favorites. I've read it several times because it is humbling and inspires me to rise to the challenge of really becoming a great programmer. If Matt reads it he might feel sim…

Dr. Norvig agrees with you:

http://news.ycombinator.com/item?id=3278080

Re: How I Became a Programmer in ~12 Weeks

#185
post #167

Earlier quoted context omitted.

Ahh I misread into your post. Yeah, the article wasn't well written and could've gone into more detail about different things but honestly I feel that an experienced programmer would know a better route for someone to take, for example I know a lot of programmers suggest people start with SICP.

Starting someone who has no programming experience with SICP is idiotic.

The book was written for an introductory programming course at MIT. It is more rigorous of a book then most and may not be for everyone starting programming, but the right people will seek it out. It is also invaluable in that it teaches the programmer about programming more then languages.

Re: How I Became a Programmer in ~12 Weeks

#186
post #185

Earlier quoted context omitted.

Starting someone who has no programming experience with SICP is idiotic.

The book was written for an introductory programming course at MIT. It is more rigorous of a book then most and may not be for everyone starting programming, but the right people will seek it out. It is also invaluable in that it teaches the programmer about programming more then languages.

Exactly -- the right people will seek it out.

Re: How I Became a Programmer in ~12 Weeks

#187
post #176
post #168

Earlier quoted context omitted.

A musician is someone who can communicate to other people via musical instruments. You are a musician, you just might not be a very good one. Similarly a songwriter is someone who creates songs, so you are a songwriter, you just might not be a good one.

The only thing that I can really communicate via a musical instrument is that it's a good thing I'm a programmer.

Hahaha, yeah that's why you aren't a very good musician yet. I think it's important to make a distinction though because it removes forms of elitism and encourages a friendly environment. People don't learn from "You can't play Flight of the Bumblebee on guitar therefore you aren't a real musician.", rather they learn from observing and participating.

Re: How I Became a Programmer in ~12 Weeks

#188
post #185

Earlier quoted context omitted.

The book was written for an introductory programming course at MIT. It is more rigorous of a book then most and may not be for everyone starting programming, but the right people will seek it out. It is also invaluable in that it teaches the programmer about programming more then languages.

Exactly -- the right people will seek it out.

Seeking things out doesn't just mean you read these things on articles or stumble upon them in libraries, it can also detail things like conversations with other people. Either way it is just an example that a guru might have a path that someone can follow that will get them somewhere quicker then a non-guru.

Re: How I Became a Programmer in ~12 Weeks

#189
post #188

Earlier quoted context omitted.

Exactly -- the right people will seek it out.

Seeking things out doesn't just mean you read these things on articles or stumble upon them in libraries, it can also detail things like conversations with other people. Either way it is just an example that a guru might have a path that someone can follow that will get them somewhere quicker then a non-guru.

You're misunderstanding. I disagree with your fundamental premise, which seems to me to be that SICP will take someone from zero to hero quicker than more accessible methods.

Re: How I Became a Programmer in ~12 Weeks

#190
post #41
post #34

Earlier quoted context omitted.

Let's not confuse correlation with causation; I once looked around for studies showing experimental interventions which actually increased work ethic (specifically, I was looking for studies on the Big Five construct 'Conscientiousness') and didn't find any. So, I'm sure the work ethic that let him join and last 10 years in the USMC helped.

Lets not confuse an absence of evidence as an evidence of absence - just because there's no study yet that shows that 10 years in the USMC helps with work ethic, doesn't mean that 10 year in the USMC does NOT help with work ethic (unless you mean to say in your survey of the lit. you found something claiming the opposite of the op's claim). That said, I'm inclined to agree with your last statement...

You should know that absence of evidence actually is evidence (though not always very strong evidence) of absence:

http://lesswrong.com/lw/ih/absence_of_evidence_is_evidence_o...

Post reply on HN