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

if I have no experience in coding is team tree house really able to teach me everything I need so I can land a job?

I'm really new here and I'm just wondering weather I can really learn everything here or if I should save the money to take a bootcamp on programming? does anyone know of any cheap bootcamps that are online maybe in a virtual class room and that cost 2000 to 3000 dollars. and does anyone ever land a job just from team tree house alone?

6 Answers

I just started myself- however, even if you just tried it for 6 months, it would be way cheaper than a bootcamp. The way I see it you having nothing to lose. Even if you do decide you need more, you'll have a good foundation already if you do want to take a bootcamp type course.

Best of luck!

Hello Joseph,

Treehouse has been tremendous help for me to learn Front End Development. I invested a lot of time learning the technology Treehouse had to offer, and I also used many outside resources to deeply understand topics better. Realistically, it is possible to get a job after six months if you are devoted to your studies and are self motivated. Personally, I am not a big fan of bootcamps; I feel that I better off learning things by myself with so many resources they are.

David T. what other resources are you using besides tree house if I may ask? I want to learn as much as possible.

I don't think that Treehouse, nor any other option should be your only source of learning. Having been around the block with different online learning resources, and having made the mistake of spending thousands of dollars on a bootcamp, I'd suggest putting Treehouse at the center of your education for the next several months. But you'll want some other things, too.

The important part is that you commit to spending at least an hour a day on learning to code. You'll not pick up on all of this in three months (don't believe the bootcamps!!!), and maybe not even in six. It just takes time. But you can do it if you stick with it.

If I were to suggest a somewhat vague course of action to start a career involving code, it would be:

  • Treehouse:, at least an hour a day. Explore some different languages and then pick one to be your first language. Learn others later.
  • Always be reading a book relevant to code. I'd suggest starting with The Pragmatic Programmer.
  • Start applying whichever language you focus on with Treehouse to Exercises for Programmers, by Brian P. Hogan
  • Build something you are interested in. Learn as you go. Don't think in terms of needing to make it for others. Make it for you.
  • Look on meetup.com to see if there are meetups near you related to your language of choice. Attend, be nice, be humble, listen, and let people help you if they offer.

I think the best part of Treehouse is that it exposes you to completely new things in a very understandable way. It guides you through the process of building things with code and, over time, helps to build context. It will take you far, but you'll have to go farther. And I'm sure Treehouse staff would tell you the same.

So take what you are learning from here and apply it elsewhere.

Good luck!

I have a simple question for Champ.

When you say to Joseph he has to spend, at least, an hour a day on Treehouse. How do you organise your time? Do you have maybe advices to him?

For example, when I learn PHP and follow the PHP tracks, I'm always afraid to go to fast and miss something. So what do you suggest ? To fill the track, answer the quiz and the code challenges and go on as long as you understand and you have time (so during this one hour) OR even if you understand, take a break during the course, try something on your own and then go back to the track?

I'm really sorry if I am not clear enough :/. (I think I ask me too many questions ^^). Thanks for the books, I'll definitely take a look on them :).

Remember, these are just my opinions and suggestion. Mainly just trying to help encourage people to set achievable goals, and stick to it. Because I believe in us!

I pay attention as best I can, but I've gotten comfortable with the fact that I am incapable of absorbing all of the info on the first pass.

I pay attention to whether I'm able to concentrate. When it's time to take a break, I take a break. That could happen at any time. I just try to use one hour as a minimum time spent learning. That's easier after a day spent doing more mundane tasks. Sometimes I can power through and hit two hours.

One hour is just a suggested goal, not a rule. But think about it, a minimum of one hour a day for thirty days is thirty hours in a month. Now think about that. If you do that as a bare minimum for six months, then you've done one hundred eighty hours. Now add in the days that you have some extra gumption to do two hours. Or a weekend where you put in three or four. That starts to add up.

Also, don't treat what you're doing on Treehouse like a game of memorization. You'll not be able to remember it all. The important part is that you build some context to allow your brain to make connections between concepts. Because beyond learning the syntax of whatever language you are learning, you're also learning a new way to think, a way to solve problems programmatically. It's like a muscle, it takes regular exercise. That's why I think doing a little a day is more important and effective than cramming the same amount of time into a weekend. You'll build more muscle by doing an hour of exercise a day [with rest between] for thirty days than trying to cram thirty hours of exercise into a few days.

Don't forget to use the things you are doing on Treehouse on your own projects and do some deliberate practice writing programs. That's why I suggest that book, Exercises for Programmers. Prime the pump and build context with Treehouse. Then practice that stuff, using documentation as much as possible to figure out syntax. But feel free to revisit a past course from Treehouse. I've done that many times.

Cheers!

Here's my .0002 cents worth : : )

I've been doing Treehouse for the last few months. I actually started last fall, did about a week or two of intense 40 hours a week. Then, realized at the end of it that I was doing too much, too quickly. I stopped for a few months, and contemplated the whole thing.

Since January, I've been doing Treehouse and a couple of months of Codecademy. I'm a visual learner so Treehouse resonates with me more. But, having said that, Codecademy has online Advisors that can answer your questions pretty much immediately when you are working on Projects, or course work. That is pretty helpful.

But, what has truly helped more than anything else has been applying the "Sandbox" approach. Whatever you are working on put it in Codepen.io and have fun with it! Explore it, investigate, create variations, see how far you can take it. Then, take a break. I try to do 25 minute intervals of working with new material. Take a 5 minute break, then go back for more. This prevents me from getting in the deep end only to find out that I have not retained the information well enough, or as well as I thought at the time.

The other thing that has helped me tremendously has been to work on my own Projects outside of the courses, applying and getting used to "process", getting used to having to search for answers, getting used to being frustrated by things not working out, getting to used to getting stuck and being frustrated. There is a great deal of confidence that is built by simply creating your own stuff, and solving your own problems.

I am constantly searching Youtube and the Web for tutorials and examples. One of my favorites = DevTips. Travis is a cool dude, and very good at explaining what he is doing as he does it. And, he's hilarious. There are many others, too.

Another HUGE help has been looking at other websites using Chrome Developer tools. I'm a musician, and the way you learn music is by learning other people's music first, then make your own. I take this approach with coding, which is fascinating to me. So, everyday....I am analyzing other people's websites, looking at their code, and styles...seeing if I can spot things I am already familiar with, constantly deconstructing what I see. Then seeing if I can implement what I've seen into my own little projects. Application is key!

Another thing - Listen to Podcasts! Listen to people discuss this stuff....absorb the dialogue. It's just like learning a language...IT IS A LANGUAGE. You can't practice Spanish by silently repeating phrases in Spanish. You have to speak it aloud.

I am a newbie just like many others here. Check out GitHub, Codepen.io, Chrome Developer Tools and all the other great tools that exist. We're literally living in the most amazing time to be able to teach yourself anything and everything at the touch of a button. IT'S CRAZY!

For JavaScript, in case you're interested, The Missing Manual is a GREAT Book. So much stuff to have SO MUCH FUN with!

I hope this helps. At least it was cathartic for me. Ha.a.a..a.aaaa!! I know I feel better!

-jS

Chet, Thank you for your advice and encouragement. I completely agree that Treehouse is a great place to center your learning, but I also agree that it important to start expanding your resource library. I love checking out other's book suggestions. I'm a beginner, and my favorite book at the moment is Jon Duckett's HTML & CSS. It's slightly out of date (includes some HTML5 and CSS3, but the book went to print before those were fully operational), but it makes for a great reference when I want to look something up, but don't want to try to find it in past teachers notes.