Live data from Hacker News

How I Became a Programmer in ~12 Weeks

mattdeboard.net

91–100 of 190 posts

Re: How I Became a Programmer in ~12 Weeks

#91
post #20

I envy that the author learnt programming and web development now as opposed to even a few years ago. Without devolving into "in my day I walked ten miles in the snow just to compile"; it's just so much more pleasant now. Stack Overflow, Heroku (and similar), GitHub, PDF Books. Obviously it takes time and effort to get better everyday but the learning curve is a bit flatter now.

[deleted]

Re: How I Became a Programmer in ~12 Weeks

#92
post #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 j…

I get the point of this post, even if it seems a bit of a tangent from the what the author is saying, but

>>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'.

and

>>Your regular data structure and algorithm sauce is probably 1% of what is required

is just false. Sure, studying classical CS concepts is not all there is to software development and success in the software development industry, but your comment largely renders advanced degrees, like PhDs, about as useful as some poorly written Java book with regard to success as a software engineer.

Re: How I Became a Programmer in ~12 Weeks

#93

I did something similar when I got started and yeah it got me a job but that was just the beginning, now, about 2 years later, I'm still learning and pushing myself to learn lower and lower level things about software development (as I started with high-level, dynamic languages) as well as more about design patterns, etc. Its definitely true that there's always more to learn so never be complacent. Its definitely pos…

[deleted]

Re: How I Became a Programmer in ~12 Weeks

#94
post #68

The hardest part to that for me is the "get to know people" part. He already had a mentor before he started learning. How would one get a mentor in the first place? How do you get to know other people?

To be fair, the friend/mentor in question started out as a dude on a small private forum I used to frequent. The forum had an AIM chatroom and he made fun of me mercilessly me for years for making stupid decisions.

Go to meetups and lurk IRL IMO. Just start small conversations. Say hi, ask what someone's working on, what the program is they have open, if they read HN or Reddit or whatever. Let them know you admire their work and ask for help.

Re: How I Became a Programmer in ~12 Weeks

#95

Learn a language, not a web framework for god's sake. Learning frameworks is harder than learning programming languages, IMO, especially after you lean one language. You should learn both.

Yeah of course it's harder, because it's built on top of a platform you don't understand. It's easier to make good design decisions in Python if you come from a background rich with C experience, right? Because you understand what's going on under the hood. Without that experience -- like me -- you just fumble around like a big stupid klutz until you realize one day that you need to learn the lower level stuff.

So naturally when you're talking about dealing with an abstraction layer built on another abstraction layer it's going to be even hard to understand. That's why I say don't learn the framework. Learn the language, the concepts, the principles. It will make understanding the complexities easier to untangle.

Re: How I Became a Programmer in ~12 Weeks

#96

Hmm, I started programming over a decade and a half ago, writing my own little game engines in dos, and a nice little x-mode GUI. I've worked as the software architect for a moderately popular (top 2000 alexa) social networking websites, I've worked at fortune 500s, I've been on the dev side, the test side, the pm side, and worked as an IC and as a lead/manager. I still don't really consider myself as being anywhere…

If you program computers for a living, guess what? You're a computer programmer. Congratulations, you made it.

Re: How I Became a Programmer in ~12 Weeks

#97
post #82
post #22

Earlier quoted context omitted.

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, lear…

[deleted]

Re: How I Became a Programmer in ~12 Weeks

#98

Earlier quoted context omitted.

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.

I don't think he was trying to be insulting. From what I gather, he was trying to justify the negativity theme in the comments for this post, which was the subject of the original comment. I agree that the blog post was not detailed enough, and didn't talk enough about HOW you became a programmer in 12 weeks.

Re: How I Became a Programmer in ~12 Weeks

#99
post #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 j…

No where in his post did he claim to understand all aspects of programming. This guy spent 12 weeks learning the basics, and is now working as a full-time programmer - presumably this is the road to "learn[ing] through experience, by working".

Re: How I Became a Programmer in ~12 Weeks

#100

Earlier quoted context omitted.

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.

I don't think he was trying to be insulting. From what I gather, he was trying to justify the negativity theme in the comments for this post, which was the subject of the original comment. I agree that the blog post was not detailed enough, and didn't talk enough about HOW you became a programmer in 12 weeks.

What kind of information do you mean? I programmed, asked questions, programmed, read source code, and programmed. There's zero magic. I learned in the same way all human beings learn.

We're knowledge workers. I gained enough programming knowledge to be a programmer. Where's the confusion?

Post reply on HN