I would say reliability is an important skill to develop. I suppose this falls under organization and communication skills too. It is easy to become flaky in this field with all of the emails, requirements, things to learn, and people to talk to. I'm not talking about being relied on to crank out code all day, but more so responding to emails that need your input, following up on things that you say you will, fixing issues reported to you on your work, be prepared to discuss something at a meeting, etc. while still handling the coding part of the job. If I know when I need something and that the person will actually respond, even if they say they cannot do what I am asking, is a wonderful thing.
I can agree with that, even in my current field of work as Director of Maintenance. Nothing more aggravating than when one of my guys tell me they fixed something or are getting ready to go fix it, only to find out in the meeting the next morning that it still isn't done. I don't know why they do it. I even tell them all the time that I WILL NOT get mad if they tell me they don't know how to do something and I would be more than happy to show them how. Yet still, it constantly happens.
This is my biggest struggle with some devs! Hah. The bug is fixed, then breaks again with the next deploy.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.