Showing posts with label Joshua Kemp No Degree No Problem. Show all posts
Showing posts with label Joshua Kemp No Degree No Problem. Show all posts

Sunday, August 16, 2015

Back to School! Taking CSC256: Computer Programming I


One of my big concerns about starting this project during the summer was what would I do once school started and I had to teach my classes again.  In Kemp's book he wisely suggests you need to aim for about 20 hours a week (about 3 a night) and I was concerned that I would allow this to slip when school started.  I have already seen that if you allow too much time to pass in between studying it takes some time to get back into the flow again.

However, a couple weeks ago, it occurred to me that I work at a college (brilliant right?).  There are a few computer science courses here that I could sit in on.  While we only have a 2 or 3 a semester because we only offer a minor, there is a Computer Programming course this semester focuses on Python.  I debated about whether I wanted to ask my colleague to sit in on it or not, concerned that this would maybe be weird.  However, ultimately I decided to do it.

I think having some accountability here as well as 3 times a week scheduled to learn programming during the day will keep me focused and will actually be fun.  It has been well over 10 years since I was a student in an undergrad class and I am filled with both anticipation and dread.  It will also be a pretty intense experience given that there are only 6 people in the class.  I w
ill have to keep up with my work or risk humiliation at the hands of my co-worker!

I am not taking the class for credit, though I suppose I could.  I guess I am not at this point due to some lingering anxiety about whether or not I can actually survive it!  I have a student who has taken these courses and he insists that they are not difficult, but I will see for myself before I actually get a grade on record!  I will report on this fascinating and potentially humbling experience throughout the semester!

On a side note, I got in a lot of good work yesterday and continue to actually learn about coding while writing about learning about coding.

Total hours into Programming: 69 (4 today)
Total Weeks Programming/Hours per week: 3/23

 Progress on Shaw's Learning Ruby the Hard Way: Finished Exercise 1-9

My Text game: 2 hours, 107 lines


TreeHouse (487 Points, 8 Badges) 

Code Academy Points: 630
Code Academy Badges: 65
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Progress on Hartl's Tutorial Ready to start Chapter 3! 

Resources Finished:
Josh Kemp's No Degree, No Problem 8/14/2015
Chris Pine's Learn to Program 8/9/2015 

Saturday, August 15, 2015

Josh Kemp's No Degree, No Problem Review

I purchased Josh Kemp's No Degree, No Problem yesterday for around $10 on Amazon.  You can go check it out from his website if you are interested.  The book does something that very few others have attempted - turning the copious books, e-books, tutorials, and websites available for early coders into a doable program.  For this, I am profoundly thankful.  It seems like the coding world believes that there are not enough tutorials out there and so they keep making more.  However, a book like this is maybe more useful because it makes some sense out of what is there.

When you get this book, you are paying for two basic things (1) Kemp's story and (2) practical advice.  Kemp's story is an interesting one about how he became committed to becoming a coder.  Long story short, he faces a lot of obstacles and continues on when most of us would have quit.  However, what is so inspiring about it is that he makes it without a strong background in the field.  He learns and networks on his own after recounting some truly dismal experiences with coding boot camps.

After his story, Kemp lays out his "Roadmap".  The roadmap should not be confused with a degree program or a course in how to become a rock solid coder with deep knowledge in everything.  The argument Kemp makes (convincingly, I think) is that you could endlessly study and just being a master of one of these skills will not get you hired.  He is interested in offering you the foundational skills that can get you into that job.  Kemp accurately points out that a junior developer's main job is to learn anyway and so following his program will get you the starting tools you need to make it through the interview and build those skills later.

This text is practical and pragmatic in the extreme.  It is broken down into very easily digestible parts with very specific directions.  Nothing is left unsaid in terms of the program of study.  Kemp lays out how much time you need to study, what kind of computer you need, and speaks to any costs you will incur.  The roadmap itself is very complete and features discussions of your own programming environment, the best tutorials and in what order to do them, why become a Rails developer, and even how to network and market yourself.

If you are looking for the quickest path to becoming employable, I think this is probably it.  It is very complete and this is a very pragmatic job-centric text.  Everything focuses on the dream of a junior developer job.  If you want a philosophical discussion of coding or something that will lead you to true mastery this is not it.  He has one clear goal here and that's what you are getting with the book.

There are, however, a few drawbacks.  This book features only one real track and he strongly encourages a Mac.  If you don't have a Mac, this will not work as well for you.  He also only covers Rails.  This is taking you specifically to Ruby on Rails web development.  If you want to do something else, you will only get value from the story and some of the basic interviewing tips.  There are a few basic errors in grammar etc throughout the book which the Amazon reviewers really harp on.  I did not find them to be that egregious, though I do read problematic writing from students in training as my current job.

Overall, I would recommend the book as a strong blueprint for making sense of the vast pool of resources out there.  Kemp gives them to you in an order which they can be digested.  I am using it as my overall guide as I learn to code, though I am adding a few other things along the way as well.  Ultimately, I will come back and post an addendum to this review when I finish his program and let you know what I thought, but if you want a practical guide to the coding resources and a plan for working through them to become a Rails developer proceed.