ÉnKép - takacsot

1. Time spent writing great code.  It is about the quantity, and the quality.
2. Interpretation of the problem. totally define the problem before doing anything! A great developer will want to understand it fully, before attempting to approach a solution.  Do you understand the problem 100%, no?  99%?  Go ask more questions and be sure you are 100% clear!
3. How the problem is approached. So once you have clearly defined the problem, you start coding right? Wrong!  A great developer will look at the layout, and start thinking of various options, and based on the problem, will start thinking about the best approach to solve the problem. Look at the problem, figure out what the outcome needs to be, what kind of time you have, the quality being expected, the tools you have to work with, etc.  Then, start solving the problem.
4. Confidence in code. As a manager, how confident can you be in their code.  Some developers you can say "I need this completed by Friday"  come Friday, you get an email saying "I have checked the code into the branch, it is ready for testing" and you  just know that there will be very little, if any, bugs found by the quality assurance team.  On the flip side, there are some developers that will email you instead and say "I am still not done, and it will be done on Monday morning first thing."  And you are nearly 95% sure that it will be there, however it will be ridden with bugs, and basically unusable for days, if not weeks, until bugs are completely ironed out of the code.  Bottom line: The higher the confidence you can have in a developer, the closer they get to being great developers!
   
5. Confidence in the solution.
6. Meets user requirements. 
7. Staying up to date. Great developers are constantly updating their skills independently and proactively!
8. Contributes to team.
9. Makes great meeting minutes. This is incredibly important!  There is nothing worse than calling a meeting, taking the time to explain new concepts, new ideas, brainstorm, come up with great designs, and not have anyone taking meeting minutes!  Even if you have a designated meeting taker, I want to see everyone showing up with a pen, and paper (developer notebook is preferred). A great developer takes great notes!  They write out all meeting minutes, and at the end of the meetings can be heard saying "So just to confirm, my action items are:  <action items here>.  Did I get everything?”  Next, a great developer will send their meeting minutes to the manger, listing the date of the meeting, the topic, and attendees.
10. Teachable and takes criticism well.
11. Always available when needed.
12. Dress's professionally every day.
13. Communication Ability
14. Goal Setting Skill.  A great developer has the goals for the year, the next five years, and knows roughly where he will be in 10 years. 
15. Organizational Skill. The final key component that really brings everything together is organization.  You may be the best developer in the world, but if you are not organized, you will fall apart and become bogged down!  Eventually you will be overwhelmed and start losing your edge.  Great developers keep an extremely clean desk, they keep all their notebooks, and write very clearly.  They print out their daily outlook calendar of meetings and tasks.  They have an inbox process to deal with emails, meetings, and new assignments.  They keep file folders and can instantly pull up projects, meeting minutes, and other details when asked to produce them.
16. Passion!   Without passion in what you do day to day, you will not be a great developer, or great at anything for that matter.

Original