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

Learning Ruby Track

Is it me or is the track shelling out points for not really achieving anything? Also, are the code challenges broken because they seem pretty easy to complete :/

1 Answer

Code challenges are just there to make sure you were paying attention to what was said in the videos. Not achieving anything? Well that depends on you - were you just watching videos, or were you actually trying to write a similar app and doing your best to understand the topic by reaching out to other sources (like official documentation) and experimenting on your own?

The entire reason for doing this track is to gain an understanding of how websites interact with users. I've done my fair share of coding in Python, JavaScript and PHP so I'm comfortable with the concepts that seem to be analogous to every tutorial teaching the basics of a coding language. I've been 'watching' the videos if only to reassure myself that I understands the concept and learn the syntax. (As you probably know PHP, JavaScript , Python and apparently Ruby all have similar derivations. I haven't progressed far enough to see any appreciable differences other than syntax although I hope to do so in the near future.)

I'm a great believer of taking everything I can from one source before moving on to another, so in answer to your question; no, I haven't been 'reaching out to other sources' because I'd inevitably end up wasting hours attempting to decipher the formal code documentation. It's why I'm here after all...

Also, in terms of writing another app, I play around with code. I'm currently re-writing my website in-light of some of the things I've learnt here and hope to be adding more complicated and responsive code soon.

I've got my own high horse thanks :)

Also, this was only in reference to this particular part of the over all track.