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!
Showing posts with label ruby on rails. Show all posts
Showing posts with label ruby on rails. Show all posts
Wednesday, September 2, 2015
Tuesday, September 1, 2015
Diving into SQLite DataBases with TreeHouse
A my previous posts indicate, my experience with TreeHouse has overall been very positive with the exception of the Rails example app course. Ultimately, I decided to simply watch the course and take the quizzes without a serious attempt at doing it myself. For reasons outlined before, I found the course pretty much impossible to do at my level. While this experience did have me second guessing myself a bit, I have decided to push through the Rails Track and then find another source for learning Rails foundations. The early leader is Daniel Kehoe's Rails for Beginners.
In the meantime, the TreeHouse courses seem to have reverted to their normal accessible selves. After Rails is a course on database fundamentals which I have been enjoying quite a bit. Previously I had to idea what "SQL" was and I am enjoying learning some basics about it. One of the things that's pretty overwhelming about learning to program is the sheer volume of information, languages, development tools, and directions you can go. You are always learning brand new things and always approaching something totally cold. I love it, but it can get overwhelming at times. Currently, I am feeling the full weight of that. Learning new things gets tougher as you get older, I think. I am only 36, but it feels like there is always a voice in the back of your head saying :forget about this, you can't do it!", especially after the last course. That said, I am pressing on, I will figure this out!
Code Report!
Resources in Progress:
Total hours into Programming: 104 (4 since last time )
Days into Programming/Hours per day: 2.7 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 (2806 Points, 34 Badges)
Code Academy Points: (745 points, 77 badges)
In the meantime, the TreeHouse courses seem to have reverted to their normal accessible selves. After Rails is a course on database fundamentals which I have been enjoying quite a bit. Previously I had to idea what "SQL" was and I am enjoying learning some basics about it. One of the things that's pretty overwhelming about learning to program is the sheer volume of information, languages, development tools, and directions you can go. You are always learning brand new things and always approaching something totally cold. I love it, but it can get overwhelming at times. Currently, I am feeling the full weight of that. Learning new things gets tougher as you get older, I think. I am only 36, but it feels like there is always a voice in the back of your head saying :forget about this, you can't do it!", especially after the last course. That said, I am pressing on, I will figure this out!
Code Report!
Resources in Progress:
Total hours into Programming: 104 (4 since last time )
Days into Programming/Hours per day: 2.7 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 (2806 Points, 34 Badges)
Code Academy Points: (745 points, 77 badges)
Progress on Hartl's Tutorial Ready to start Chapter 3!
Resources Finished:
Josh Kemp's No Degree, No Problem 8/14/2015
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 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
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
Monday, August 31, 2015
3 Ways to Improve TreeHouse's Rails "To do App" Course
I have spent many, many hours working through TreeHouse's Rails Track. I love TreeHouse. I have raved about TreeHouse on this very blog since I started it around three weeks ago. I like Seifer and enjoyed his Ruby basics course. I waded through many hours of TreeHouse to finally be able to work with Rails and I have been looking forward to it for weeks! I am about halfway through this course and it is really disappointing. I was initially thinking of writing a fairly negative review of the course and opening up on it. However, as an educator of well over 10 years myself, I understand that teaching people stuff is hard. Therefore, I decided to spin this and make it about improving the course instead of attacking it.
Before I start, let me say that I have about 100 hours into coding and am basically new to it. That said, I have finished the first three chapters of Hartl's work on Rails. So, if you are a little more advanced, this course might be a better fit for you than it was for me.
(1) Slow it down! When Seifer introduced us to Ruby, he was slow. Something has happened between then and now. He is now super fast. There is very little explanation in between the commands and some of them are performed too quickly to even keep up if you are simply typing as fast as you can! At times it feels like this tutorial is more about him making the "To Do" app rather than about teaching the students. Again, I am an educator. I know how grueling it can be to crawl through material you are very familiar with. That said, this is simply too fast and if students can't follow along they are going to quit on you.
(2) Divide it Up! In this tutorial, there is a lot going on. It could easily have been divided up into more sections with more context. In this course, he deals with gems such as capybara and rspec. I have divined through watching and doing that these are gems meant to help test your app as you go. We need more explanation about what they are! Where did they come from? Why are we doing this? Leading up to this, we took entire courses on the command line and on Git. Now new gems are thrown at us and if you are like me you don't have the faintest idea what they do or why we are utilizing them without reading between the lines in the course.
(3) Testing based development needs explanation! Throughout the process, you will develop an app, but more time will be spent programming tests to make sure your code works. You will probably make more tests than app before you get done. The tests are complex and very confusing and there is scarcely an introduction to the whole process. This is very frustrating for the newcomer. I read in the forums that testing based development is a good practice and eventually helps to develop more efficient and error free software.
I am sure that's true, but if you are new it's really clouding the issue. I teach college students history. There are countless "best practices" that I have to overlook in the name of teaching them on a basic level that they can grasp and do. Would it be nice if I could teach them the ins and outs of citations, historiography, and deep reading of primary materials starting on day 1? Yes! However, if I try to go into all of that in a 200 level course, nobody will get it and nobody will like history. In the name of trying to familiarize them with best practices and save time, everyone hates it and before long they won't be interested in anything I have to say! I think testing based development needs a lot more context here. Seifer never explains what it is and so we are left not sure what we are doing and most likely not doing it very well. Teach us to crawl before we walk!
At the end of the day, I still love TreeHouse and I think Seifer is a fine instructor. I just think some decisions were made that were not consistent with the rest of this course. In Ruby Basics, Seifer is slowly showing you how to make Ruby print text. 5 hours later, he reappears and is absolutely crushing you with fast moving Ruby on Rails lessons that are pretty demoralizing.
Before I start, let me say that I have about 100 hours into coding and am basically new to it. That said, I have finished the first three chapters of Hartl's work on Rails. So, if you are a little more advanced, this course might be a better fit for you than it was for me.
(1) Slow it down! When Seifer introduced us to Ruby, he was slow. Something has happened between then and now. He is now super fast. There is very little explanation in between the commands and some of them are performed too quickly to even keep up if you are simply typing as fast as you can! At times it feels like this tutorial is more about him making the "To Do" app rather than about teaching the students. Again, I am an educator. I know how grueling it can be to crawl through material you are very familiar with. That said, this is simply too fast and if students can't follow along they are going to quit on you.
(2) Divide it Up! In this tutorial, there is a lot going on. It could easily have been divided up into more sections with more context. In this course, he deals with gems such as capybara and rspec. I have divined through watching and doing that these are gems meant to help test your app as you go. We need more explanation about what they are! Where did they come from? Why are we doing this? Leading up to this, we took entire courses on the command line and on Git. Now new gems are thrown at us and if you are like me you don't have the faintest idea what they do or why we are utilizing them without reading between the lines in the course.
(3) Testing based development needs explanation! Throughout the process, you will develop an app, but more time will be spent programming tests to make sure your code works. You will probably make more tests than app before you get done. The tests are complex and very confusing and there is scarcely an introduction to the whole process. This is very frustrating for the newcomer. I read in the forums that testing based development is a good practice and eventually helps to develop more efficient and error free software.
I am sure that's true, but if you are new it's really clouding the issue. I teach college students history. There are countless "best practices" that I have to overlook in the name of teaching them on a basic level that they can grasp and do. Would it be nice if I could teach them the ins and outs of citations, historiography, and deep reading of primary materials starting on day 1? Yes! However, if I try to go into all of that in a 200 level course, nobody will get it and nobody will like history. In the name of trying to familiarize them with best practices and save time, everyone hates it and before long they won't be interested in anything I have to say! I think testing based development needs a lot more context here. Seifer never explains what it is and so we are left not sure what we are doing and most likely not doing it very well. Teach us to crawl before we walk!
At the end of the day, I still love TreeHouse and I think Seifer is a fine instructor. I just think some decisions were made that were not consistent with the rest of this course. In Ruby Basics, Seifer is slowly showing you how to make Ruby print text. 5 hours later, he reappears and is absolutely crushing you with fast moving Ruby on Rails lessons that are pretty demoralizing.
Sunday, August 30, 2015
Curves on the Rails
I finally finished a lot of the basic context in my TreeHouse Ruby on Rails track. I learned about Git, Ruby Basics, the command line, and a host of other basic skills. These skills were all explained in perfect detail and offered way more hand holding than was needed.
Then I started the Build a to do list application with Jason Seifer. If you have read my previous review of Seifer's Ruby Basics class you know that in that one he moved slowly and spoke in clear terms. In that course, it seemed almost to be a little bit too slow. In this one, Seifer is racing through making this application. There is an initial explanation of the directories that "rails new" makes and then we are off to the races. For someone with little to no experience this is kind of silly. While there is some loose theoretical explanation, mot of it is really brief or totally absent. There are also a host of version problems with the tutorial which I had to battle with uninstalling the newest Ruby and working backward to what Seifer uses.
I am wondering how this could happen. TreeHouse, to this point, has been very clear and if you are paying attention you can learn. This is why I was happy to plunk down $25 for it this month, it was a service that was excellently done and I have been exceedingly satisfied until this course. This one harkens back to CodeAcademy in that you are just kind of dumped into the middle of it with very little explanation. I am writing this blog entry now from a decisive point in the road. I am 9 videos in and am pondering if it is worth finishing. I am not getting much out of it outside of some practice copying code into the editor.
That said, I think sometimes you just have to trust in the process. I am going to finish the chapter and get it done. Perhaps I am learning more than it appears! Signing off.
Code Report!
Resources in Progress:
Total hours into Programming: 100 (2 since last time )
Days into Programming/Hours per day: 2.8 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 (2581 Points, 32 Badges)
Code Academy Points: (743 points, 76 badges)
Code Report!
Resources in Progress:
Total hours into Programming: 100 (2 since last time )
Days into Programming/Hours per day: 2.8 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 (2581 Points, 32 Badges)
Code Academy Points: (743 points, 76 badges)
Progress on Hartl's Tutorial Ready to start Chapter 3!
Resources Finished:
Josh Kemp's No Degree, No Problem 8/14/2015
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 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
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
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.
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.
Monday, August 3, 2015
Toy_app Done!
I finished chapter 2 of Hartl's book which is a great feeling! Everything worked and I even had the chance to correct a few mistakes. I also learned from a few different Stack Overflow questions and am really beginning to feel like I could perhaps do this unguided one day. Whereas I was feeling pretty defeated a couple days ago, making slow and steady progress through the Ruby on Rails tutorial book has been rewarding.
That said, chapter 3 is really where it begins. The earlier chapters essentially say that you will not pick much up in terms of deep understanding jut by doing them, but they do give you some momentum. I am also getting more and more comfortable with git, bitbucket, and heroku. I even got my app to display and work on an actual browser!
Python has gotten a little more sticky, but I have made it to around 40% through that Code Academy tutorial. I have gotten to the dictionary portion of the tutorials and am trying to work through how to print the key with the values from two separate dictionaries in one output.
I also notices that I have made it over 40 hours on this journey so far. Going from no knowledge at all to a decent foundation in basics in Ruby and Python as well as a solid foundation in Ruby on Rails is a pretty good start. While I love the idea of working as a programmer, coder, or developer I am not relentlessly and desperately pushing for that at this point. First things first, I want to be literate enough to code some of my own small programs.
Total hours into Programming: 41 (6 today)
Progress on Hartl's Tutorial Ready to start Chapter 3!
Code Academy Points: 447
Code Academy Badges: 50
Code Academy Skills Finished: 2 (Make a Website, Ruby)
That said, chapter 3 is really where it begins. The earlier chapters essentially say that you will not pick much up in terms of deep understanding jut by doing them, but they do give you some momentum. I am also getting more and more comfortable with git, bitbucket, and heroku. I even got my app to display and work on an actual browser!
Python has gotten a little more sticky, but I have made it to around 40% through that Code Academy tutorial. I have gotten to the dictionary portion of the tutorials and am trying to work through how to print the key with the values from two separate dictionaries in one output.
I also notices that I have made it over 40 hours on this journey so far. Going from no knowledge at all to a decent foundation in basics in Ruby and Python as well as a solid foundation in Ruby on Rails is a pretty good start. While I love the idea of working as a programmer, coder, or developer I am not relentlessly and desperately pushing for that at this point. First things first, I want to be literate enough to code some of my own small programs.
Total hours into Programming: 41 (6 today)
Progress on Hartl's Tutorial Ready to start Chapter 3!
Code Academy Points: 447
Code Academy Badges: 50
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Back to Rails
Last night I redid the early part of the Hartl Ruby on Rails tutorial and I managed to get it work correctly this time. I am still working very slowly through it, but I am trying to take solid notes and get a grasp for what is going on underneath the scaffolding features of rails. While scaffolding provides a real time saver and gets an app off the ground very quickly, it can be very confusing if you have never done such a thing before. On the plus side Hartl does an amazing job of explaining in both diagrams and text what is happening when a person visits your app and how controllers, routes, and applications work together to store their information and display the correct HTML. I am cautiously optimistic going forward!
Total hours into Programming: 39 (4 today)
Progress on Hartl's Tutorial 2.2.2
Code Academy Points: 440
Code Academy Badges: 50
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Total hours into Programming: 39 (4 today)
Progress on Hartl's Tutorial 2.2.2
Code Academy Points: 440
Code Academy Badges: 50
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Sunday, August 2, 2015
Learning How to Start Over
Last night I got on a roll in Hartl's Ruby on Rails Tutorial. Everything seemed to be going very smoothly (outside of Heroku issues). I fairly quickly generated the app and the database needed for the toy_app. Then, sadly, things went awry. My database was supposed to include two prompts, one for username and one for email. However, it included 4 - one for email, one for string, one for username, and another for string. I must have mistyped or misunderstood something along the way. I tried to overwrite the database using the --force command I discovered on Stack Overflow. I could not get this to work. So, finally, I learned how to delete the app, its git repository, and delete it from Heroku. While this was not the most desired outcome, I did learn a new skill of sorts. Now, to start again!
Total hours into Programming: 35 (5 today)
Progress on Hartl's Tutorial 2.0.0 (got the 2.2.1, but am starting this section over)
Code Academy Points: 403
Code Academy Badges: 47
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Total hours into Programming: 35 (5 today)
Progress on Hartl's Tutorial 2.0.0 (got the 2.2.1, but am starting this section over)
Code Academy Points: 403
Code Academy Badges: 47
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Saturday, August 1, 2015
Python and Rails
Today I worked with Python in the early section of the Code Academy site. I am finding that to be a kind of review of what I did in Ruby and it is satisfying to understand much of it without having to grip my skull in agony. I have a solid grasp on if, or, not, else, elif, else, equal, less than, greater, than and most of the basics (sometimes called Control flow). I am hard at work forming an app that converts words into Pig Latin which is a real challenge since Pig Latin on its own is more confusing to me than it should be.
I also completed Hartl's Chapter 1. In the intro there is a introductory paragraph singing the tutorial's praises by some brave soul that completed this whole tutorial in 3 days. I can't imagine anyone who really needs this training completing this in 3 days. So far, I have completed an app that only displays one line to the world and in that process I have been introduced to a host of programs/websites that I had no clue existed before, memorized a basic directory structure for Rails apps, gotten basic training and a definition of version control, and deployed the app to Heroku (without success, see below).
Good news, everything went slow, but great. Bad news, my stupid app does not run on Heroku like I desperately wanted it to. Just as I was about to paste my app's test web address into an email and send it my wife (to demonstrate that I have indeed learned something!) , it failed to work. I followed up on a few of the Heroku error messages such as putting a Ruby version in the gemfile, but my meager store of knowledge is not yet strong enough to troubleshoot deploying an app. So, this was kind of bittersweet. I completed the chapter and the exercises and feel really good, but I was robbed of my small moment of glory! That said, I remain undeterred and will start the "Toy App" tomorrow in chapter 2.
Total hours into Programming: 33 (3 today)
Progress on Hartl's Tutorial 2.0.0
Code Academy Points: 393
Code Academy Badges: 45
Code Academy Skills Finished: 2 (Make a Website, Ruby)
I also completed Hartl's Chapter 1. In the intro there is a introductory paragraph singing the tutorial's praises by some brave soul that completed this whole tutorial in 3 days. I can't imagine anyone who really needs this training completing this in 3 days. So far, I have completed an app that only displays one line to the world and in that process I have been introduced to a host of programs/websites that I had no clue existed before, memorized a basic directory structure for Rails apps, gotten basic training and a definition of version control, and deployed the app to Heroku (without success, see below).
Good news, everything went slow, but great. Bad news, my stupid app does not run on Heroku like I desperately wanted it to. Just as I was about to paste my app's test web address into an email and send it my wife (to demonstrate that I have indeed learned something!) , it failed to work. I followed up on a few of the Heroku error messages such as putting a Ruby version in the gemfile, but my meager store of knowledge is not yet strong enough to troubleshoot deploying an app. So, this was kind of bittersweet. I completed the chapter and the exercises and feel really good, but I was robbed of my small moment of glory! That said, I remain undeterred and will start the "Toy App" tomorrow in chapter 2.
Total hours into Programming: 33 (3 today)
Progress on Hartl's Tutorial 2.0.0
Code Academy Points: 393
Code Academy Badges: 45
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Friday, July 31, 2015
Ruby on Rails Tutorial: Day 1
After a very confusing intro to Ruby on Rails via Code Academy (where I somehow managed to "complete" 24% of the lesson), I was not feeling so confident about apps, Ruby on Rails, or much of anything really. Tonight, I started Michael Hartl's Ruby on Rails tutorial book which seems to be a real standard in learning the ropes of Rails. I spent about 2 hours with it so far and have completed 1-1.4.1. This doesn't seem like much and at the end of the day it is a very small chunk of the tutorial, but I am trying to take my time and really learn it.
So, how is it for the complete newb? I like it a lot, actually. I am actually working in an Integrated Development Environment, and it is really explaining in detail what is going on at every stage. I was introduced to Cloud 9, Git, and Bitbucket today and I have a pretty solid concept of what version control is and why programmers do it. Hartl does a nice job of explaining what is pertinent to the new coder without speaking a different language I would never understand. I was also really happy to recognize some of the formats I had learned from the Ruby Code Academy tutorial and understood what was going on when instructed to place a method within the controller. I also now have a clue what a gem is and understand what is happening on some basic level when rails designs the framework for your new app. So far, I really love it!
I also worked through a few lessons on Python this morning which were much easier and faster than my early Ruby lessons. I am enjoying the learning process and have actually had a few moments today where I knew what to do without making many, many mistakes and having to scratch my head in frustration. Good day!
Total hours into Programming: 30 (4 today)
Progress on Hartl's Tutorial 1.4.1
Code Academy Points: 368
Code Academy Badges: 43
Code Academy Skills Finished: 2 (Make a Website, Ruby)
So, how is it for the complete newb? I like it a lot, actually. I am actually working in an Integrated Development Environment, and it is really explaining in detail what is going on at every stage. I was introduced to Cloud 9, Git, and Bitbucket today and I have a pretty solid concept of what version control is and why programmers do it. Hartl does a nice job of explaining what is pertinent to the new coder without speaking a different language I would never understand. I was also really happy to recognize some of the formats I had learned from the Ruby Code Academy tutorial and understood what was going on when instructed to place a method within the controller. I also now have a clue what a gem is and understand what is happening on some basic level when rails designs the framework for your new app. So far, I really love it!
I also worked through a few lessons on Python this morning which were much easier and faster than my early Ruby lessons. I am enjoying the learning process and have actually had a few moments today where I knew what to do without making many, many mistakes and having to scratch my head in frustration. Good day!
Total hours into Programming: 30 (4 today)
Progress on Hartl's Tutorial 1.4.1
Code Academy Points: 368
Code Academy Badges: 43
Code Academy Skills Finished: 2 (Make a Website, Ruby)
Subscribe to:
Posts (Atom)