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
Dan Arata
9,253 PointsDo employers like just code? Or more?
I know that after finishing the Treehouse courses we'll have to take what we've learned and practice them further by applying them to projects.
But my question is this. When presenting your work to an employer, is it okay to just show them the code and that it works out of things such as alert() and document.write() as we did in this course? As opposed to having a fully market ready application with a GUI?
Thank you in advance
3 Answers
Justin Black
24,793 PointsAs an employer, I'll answer this for you.
What an employer looks for varies based on the job they are looking to fill and the level of knowledge they are looking for. For this course ( JavaScript ), after finishing it I would personally consider you "pre enty-level". Which basically means, you know the basics but definitely aren't ready to be in the job market just yet.
So, what exactly do I look for? If I am looking for an entry level person, I still want to see their code -- specifically to see if they are current and concerned with best practices in their own things. It doesn't have to be 'ready for market' material, but shouldn't be something super simple as what we've ran across here in these videos. For javascript developers, the best code samples I get take a look at some real world problems that exist in web development ( even if there are libraries that achieve the result ), and bring an interesting new approach to solving the problem.
If I am looking for an entry level developer, I don't care so much as to the full depth of your knowledge, more so the current level that you are, and your willingness to expand your knowledge. Now if I am looking for a mid-level developer, you should have a solid understanding of the principals for the language(s) you use. For instance, a mid-level developer should be able to list and explain the OOP Methodologies ( Encapsulation, Polymorphism, Inheritence, etc.. ). A senior level, should really know the ins and outs of the language(s) they use. For senior level developers I hire, I often give them a piece of paper riddled with bugs and see if they can pick them out and explain how to properly fix them.
Being here, you will be entry level soon enough. So don't worry so much about the depth of your knowledge, just continue to learn and when you do start applying for jobs be sure to put in your CV where you started learning, and what you use to continue to enhance your knowledge ( I'm a senior level developer in many languages and I still do this in my CV ). Most companies that are looking for entry-level, are more than happy to pair you with a mid-level or senior-level dev to expand your knowledge. In fact many companies prefer hiring entry-level as opposed to mid-level or senior level for one reason: Entry level developers are still moldable, if you have picked up any bad practices it's easier to help you correct them as an entry level developer as opposed to mid-level or senior level developers that are cocky as hell ( usually ) and stuck in their ways.
Matt F.
9,518 PointsI think that this video would help you: https://www.youtube.com/watch?v=zXqs6X0lzKI
I would say that you should not wait until after finishing all of the courses to apply them in personal projects. Start doing it now.
Matt F.
9,518 PointsThe video I referenced above was updated for 2015: https://www.youtube.com/watch?v=pB0WvcxTbCA
Dan Arata
9,253 PointsThank you. That really helps
Tyler Hogstrom
2,705 PointsTyler Hogstrom
2,705 PointsThanks so much for this feedback on the difference between 'pre entry-level' vs 'entry-level' development standards, it really gives me some good insight.
As to your last paragraph about including continuing knowledge on your CV, can you provide an idea of the format you use for this section? Thanks!
Justin Black
24,793 PointsJustin Black
24,793 PointsTyler, I've tried many approaches when it comes to my CV. I've done basic approaches as well as highly detailed approaches. What I've found over the last 20 years in the industry, and over the last 2 years as a hiring manager. Is that super basic just doesn't cut it. But being super detailed leaves nothing to be questioned. A nice middle ground is paramount, as it leaves the perspective employer with enough questions that they feel they HAVE to bring you in to discuss them with you.
At this point, all I have is a basic education point for "self study" from 1995-present and I am always prepared to elaborate upon that in an interview. With the right CV/Resume you can get high returns on your job search. Keep in mind that the CV isn't the only thing you need to be concerned with when applying for positions ( in any industry ). You also have the cover letter, which should be a short 2-3 paragraph explaining the basics of who you are, what you excel in and why they should choose to schedule an interview with you. Cover letter should also be tailored per job ad ( doing your research can come in handy, such as who the email is going to so you can identify them personally. the job title you are applying for, and tailor the letter to key activities for the job you are applying for )...
An older version of my CV/Resume can be found at: https://drive.google.com/open?id=0B3QVbPFDgkgKLTRYeTNJLXN1cl9UbHRSOXhnclg4MWFIRXpv&authuser=0 keep in mind that this is still the same resume I use, though the information contained is a little outdated ( and in some cases the dates are completely wrong )