Showing posts with label Chris Pine Learn to Program. Show all posts
Showing posts with label Chris Pine Learn to Program. Show all posts

Saturday, September 5, 2015

TreeHouse Ruby Operators, Control Structures, and Collections by Jason Seifer Course Review

I decided to finish the Ruby track on TreeHouse before I continued on with Rails.  While I have worked with Ruby for quite some time, there is still much of it that I need to relearn, refresh, or learn for the first time.  While I had approached much of this material before, I definitely did needed the refresher.  I come to this review as someone who has completed Code Academy's Ruby course, worked through Chris Pine's Learning to Program, and having completed about a third of Zed Shaw's Ruby the Hard Way book.

When I saw Seifer staring me down I had some reservations.  Last time I saw this man he was speed racing through the Rails tutorial and was a major player in the coding crisis that ensued after I "halfpleted" the course.  By halfpleted I mean that I worked through it but conceded that I was essentially lost for the whole second half which i the worst case scenario of online tutorials and a scenario that played itself out many times when I worked through Code Academy.

Fortunately, my fears were unfounded.  The speed-racing alien that replaced kindly Jason Seifer seems to have left his body.  This was the friendly and kindly fellow who taught me Ruby Basics!  He moved slowly and I was easily able to follow along in Workspaces without excessive video pausing.  Generally speaking, these courses reminded me of why I subscribed to TreeHouse in the first place.  It features a nice combination of quizzes, coding, and videos.  The videos are succinct and it is not torturous to watch quite a few of them in one sitting.

These courses do a fine job of covering arrays, hashes, and programming branching in Ruby and I came away with a stronger knowledge of these subjects and was closer to mastery than before.  There is also a really nice exercise during which you have to build a grocery list.  The exercise is difficult where I had to look up some of the tough parts but not so tough where I felt lost and hopeless.

These two courses are pretty quick and accomplish their aims without much difficulty.  I did not feel like I was just doing it for the points or clicking through as I had with Rails.  They are perfectly paced and offer enough complexity to get you thinking and provide a solid foundation as we move forward.  Next up, I take on loops which has been a topic I have a basic understanding of but certainly need more practice on.

Resources in Progress:
Total hours into Programming: 111 (3 since last time )
Days into Programming/Hours per day: 2.5 Hours Per Day (Goal:3.0)

Progress on Gaddis' Starting out with Python: Done With Chapter 1, Appendix A,B


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

My Text game: 3 hours, 118 lines

TreeHouse (3437 Points, 40 Badges)

Code Academy Points: (752 points, 78 badges)

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

TreeHouse Make a Website Track 8/17/2015
TreeHouse Ruby Basics 8/20/2015
TreeHouse JavaScript Basics 8/22/2015
TreeHouse Console Foundations 8/24/2015 
TreeHouse Git Basics 8/25/2015
TreeHouse Installing a Ruby Environment 8/26/2015
TreeHouse Making a ToDo Rails App 8/31/15
TreeHouse Ruby Logical Operators 9/4/2015
TreeHouse Ruby Collections 9/5/2015

Code Academy Make a Website Course 7/29/2015


Code Academy Ruby Course 8/5/2015
Code Academy HTML and CSS Course 8/24/2015

Wednesday, September 2, 2015

Beginner Coding Resources and the Curious Case of the Cliff

One of the most amazing things about learning to code is that there are so many resources out there!  You will want to do them all and you will want to complete them all, I know that's how I feel/felt.  That said, all resources are not created equally, even if they all often bill themselves as being beginner friendly.

I have found that there is a curious learning curve in beginner resources including Pine's Learn to Program, Code Academy, and the TreeHouse Rails track I just took.  The curve, or cliff as I call it, usually happens around 75% of the way through the resource.  Whereas they will spend inordinate amounts of time explaining the most simple of tasks early on, there comes a point where things start racing and zooming and explanation is at a premium.  Terms, language, and sophistication pick up at a rapid pace and you (the beginner) begin to feel like a total jackass which should not be the pedagogical goal.

