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

Python Object-Oriented Python Instant Objects Your first method

Code challenge Class: Student, praise method. No idea what's up here. confusion is running rampant in my brain !!!

Can anyone let me know whats wrong with my code?

first_class.py
class Student:
    name = "Ted"

    def praise(self):
        return ("You're doing great, {}!".format(self.name))

1 Answer

Eric M
Eric M
11,545 Points

Hi Theodore,

This code will pass the challenge. Good work.

Unfortuantely there was a bug impacting some of the code challenges at the end of last week, which I think you ran into. Shouldn't be any issue if you give it a go with your posted code now.

Cheers,

Eric

Thank you, Eric.

Namaste, Ted

Eric M
Eric M
11,545 Points

No sweat, it was a very frustrating bug! Glad you're back at it now everything's working :)

Hey eric I have a person question for you, if thatโ€™s ok? How much have you had to learn to find work in development. Do you have any suggestions for course tracks if I want to find a job?

Eric M
Eric M
11,545 Points

Hi Theodore,

The short answer is: I've had to learn a lot and I learn more every week if not every day. I read books, I write side projects, I do courses on team treehouse as well as other sites, and I go to meet ups to talk to other developers.

Don't think of that as a list of things you have to do though, but also don't think of it as "if I do all of this I am guaranteed a job".

But, there is a simple answer, and one thing you absolutely must do: write code.

More specifically: complete entire coding projects, start to finish, at a professionally level.

What do I mean by a professional level? No bugs, no weird stuff going on with the UI, a pleasant straightforward experience the likes of which you would expect from any app you downloaded from the app store or any website you visited. Once you can do this, you'll be able to find someone to pay you to do it.

In fact, you can probably find someone to pay you sooner, but it (the job search) will be harder work. When looking for a job you have to be two things. You have to be good enough to get hired. You have to be better than every one else who applied. Then you get an offer.

Teamtreehouse is a great resource, but it's not going to make you a developer (probably an exception to this is the tech degree which requires you to do the sort of work I'm about to describe). It's going to set you up with the foundations to make yourself a developer. You need to take the skills these courses are teaching and apply them. Completing an entire track on a language is a great start. Most of the languages also have intermediate tracks for once you've finished the beginner ones. If you can complete those, then go back through the code challenges and knock them out, then this is a great start. From there I would look at doing some of your own projects. Try to keep the scope very, very small. I mean tiny. A good example would be a program to read in a text file, find all of the countries or cities mentioned in the file, and output them in a csv with the number of times they're mentioned against each country or city. After you've done a few of these you're sure to get an idea for a bigger project. Don't feel like it has to be something that hasn't been done before, or something that's commercially viable. All that's important is that you do it, start to finish, and make it easy to use (also ideally your code is well structured, conforms to conventions, and has test cases (Treehouse has some courses on unit testing if you don't know what this means)).

Also, once you do start doing bigger projects, don't feel like you need to know everything. It's okay to do a lot of googling! What's not okay is copying and pasting code you don't understand. If you get an answer from google, make sure you can understand it and rewrite it yourself. If you can't, study the functions within it until you do.

I know this probably seems like a lot. It kind of is. But learning to program, programming as a hobby, and being paid to write programs are all different things. At the end of the day this is a complex, technical, profession that takes a lot of work. The problem solving and creativity that it allows though makes it the most rewarding work I've ever done. I hope that you can get to that point too! But don't try to rush it, try to enjoy it and create things!

More importantly, enjoy learning it. I enjoy learning this stuff a lot, that's why I'm here! (a lot of what I learn through Team Treehouse I don't have an immediate application for at work, but it's fun)

Cheers,

Eric

Awesome insight and guidance. Thank you for replying, I really wanted to understand where to start.

Iโ€™ve always loved problem solving and honestly I thought I wasnโ€™t smart enough or creative enough to try this, I quit cooking as a sous chef because of the yelling and stress. Deciding to pursue this even though I wonโ€™t be getting a paycheck seemed daunting. However, happiness is more important than money and even though stress canโ€™t be dissolved I figured it would be healthier to try something new. So, since I started a few months ago I gained some confidence and Iโ€™m really diggin writing functions.

Start small is what Iโ€™m taking out of this but with every small step make it count and donโ€™t expect much right away career wise. I think I can do that. Thank you again for giving me your time. I really appreciate you.

Eric M
Eric M
11,545 Points

Start small and keep building is a great takeaway, and much more succinct than what I wrote!

Best of luck!