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
Tom Ellis
3,372 PointsDoes the Web Dev Learning Adventure Go into More Detail?
I'm just going through the web developer LA and have a question regarding its depth.
I come from a pretty solid HTML/CSS/JS background, but have never learned any back-end languages so I was hoping to 'learn' Rails from the Treehouse course.
I'm studying Ruby alongside it to get a good handle on that side of things, but I'm concerned I'm not really learning Rails as much as I am just building what Jason/Jim built using scaffolds.
Don't get me wrong, Jason and Jim are great teachers, and they do explain what they are doing very well, but I'd like to learn more about how to do it 'from-scratch' rather than with scaffolds.
Does the course get more in-depth in the later stages? I feel like at this stage, all I could really do with Rails is rebuild the exact same thing, again, using scaffolds as oppose to building something of my own.
Thanks
6 Answers
Chad Shores
Courses Plus Student 8,868 PointsScaffolds are what many developers start with when fleshing out a Rails app. You can remove these later, and most do.
Don't spend too much time over-thinking certain aspects. Just get through the course and see what you know on the other side.
Tom Ellis
3,372 PointsThanks, Charles.
That's what concerns me though, you say that most devs remove the bits they don't need later, but I don't even know which 'bits' get added, or indeed what a scaffold really does.
I'll certainly see the course through, I just hope it'll position me better for building some of the projects I have in mind.
Chad Shores
Courses Plus Student 8,868 PointsNot super important at this very second, the universe always has a way of giving us the information we need at the time :)
You can do it!!!
Tom Ellis
3,372 PointsGood call Charles, thanks!
Philipp Antar
7,216 PointsI learned a lot by not using scaffolds. I may be not in the position to give this kind of advice, but here's how I learned how a Rails app basically works:
First generate a brand new app. Then, before you do anything else, write an integration test, that tries to get to a certain path (e.g. posts/index). Run the test – it will fail, but it will also give you message saying how it failed. Probaly something along the lines of "no route 'posts/index'"). So you go to config/routes.rb and add the route. Run the test again and chances are it will complain about a missing controller, then a missing template.
By going through this process step by step you'll learn about how the a browser request is processed by the MVC architecture, whilst practicing TDD. A good motto of TDD to keep in mind is to write tests for the code you wish you had. :)
I don't know if this makes any sense… just some advice from student to student :)
Tom Ellis
3,372 PointsThat's awesome, thanks Philipp.
Fortunately, I did a little bit of the Michael Hartl book so I can see the power of TDD, I'll certainly have a go at the method you've suggested.
I've actually found the biggest learning experiences have come from fixing things when they go wrong, and having come from a frontend background, one thing I've noticed is there is a LOT that can go wrong with even the most subtle change!