In the case of Pine, he has you knee deep in problems that his previous 75 pages simply do not prepare you for.  In the case of the Rails track on TreeHouse, Seifer seems to start in the middle of an intermediate course on test based design and literally races through making an example app.  One of the things I realize this field needs is a guide to the guides.  Many of these resources that have "cliffs" are probably not that bad for the intermediate, but for the true beginner, they are absolutely demoralizing.  In fact, spending 15 hours building up to a Ruby tutorial that did not end up working out for me has left me pretty salty about the whole thing.  It's called the Rails track and that's the one thing that is not explained in any kind of detail!  I love the points, the interface, and the teachers, but in the end, it did not help me learn rails.  I learned many thing leading up to this, but at the end of the day, the course fell short.

Where do I go from here?  I think I am going to try to scale back to more Ruby programming fundamentals, finish up Shaw's book, take the Ruby course in TreeHouse, and then get into a new book I have discovered which draws rave reviews from beginner by Daniel Kehoe entitled learn Ruby on Rails.

Frustrated but not defeated!

Monday, August 24, 2015

TreeHouse JavaScript Basics by Dave McFarland Course Review

I entered this course a little bit differently than I entered the HTML and Ruby courses and I do think this colored my experience a bit.  When starting those courses, I had completed a number of resources focusing on the material already.  This does not mean I had them mastered, but I had at least seen the syntax before.  With JavaScript this was not the case.  This was the first resource I had ever worked with to learn JavaScript.

At first, this was tough.  While McFarland is the most natural of the three teachers I have encountered on TreeHouse, he is also the fastest.  In fact, for the first time on TreeHouse there were times I totally stopped following along on their integrated Workspaces platform.  This man types like a friggin maniac and even for those who type pretty quickly you are going to need to pause it.  Combine this with some of the strange syntax embedded in JavaScript and there are going to be some moments of confusion.

That said, I think McFarland might be my favorite of the teachers in terms of his manner with the viewers.  He is very natural and conversational and you do feel like you are in a classroom with him.  Once I decided to just focus right in on what he was saying and picking my spots on Workspaces, I was able to get what he was saying pretty easily.  While some of the other teachers can hammer a simple point over and over again, McFarland doesn't do this.  He gets right to it.

I should also point out that the explanations built into the course are really nicely done.  He explains concepts such as if/else if/else statements and functions in the best way I have yet heard (and I have read a lot on these basic programming elements).  McFarland draws in real life examples and features helpful visuals to back up his points which add a lot to the course and really help you understand what the benefits of a function or the if/else tree are.

