Live data from Hacker News

The Ugly Side of Learning to Code

crowdcademy.com

11–20 of 62 posts

Re: The Ugly Side of Learning to Code

#11
"Coding uses a lot of thinking patterns that I hadn't really used since my math and statistics classes in college, and even back then not in this intensity"

And

"I guess my point is, that if you want to become a programmer, you have to be comfortable with having to learn new things constantly for the rest of your life."

So many conversations around "but I want to be a programmer, do I really need to learn math? Really, really?"

Yes, you do. But more disturbing than the resistance to learn math is the resistance to learn. Period.

What i like about the article is that, all though the writter admits there are some challenges, he does not whine about them, but instead he overcome them. Because of that, he has a good chance at succeeding in programming, or anything else for that matter.

Maybe not in 6 months... But he will get there

Re: The Ugly Side of Learning to Code

#12
post #2

"As a result I've become more focused, more logical and smarter. But I've also become more detached from everyday life and less fun to hang out with. I'm not sure yet if the change is permanent, but I certainly hope that it can be undone :)" 6 months away from programming, and you'll be fine :)

When I was in high school and just starting out I felt that I was becoming detached, and I hated it so much. At some point, however, I decided that I didn't really care if I was becoming more detached and less fun to hang out with. It was more like I had redefined fun, and I eventually found new friends that fell within this definition. There is definitely a change though, and I don't blame the author for feeling uncomfortable. You either learn to accept it or you walk away. The choice is yours.

Re: The Ugly Side of Learning to Code

#13

> "I'll never become a good programmer, but I strive to be the most capable brogrammer I can be." Being a competent programmer is a prerequisite to being a "brogrammer" (whatever that means).

Not necessarily if you want to be a brogrammer... watch the video, it from the first twilio conference. it's hilarious! :)

Re: The Ugly Side of Learning to Code

#14
post #2

"As a result I've become more focused, more logical and smarter. But I've also become more detached from everyday life and less fun to hang out with. I'm not sure yet if the change is permanent, but I certainly hope that it can be undone :)" 6 months away from programming, and you'll be fine :)

I've experienced this "detachment" with friends and family. I sometimes have to make an effort to really engage in regular conversation. It's like programming, continuous learning, etc. take so much brain power that I start to go into self-preservation mode. In social situations, it's sort of "turn it off or you won't have anything left for dealing with development work".

Re: The Ugly Side of Learning to Code

#15
I have a real problem with this:

"I guess my point is, that if you want to become a programmer, you have to be comfortable with having to learn new things constantly for the rest of your life."

I really feel like this is the outlook everyone should take on life, not just programmers. Maybe the causality ought to be switched; good programmers are people who have a "learn something new every day" outlook on life. Hell, it could even be said that good people in any field are those who take that viewpoint on life.

Re: The Ugly Side of Learning to Code

#16

I wish more business guys would try to learn programming, so well done sir. But I do have a quibble with this statement: > if you want to become a programmer, you have to be comfortable with having to learn new things constantly for the rest of your life". In my experience, the quickest way to tell that someone is not cut out to be a programmer is when they complain about the amount of continual learning that is a re…

That's so true! I used to love to learn... I mean I had to learn Spanish in 6 months when I moved to Costa Rica for an internship. Plus I've read at least two books per month for the last 3 years (business and psychology stuff). But learning to code was a lot more exhausting because it's based on knowledge and there's no room for bullshitting (unlike business ;)

Re: The Ugly Side of Learning to Code

#17
I think this post touches on an interesting point about web development (might apply to other areas too, but the web seems particularly bad). A lot of things appear to be easy (Rails, Django, Heroku, AWS, JQuery etc.), but the number of different components you need to manage is still overwhelming. Furthermore, you often end up having to develop a low-level understanding of problems that someone else claimed to have solved for you. While this low-level knowledge is useful, it does add significant amounts of complexity for beginners and people who might not be committed as the hardcore full timers out there.

As we seem to push more and more for the "everybody should learn how to code" mindset, I think there is a big opportunity for someone out there to combined managed and protected environments with the ability to write your own code. I don't know if the solution is unifying languages across front and back end or a better set of abstractions, but I see way too many obstacles for 'simple' coding (although the situation today is without a doubt better than ever), and I imagine this is some of what the author of this post ran into.

Re: The Ugly Side of Learning to Code

#18

I wish more business guys would try to learn programming, so well done sir. But I do have a quibble with this statement: > if you want to become a programmer, you have to be comfortable with having to learn new things constantly for the rest of your life". In my experience, the quickest way to tell that someone is not cut out to be a programmer is when they complain about the amount of continual learning that is a re…

I think that this is more and more true of most any job, though certainly programming is in the forefront.

Re: The Ugly Side of Learning to Code

#19

I think this post touches on an interesting point about web development (might apply to other areas too, but the web seems particularly bad). A lot of things appear to be easy (Rails, Django, Heroku, AWS, JQuery etc.), but the number of different components you need to manage is still overwhelming. Furthermore, you often end up having to develop a low-level understanding of problems that someone else claimed to have…

I wish that the learn-to-code movement had a greater emphasis on code as a utility belt, rather than "here's how to make a social website!"

Web dev is exceedingly complex and involves a lot more memorization of arcane things than does general purpose programming. Whereas for a non-technical founder, the important thing to learn is how aspects of business and content can be handled in modular, abstract ways (something that is apparent after learning loops and methods).

Learn enough code to understand implications of such things as granularity of data, taxonomy, and automation...if a novice can generate a static webpage chart from mashing up multiple data sources, that is hugely useful

Re: The Ugly Side of Learning to Code

#20

> is it possible to become a decent programmer ... No. > ... and build a MVP in just six months? Yes.

exactly. Thinking that you're a decent programmer after 6 months is nothing but hubris, and shows you're still in the stage of not realising there is much, much, much more to learn. Or his definition of 'decent' does not match mine.
Post reply on HN