Live data from Hacker News

How I Became a Programmer in ~12 Weeks

mattdeboard.net

81–90 of 190 posts

Re: How I Became a Programmer in ~12 Weeks

#81
Credit to you for sticking with it for 12 weeks and being successful.

I had been attempting to learn how to program (Ruby) for the past 6 months (from a ZERO programming background) and in the beginning I honestly could not do more than one week learning 'intensively' before I had to take a break to let all the new concepts and information settle in.

Perhaps it's just my style but I've found learning a little bit everyday is more effective in the long run than cramming it into a condensed period of time. It's surprising how you can take a break from a piece of code and have everything come together when you look at it again.

That said, learning how to program in 'X weeks' sounds great and I wish I could have done it!

Re: How I Became a Programmer in ~12 Weeks

#82
post #22
post #11

Then he didn't become a programmer. He became Django programmer.

He learned some Python, Django, HTML, CSS, Javascript and wrote programs. Can "programmer" not encompass both people getting their feet wet and 20 years experience mastering multiple languages?

He hasn't made any hard choices, he just picked what is most available and put the pieces together.

Frankly he'd have bought me if he made his hands dirty with some obscure 8bit assembler. There he'd have to really THINK his way out.

At least some sweat during rolling his own data structures and algos around them would make him something in a shape of a programmer, but not this.

Of course what he's done is cool, learning anything new is worth some pat on the back. But this is a newsfeed on hacking, and Lords, it ain't hacking. Let's call things what they are, ok?

There's also the problem that some people like him start calling themselves programmers on the job market and when we're trying to hire them, they occur to be only Django programmers with very limited abilities. Practice makes perfect, but they didn't do it yet. Have some interviewing experiences like that. Not funny.

Re: How I Became a Programmer in ~12 Weeks

#83
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...

Well, in general terms, if the USMC (or the Army, or the Navy, or...) really did build up work ethic - a personality trait that correlates quite a bit with income - why do veterans seem to do so poorly, even veterans who never experience the confound of war? Because personality traits are, like IQ, very tough to alter. (This is why that psilocybin-increases-Openness study got so much play.)

Re: How I Became a Programmer in ~12 Weeks

#84

Earlier quoted context omitted.

What load of bull. What separates a 'programmer' from a 'Django programmer'? I can't think of any way to make that distinction that isn't logically self-defeating.

A programmer is language agnostic and has a deep understanding of both algorithms and computation. I find the term para-programmer to be an apt description of anyone else. Why is this on the front page btw? Aren't we all hackers here? What makes this news?

Maybe a grad student has those things ( ;) ), but once you realise computers aren't the hard part about building software, you realise that there are a whole host of skills you need to be a successful programmer, that have nothing to do with algorithms or computation.

If all you have is a strong understanding of algorithms and computation... your just a computer geek. Doesn't make you a good 'programmer' (in the sense that you can produce something someone wants).

Re: How I Became a Programmer in ~12 Weeks

#85
post #62

Earlier quoted context omitted.

"learned" was DEFINITELY an overstatement. I knew they existed is more accurate.

I'd argue that it still predisposes you very strongly. If nothing else, just in the abstract sense that you are familiar with the computer and don't see it as some scary or magical thing.

My college roommate ran several BBSes but ended up being pretty dumb with computers in college. It always made me scratch my head.

Re: How I Became a Programmer in ~12 Weeks

#86
You can certainly be a programmer in 12 weeks, but you will be different programmer than what we are expecting here.

You can also learn programming by reading 'Learn programming in 30 days'. But that is a very different kind of programming than what most people are expecting in this thread. You can learn enough programming to begin to understand how to work with software. It gives you a start. It also works if your job is extremely trivial. And I think the target audience for the book is those kind of people.

Coming to programming as a profession, in that case there are a lot of aspects that influence your full time profession, among that is giving your full learning every detail of programming and related ecosystem. Other aspects are productivity, management, analytical skills, UI design, requirements gathering, people skills. Also there are many other things required to win in practical software environments like working under tough deadlines, learning to deal with frequent stress and burnout. Keeping in touch with rapidly changing tech scenario, tools and languages. The list goes endless. I haven't covered even a percent of what I wanted to write.

Your regular data structure and algorithm sauce is probably 1% of what is required to win in practical software development today. There are 99% of other things which are not taught in books, colleges and universities. You have to learn them through experience, by working.

So just in case you think you have spent 10 years learning all the secret recipes in computer science books but are not good in other areas. You are no better than the 'Learn programming in 30 days guy'. Because if has problems in a set of areas, you have equal number of problem with another equivalent set.

This is something I have seen among so many bright, people with great academics, who don't make it big in the industry. They just don't understand so many practical aspects of the industry. Just like how 12 weeks programming guy doesn't understand all aspects of practical programming.

Re: How I Became a Programmer in ~12 Weeks

#87

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…

My biggest problem with the article is that it's essentially a puff piece about how awesome the writer thinks he is, and how special he is for being able to learn the basics in a short amount of time. The post is entirely too hand-wavy about actual details; telling someone to read some blogs, Q&A sites and code doesn't help anyone. Where is the substance? Were there any interesting ah-ha moments? What would he do dif…

My blog has comments. My email address is in my HN profile. If you wanted more information you could've asked instead of insulting me.

Re: How I Became a Programmer in ~12 Weeks

#88
post #53
post #39

My mantra for the past 2 weeks has been that there's never been a better time to learn to code, simply because the resources are so abundant and available. I'm self-learning web development right now. Between HTML Dog, W3 Schools and Google, I have more than enough information. I wanted to play around with WordPress-fired up a VirtualBox VM with Fedora, and an hour later had completed the 'famous 5-minute install.' W…

Exactly. As a 17-year-old I've been able to run my own little freelance business. The internet = opportunity if you use it right.

Awesome. I wish I was doing this at 17. Ten years later I'm making up for lost time. Congrats for getting after it early!

Re: How I Became a Programmer in ~12 Weeks

#89

I absolutely admire you. There are so many people in this world who pretend that something is preventing them from learning or doing something and you went out just did it. You may (or may not) be the best engineer in the world, but I'd hire you in a hot second just because you have the tenacity to make it your mission to figure something out. Sometimes, 90% of writing code is just sticking with a problem until you g…

[deleted]

Re: How I Became a Programmer in ~12 Weeks

#90
post #84

Earlier quoted context omitted.

A programmer is language agnostic and has a deep understanding of both algorithms and computation. I find the term para-programmer to be an apt description of anyone else. Why is this on the front page btw? Aren't we all hackers here? What makes this news?

Maybe a grad student has those things ( ;) ), but once you realise computers aren't the hard part about building software, you realise that there are a whole host of skills you need to be a successful programmer, that have nothing to do with algorithms or computation. If all you have is a strong understanding of algorithms and computation... your just a computer geek. Doesn't make you a good 'programmer' (in the sens…

What a ridiculous point. If you don't have such understanding, you're just copypasting someone else's instructions.
Post reply on HN