This course also features a bit of a different element: integrated challenges.  While it still has quizzes, simple code challenges, and videos a few times throughout the course he will give you a more complex challenge separated off in its own video.  In these challenges the directions are embedded in Workspaces and you are to work through the solution on your own before playing how he solved it in the next video.  I thought these were a nice touch and added another level of complexity to the course.  I also felt these were doable.  Some code challenges (Pine I'm looking at you!) are insane for the level of the person working them.  They seem to come straight from the moon.  These challenges are ones that you can actually do at your level.  There is nothing more devastating than reading a code challenge and feeling like "Ok, I'm an idiot" right after you read it.  These can actually be done by someone of the course's target's level.  

This course did, however, seem to be a little bit out of step with Ruby Basics just in terms of its coverage.  It was much more extensive and deeper than the Ruby basics course.  You get pushed through a lot of important and basic concepts, and you are expected to be a semi-functional basic programmer when you get done.  While the Ruby course really was like dipping your toes in a new language, this course throws you in a bit more.  My only other issue was that at times my Workspace did not function all that well.  I am sure this was due to my internet settings on my browser or something simple, but it did happen from time to time.

Overall, this was a nice course which felt a lot more challenging than Ruby Basics.  I spent more time pausing, taking notes, and thinking as opposed to simply waiting for the videos to end.    If McFarland would slow it down just a hare I think we would have the perfect formula here.  That said, I understand (as a teacher of sorts myself) how excruciating it can be to slowly work through simple material.  I am sure he is doing his best, but sometimes old newbs like me need it just a bit slower!


Code Report!

Resources in Progress:
Total hours into Programming: 90 (3 since last time )
Total Weeks Programming/Hours per week: 4/22

Progress on Gaddis' Starting out with Python: Done With Chapter 1, Appendix A,B


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

My Text game: 3 hours, 118 lines

TreeHouse (1779 Points, 21 Badges)

Code Academy Points: (702points, 72 badges)

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

TreeHouse Make a Website Track 8/17/2015

Code Academy Ruby Course 8/5/2015


Code Academy Make a Website Course 7/29/2015

Friday, August 21, 2015

Month 1: Looking Back

I started this in the strangest way.  I am a gamer and in mid July, I read an article on Kotaku about the "Exceptional Beauty of Doom 3's Source Code".  I did not really read the article deeply but have since read it many times.  The article (re)flipped a switch and  reminded me that I was very interested in code in high school (around 1995).  I even worked a whole semester on a project in BASIC under one of the math teachers at my high school.

I did not pursue coding because I was already in the process of deciding to hate math at that point.  When I got to college I saw that one would have to take many math courses to do anything with computers and so I turned from it pretty quickly.  Everyone was pretty surprised because I was a computer geek from age 13 on and worked pretty consistently with them after I bought my first one in the summer of 1993.  I think tying computers and coding to math makes some sense, but we are also losing a lot of great people to this marriage.  Coding has math in it, but it is also about logic, creativity, and critical thinking.  I also did not code then because the software was so expensive.  I always wanted to learn Pascal, but it was $100s of dollars and I never could muster up that much desire.  Now, it is all more or less free which is so amazing!

At any rate, this article reminded me of coding and so I googled it a few days later and came to a kids coding website with inspiring interviews from Bill Gates, Facebook guy, and a host of others.  I was intrigued!  Shortly thereafter, I discovered CodeAcademy and since then I have been off and running.  Let's take stock of where we are now:

The Good:
(1) I love it!  Learning new commands and solving mysteries you previously did not understand is so refreshing.  I am no master, but I have come so far in a month and have really loved learning every bit I have.  Coding is super fun!  (Yesterday I worked on understanding ARGV in Ruby!)

(2) I am working on it every day, because I like it!  I wondered when I first started how long I would do this for.  I do not dread it and I do not do it because I want to "finish what I started".  I look forward to learning, finding new resources and gaining confidence and skill.  Over the past month I have done something with coding every single day.

(3) I have found many (too many?) resources ranging from Pine and Shaw's books to TreeHouse, Code Academy, and Code Newbie.  I have made friends and acquaintances and have come to really love the community.  It is welcoming and inspiring!

The Bad:
(1) I need to focus fire.  I am doing too many things at once.  Currently I am working on 3 books, TreeHouse, and Code Academy.  This is probably too many.

(2) I have nothing to show for my study yet outside of a basic shell of a Ruby text adventure game.

(3) I am still a bit confused by GitHub and how to share work and I do harbor a fear that I will never actually be able to create things on my own!

Where is this going?  I have no way of telling if coding will be my next career move, but right now I am absolutely in love with it and can't get enough of it!  I am definitely open to pursuing options in coding, but before I commit to that, I want to prove to myself that I can write a piece of code that works and is useful.  As always, thanks for reading!

Sunday, August 9, 2015

Review of Chris Pine: Learn to Program

Today I did not do as much coding as in day past, but I did manage to get through Pine's book and figured I would write a review/wrap up featuring my perspectives.

Chris Pine, Learn to Program, Second Edition, Pragmatic Bookshelf, 2009.
List Price: 24.95
Realistically: $5-$15 on Amazon, mostly free online:
https://pine.fm/LearnToProgram/
*I purchased the hard copy from Amazon for $15.

First off, I am coming from only having completed the CodeAcademy Ruby course.  This means that I have very little background.  If you have more experience than me, this may not be the right review for you.  However, if you are a coder-in(self)training, at the start of your journey you may find this useful.

Points of Style
First off, the book is generally a pretty quick read, it has 14 Chapters of really dense programming knowledge as well as an epilogue of sorts featuring his solutions to the exercises in the book.  This amounts to around 120 pages of material which seems pretty slim until you get into it.  Stylistically, it is written conversationally and there are regular attempts at humor.  If you hate this type of jokey writing, you will not enjoy this book.  I personally liked it because it takes the edge off of a difficult and at times intense subject.  The example programs are also full of attempts at humor.

Best Features
Pine really has a gift for making the complex seem simple.  This is especially try in chapters 1-8 as he effortlessly guides you through some of the basics of Ruby.  Beyond that, I loved his example programs.  He features copious in program notes (using #) and really tells you what is happening here.  Even in some of the later chapters when much of it was flying over my head, the programs never lost me.  This is really fine work and helped me to understand what he was doing.

On a related note, the chapters are not too deep.  Each chapter has one goal and it goes about its business pretty quickly.  You will not find yourself having flashbacks to math class marooned in the middle of a never ending chapter.  I always felt energized when I completed a chapter even if some were only 8-10 pages.  Each chapter also features a number of clearly marked headings which are also listed at the beginning of the book.

Additionally, the book is practical and gets you started on your way with your own IDE.  This means that he helps you set up your computer so you can make your own programs without needing an artificial experience like CodeAcademy or other self-training sites.  It's not complicated or crazy he just helps you get set up in around 1-2 pages.  This was a delight for me after CodeAcademy left me confused.  Now, I have Ruby, a nice text editor, and a directory full of programs!  He also has guides here for Windows, Mac, and UNIX users.

Next, I really enjoyed Pine's answer key (which you will use a lot).  In the back he has a couple of different solutions to his devious exercises spread throughout the book.  I enjoyed that he gave the alternative solutions even if many of them were way over my head.  While I wish the programs would have been notated a little more heavily, these were still really useful.

Finally, the book challenges you.  In the era of "complete this line of code" or "add an equal sign", Pine is having none of it.  He regularly challenges you and the challenges are always write your own program.  Even if I was almost universally a failure at writing my own programs, just trying and thinking the process through make you much better much more quickly than if you stick to CodeAcademy.  Unsurprisingly, the other side of the coin is that these challenges can be brutal and bring you to the cusp of 'to hell with this'.

Room for Improvement
Some of this stuff is borderline impossible for a new person.  Many (most?) of the challenges will frustrate you to the point where you don't want to go any further.  I ended up just looking at some of the answers and continuing to read on.  If you are the type of person who will view yourself as a failure if you don't get all of the answers yourself perfectly than this is going to be a tough slog.  These challenges are hard, particularly if you are brand new,

Next, Chapters 9-14 are rough.  I read them and took notes and I did learn from them, but somewhere around chapter 10 I pondered putting the book away permanently.  Do not do this!  Continue to read, but be aware that you will probably fall off your intellectual cliff at some point in this book.  I say continue on and come back to it later.  That said, this is really, really, demoralizing and probably could have been worked out with a little more "debugging" featuring newbie Rubyists.

In Final Analysis
Would I recommend it to a new coder?
Yes, but I would caution them about the cliff that comes in the chapter 9 range.

Will I sell the book, or keep it?
The book is really nice for reference.  I have already used it and will continue to use it for many of the simple syntax forms I am always forgetting.

Score out of 10 (because we all love this!)
7.5/10


On Perseverence

One of the things that's really hard for me to work through at times is being confused.  I don't like being confused and this is, in fact, the only thing that can prevent me from reaching my goal of being a competent coder.  Confusion leads to a loss of confidence which can inspire feelings like "this just isn't my thing", "I am no good at this".  As I read through more and more stories of people coding I have seen over and over again that being baffled is a natural part of learning to code.

In this spirit, I have continued on with Pine's Learning to Program and have nearly finished reading it and taking notes on it.  While I am not capable of doing all of the exercises, the book still has a great deal to teach me and I have learned quite a bit by reading and taking good notes even if it is not all clear to me.  Three weeks ago, I knew nothing, now I have a solid foundation in terminology and can write basic programs.


Total hours into Programming: 52 (5 yesterday)
My Text game: 2 hours, 107 lines
Chris Pine's Learn to Program (Finished with Chapter 12 of 14)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 546
Code Academy Badges: 58
Code Academy Skills Finished: 2 (Make a Website, Ruby)

Saturday, August 8, 2015

Chris Pine's Chapter 10: nope



I came to Chris Pine's Learning to Program because it was recommended on Josh Kemp's blog.  I felt since his programming background was similar to mine that this would be a good path to take.  On his most famous blog entry he suggests you take on this book in month 2.  Given that I had done everything in month 1, this seemed a good thing to start.  I read the Amazon reviews and while they were mostly promising, many people seemed to hit a wall around chapter 9-10.  In a moment of hubris, I dismissed these souls.

I should not have dismissed them.  While Pine remains his usual upbeat self after chapter 8, it feels very much like you got sick and missed a week of math class as the book ramps up to stuff that is really difficult.  Early on, Pine dwells on every detail about getting the length of a string.  Later on, he tells you to do activities which seem pretty much impossible for a person of my skill level.

While I do appreciate the challenges and looked at the answers as well as typed them in to my editor, this was just too tough.  So, I am going to finish reading the book, take from it what I can, and continue on my way.

Would I recommend this book to a total newcomer to code?  The first 8 chapters: absolutely!  After that: no way!  I do credit the book with helping me get familiar with setting up my environment and actually making me start coding in it.  However, looking at those chapter 9 and 10 challenges make me feel like a jackass so I will simply read through them instead of soaking my keyboard with salty tears as I fail to get anywhere close to any reasonable solution.

Total hours into Programming: 49 (2 so far today)
My Text game: 1 hour, 51 lines
Chris Pine's Learn to Program ("Finished with Chapter 11" of 14)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 535
Code Academy Badges: 57
Code Academy Skills Finished: 2 (Make a Website, Ruby)


Working on Many Fronts at Once

I am not totally sure this is the best course of action, but I find myself working on many different fronts at once.  Let me explain what I am doing and where I am at on each one and perhaps I can explain why I have done such a thing!

(1) Code Academy  -  I am working though Python mostly to prepare for the Computer Programming Course I am taking in the fall.  I also stubbornly refuse to give up on my daily streak which is now up to 16.  I continue to love Code Academy as an introductory tool, but feel that you will always have to go to different and varied sources to advance.

(2) Chris Pine's Learning to Program (Ruby)-  This is my priority.  I am trying to finish going through the book.  I am currently on chapter 10 (of 14) and am feeling pretty unsure about the content right now, but I will finish it up and revisit these ideas in different forms and resources when I finish the book.  I may also work through the book again when I finish at some point.

(3) My text game -  Because I have read over and over again that in order to make it stick you have to do it, I have begun work on my text game.  I am writing my own methods and creating my arrays and encountering my own problems.  The real problems you encounter when coding are so much more interesting and seem so much more practical than some of the designed exercises.  I have learned from Pine's book that sometimes you need to work out the solution "in English" before thinking in the program language and working on my game has helped me in this regard.  As I finish more of the game, I will post versions of it here, hopefully today or tomorrow!

Total hours into Programming: 47 (2 yesterday)
My Text game: 1 hour, 51 lines
Chris Pine's Learn to Program (Finished with Chapter 9 of 14)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 502
Code Academy Badges: 56
Code Academy Skills Finished: 2 (Make a Website, Ruby)

Friday, August 7, 2015

Battleship and Pine

Continued on today with Code Academy, well over halfway done with their Python course.  I am working now on the Battleship game they have you make.  Now that I have gotten about halfway through the tutorial, there is a lot of looking up of the problems in the forums.  I often find myself pasting the correct code next to mine and comparing to see where I went wrong or what I do not know.  There was a message posted to the local forums which expressed frustration at a similar situation.  If you always have to go to the forums in every lesson are you learning it yourself and will you realistically be able to replicate it?  I say, probably not which is why I love Code Academy as a starting point but not necessarily as an ending point.

Meanwhile, I continued on in Pine's Learn to Program with Ruby.  I have finished up to Chapter 9 and have to say that I continue to enjoy the explanations and hands on activities spread throughout this book.  I have managed to completed a couple of the challenges with no help and the rest of them I have done with some guidance from his answers in the back.  Whereas I used to totally freeze up when being asked to start writing my own code in response to a problem, Learning to Program has gotten me more comfortable writing my own code without the Code Academy scaffold.  I have also learned a great deal more about the details of the syntax because you just find yourself at the prompt running test programs all the time in this volume (which I like).

Total hours into Programming: 47 (3 yesterday)
Chris Pine's Learn to Program (Finished with Chapter 8 of 14)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 495
Code Academy Badges: 54
Code Academy Skills Finished: 2 (Make a Website, Ruby)

Wednesday, August 5, 2015

99% right == 100% wrong: Beginning Programming

So, one of the things that is so difficult about programming is that it is pretty unforgiving.  It is a detail oriented business and each letter, piece of punctuation, symbol, or variable must be noted exactly right.  99% in many cases means that you can more than get by, you have done a wonderful job!  1% wrong on most programs and it will not function.

In Pine's Learn to Program I have decided to actually type all of the answers into the editor for practice for this very reason.  Often times I have found myself sure I more or less understand what's going on, but when I do it myself it will not function.  This is the 99% rule in action.  Maybe you missed a colon, quote, or put one equal sign instead of 2 (my personal favorite!).  These mistakes make the program fail to run and can really test your sanity.  This afternoon I stared at my program and the one listed in Pine's book for 20 minutes sure he must have written the book wrong (even though I knew this could not be possible).  Finally, I found I left out one equal sign.  Hundreds of characters right, one wrong and kaput.

This is enough to drive the beginning programmer crazy because just when you think you've got it...you don't.  If you have had this experience know that at least one other person shares it with you.

Total hours into Programming: 46 (2 so far today)
Chris Pine's Learn to Program (Finished with Chapter 7)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 473
Code Academy Badges: 52
Code Academy Skills Finished: 2 (Make a Website, Ruby)

Pine's Learn to Program Chapters 1-5

Yesterday I got to work on Chris Pine's Learn to Program (foresaking Hartl's tutorial for now) and I really love it so far.  Best features:

(1) Helps get you set up with your own environment.
Pine helps you quickly and easily set up Ruby, Notepad++, and works you through the terminal.  I love this setup because I am actually writing programs and I have an open ended workspace on which I can practice.  This is one of the drawbacks to the infrastructure of Code Academy, you never get your own workspace and you rarely have an opportunity to practice outside of their lessons.  If you play around with the code, the lesson will always return a "right, move on!" or "wrong, try again" message which is annoying if you are trying to play with the code.

(2) Explanations!
If you have worked through any coding at all, these first chapters are going to go by really quickly unless you just decide to skip them.  However, I decided to read them closely and in doing so gained a deeper understanding of what was going on in the language.  Pine does not over explain or speak in too much jargon, but he does explain the underlying concepts which is so useful to the beginner.  Pine also has an upbeat and can do attitude throughout the book and it helps to disarm some of the anxiety of the beginning programmer.

(3) Excercises
This is the best part by far.  Pine integrates exercises into the chapters and has two answer sets at the end explaining both how you might do them based on what you know and how he might do them based on his experience and knowledge.  These exercises are real challenges and they have you writing programs throughout.  It gets you practicing in the editor and practicing running and double checking your programs as you go.  Some of these early exercises seemed simple, but presented me with a real challenge.  I feel like I have made so much more progress just in designing my own simple programs rather than being guided through more complex projects.

That said, I am only on chapter 6, and some of the reviews on Amazon speak to an issue where Pine begins to jump forward while failing to provide some of the explanation I just praised him for.  I will post a full review of the book when I finish it up, hopefully in a day or two.

Total hours into Programming: 46 (5 yesterday)
Chris Pine's Learn to Program (Finished with Chapter 5)
Progress on Hartl's Tutorial Ready to start Chapter 3! 
Code Academy Points: 461
Code Academy Badges: 51
Code Academy Skills Finished: 2 (Make a Website, Ruby)