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

General Discussion

Posted by James Biddle
James Biddle
3,853 Points

TORN!

Just finished the initial Build a Web site module, very cool how Treehouse is doing this, best ever.

Now I am torn about should I stay on Front-end or go straight to Ruby or PhP!

Any experiences or advice would be appreciated.

Thanks all!

3 Answers

Kevin Korte
Kevin Korte
28,149 Points
Kevin Korte
Kevin Korte
28,149 Points

Why not both?

James Biddle
James Biddle
3,853 Points

That would be "Full Stack" I take it?

Kevin Korte
Kevin Korte
28,149 Points
Kevin Korte
Kevin Korte
28,149 Points

Yeah, but even if you want to "focus" on one or the other, I think it's important for the right hand to know what the left is doing. I'll be honest, I'm more of a creative guy. I like UX, I like UI. However, I'm addicted to the logical problem solving of the back end stuff.

If I had to pick one, I'd rather stay front end. but knowing as much as I do about PHP and Ruby has already been proven invaluable to me, and I'm sure to an employer too.

Also, I go through spurts. I swing back and forth between learning front end and back end stuff. I tend to grow tired of one, so I move over to the other to learn a bit, and rinse and repeat.

James Biddle
James Biddle
3,853 Points

That's where I am at now mentally; CSS seems like it may drive me nuts, but stuff like jscript seems intriguing and I would like to learn how to implement that sort of thing if needed. On the other side I am torn between php and rails. More php jobs, but rails is apparently where "its" goes. I read an article yesterday comparing them, think I may just stick with PHP.

Thanks for your comments!

Kevin Korte
Kevin Korte
28,149 Points

I'll clarify, I do agree with Jim. I would pick a track and start. As you advance, your interest might change. When it comes down to php vs rails, once you learn one, I feel it's easier to learn the other. Because you don't know, just start with your gut and go from there. I started in PHP, and have just now moved over to learning Rails.

It's overwhelming for sure. But be ready for a life long of learning, and don't be afraid to go on both sides.

Jim Withington
Jim Withington
12,025 Points
Jim Withington
Jim Withington
12,025 Points

I think it's good to pick a track and dive in. The tracks are structured to give you a pretty holistic view, and sticking to one is a great idea. If you pick and choose you won't get the base for things in the same way as you would have if you pick a track and go through it.

That said, you could go Front End, or Ruby, or whatever! But I'm fully pro-track. :grinning: