Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Ruby Build a Todo List Application with Rails 4 Build a Todo List Application with Rails 4 Cleaning Up Our Code

Make your website half decent so your users can learn something.

Firstly, you make it awkward for people with little experience by forcing people to learn html and javascript. Secondly, Jason Seinfer or whatever his name is, never explains anything about what he's doing. For example: partials are typically named beginning with an underscore but despite this, can be called without the underscore. Does he explain this? Hell, no. Also, try actually explaining everything your doing instead of your users wondering what the fk you're doing. This capybara gem looks useless. What is it even achieving for you? Why not just code Ruby On Rails properly? Go to Lynda.com and remake your series instead of wasting everyone's time.

To all people who are confused by this series, switch to Lynda.com. And if they were paying me, I wouldn't be swearing.

Ross Litzenberger
Ross Litzenberger
11,706 Points

Hello jason blesing, I would encourage you to start learning html, css and javascript before digging into a dynamic website. Once you understand the basic. I would encourage you to checkout emmet , sass and coffeescript. Once that is completed, you are ready to apply that to a rails application. Treehouse has given me the foundation that I needed to understand ruby on rails framework. I have completed my rails course a while back now but, that has not stop me from learning more about rails. Thanks for the resource i will check them out. I would encourage you to dig into the documentation of capybara gem. If you want to be a great developer you need to be will to dive into new things each day.

Dude, I already know all that stuff. I just don't like the syntax in this rails app because it's way too much for just a tiny bit. You could just hard code it easily using rails(without gems). There are way better helper gems out there to build stuff more efficiently(scaffolding). By the way, in Lynda, be prepared for masses of copying down. Otherwise, the explaining is much better.

Ross Litzenberger
Ross Litzenberger
11,706 Points

Cool All right which lesson in lynda did you do or are doing?

Sorry dude for not being on for a while. It's called Ruby on Rails 4 essential training - by kevin skoglund.

Ross Litzenberger
Ross Litzenberger
11,706 Points

Thanks , Question off topic, Want to learn about connecting hardware to a web app? Jason do you have any resources that you have come across talking about how to use them?

Sorry, got no idea what you're talking about. You're asking me if I know resources for you to learn, right? Sorry, I don't. By the way, are you experienced in rails? On the lynda.com course, I'm having trouble making pages(I'm not using sections) editable and deletable only to the AdminUsers that made it. Don't worry if you can't help me in an instant(snort snort Get it? Like... and instance... variable snort snortnerd laugh)

1 Answer

I completed this ODOT tutorial today. It's a beast, took me a few days.

AND I LEARNED VERY LITTLE.

It seems to me that the tutorial has been put together quite hurriedly, and getting the app finished seems to have been made a priority, rather than helping the student learn how to build an app.

There's a HELL of a lot of ground covered in this tutorial - too much for one badge. I think it needs to be completely redone.

THere is very little explanation, which sits in opposition to the decision to hand code everything instead of using a few automated processes. If you're going to take that path, you need to back it up with explanations. To understand what's going on in this tutorial, A LOT more explanation is required.

Once I got to halfway I decided to hack my way to the end, just so I had an app to modify and practice pushing to heroku etc.

I watched all the videos and followed along, but now I'm thinking I might have been better off just copy/pasting the code from the project files and not even bothering to watch the videos - the idea being that I could have spent the last day and a half of my time on something more worthwhile, actually learning something.

Sorry to be harsh, Jason, but this tutorial was way off the mark and very disappointing.

As a general comment about all of the Ruby tutorials on this site, I think they need to be sloowwwed down A LOT.