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
Sage Elliott
30,003 PointsComplete projects | Career program
Hello every one!
If you've made any projects for the treehouse career program I'd love to hear what it was!
I've been holding back probably longer than I should have on creating/submitting anything because I feel like they should be polished and serve a purpose. I will likely be seeking a jr. rails developer job, so I feel like I should build up the apps using, TDD(with Rspec/Capybara), authentication(probably devise) and demonstrate knowledge thorough knowledge of Ruby, TDD, and a good understanding of rails(activerecord, migrations, etc...). I also think at least one should parse data from an API.
Any tips or Ideas on anything else I should include or specific apps you think employers would like to see?
Thank you :)
1 Answer
Tyrell Jentink
8,415 PointsI don't think they are looking for three complete websites as projects; IN the PHP Development track, for example, we made the Shirts4Mike page, and then we just kept doing more "projects" to add new functionality to it. The implication being, each time you add functionality, that's a new project.
SO, with my three projects, I first built a static version of my website (In HTML and CSS) and called it Project 1. Then I added dynamic data, and refactored my CSS, and called that Project 2. Then for Project 3, I refactored my PHP into the Model-View-Controller pattern, and added 3 more pages to my site. The real challenge is to write up each project with details on what you did, and what skills that proves competency in. Also, make sure the competencies all broadly apply to your track.
Finally, on the note of polish... You will NEVER be done with ANY given website; There will always be SOMETHING that can be further polished, or new functionality you would like to add, or some new content you think is important.... If you wait till everything is done, you will never publish. SO, define the scope of each project narrow enough as to be obtainable, and focus only on those tasks until they are complete. Publish it, then set new goals and a new project.
That's how it's gonna be in the Real World anyway, so you might as well set up these projects in a similar framework ;)
Sage Elliott
30,003 PointsThanks Tyrell Jentink ! Good point about the polishing never being done! :)
Tyrell Jentink
8,415 PointsNo problem :)
At risk of sounding like a point whore... Any chance of getting an upvote on my answer? ;)
Sage Elliott
30,003 PointsI don't think you can get point in general discussion topics so please accept a virtual high-five!
Tyrell Jentink
8,415 PointsHaha... Fair enough. I forgot there were rules to all of this... ::Sigh::
As much work as those projects were, just wait till you have to get 60 forum points. I put it off, and now I'm trying to rush through them.
Sage Elliott
30,003 PointsThere are always plenty of posts that need answering!
I still think I'll be building up 3 separate projects and documents them individually and include tests. I assume they will be going to potential employers to look at, and I feel like I'm not too far from that point of building those.
Sage Elliott
30,003 PointsSage Elliott
30,003 PointsOh and I will also be polishing the front end with SASS, since thats the norm for the rails community.