Linked by Howard Fosdick on Fri 13th Apr 2012 20:21 UTC
In the News Six-month-old web site Codecademy claims you can learn programming through its online tutorials. The free modules on JavaScript are now available. The site also allows anyone to post their own programming courses. The site has good funding, but question is: can you really learn programming this way? One blogger enthuses that Codecademy's approach "looks like the future of learning to me," while another slams it saying "Seriously? Wow, bull**** badging and sh**ty pedagogy wins the day in ed-tech investing." What do you think?
Thread beginning with comment 514242
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: What do you think?
by Loreia on Sun 15th Apr 2012 09:45 UTC in reply to "RE[3]: What do you think?"
Loreia
Member since:
2012-01-17

:-)
And that comes after years of reading OSNews.

I strongly believe that access to knowledge should be free. After that, it is up to each individual to decide how much time and effort he/she is willing to invest in learning.

I do have university diploma and I don't want to downplay importance of formal education, but I think that programming is way too dynamic for classical education with semesters and grades and professors. Most of what I know about computers I've learned on my own AFTER university. So, the best way to become a programmer is to:
1. learn basics of coding (loops and functions can be learned on your own on web sites, by reading downloaded PDFs or by buying and reading book)
2. after that start a small project of your own. It is important to learn how to solve problems by helping yourself with Google search and local library search (any serious programmer has a TON of PDFs on his hard drive)

--- University will give you this too, albeit in a more formal and strict way, but really important stuff is nbr 3. ---

3. and finally, join a "real" project (at work or by joining some open source community) to see what collaboration is, which standards and conventions to follow, to have your code reviewed and so on.

After several years of experience doing number 3. you can call yourself an experienced programmer, with or without a piece of paper that says "this guy graduated in out University. It is the best University in the world. Please give him a job."

Diploma may be an indicator of someone's knowledge, but any serious job interview I've done focused on my knowledge, skills and previous work experience. With time, I adopted the same approach.

BR
Loreia

Reply Parent Score: 0

RE[5]: What do you think?
by Alfman on Mon 16th Apr 2012 02:47 in reply to "RE[4]: What do you think?"
Alfman Member since:
2011-01-28

Loreia,

Your first two suggestions are strait forward.

"3. and finally, join a 'real' project (at work or by joining some open source community) to see what collaboration is, which standards and conventions to follow, to have your code reviewed and so on."

"After several years of experience doing number 3. you can call yourself an experienced programmer..."

This last one can be a catch-22 at times, since employers often don't want to give experience to those who don't already have it. Many employers are strict about counting only professional work experience too.

Lucky for me I have experience, but I face a different problem. The market segregates us into sub-categories like embedded programming, database programming, or web development. For me, it has been surprisingly difficult to transition my experience in one role into gainful employment in another role. Referrals for new work are more of the same.

Reply Parent Score: 2