Coding skill vs. employee skill
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
Rodrigo wouldn't do well in a team environment, but it's hard to believe that Gabriella "hasn't missed a deadline." Delivering buggy code on time isn't my definition of "meeting the deadline". :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
Amazing thoughts. What seems to be the paradox is, you can do well without being a great coder. But to get inside [an organization] you need to have to be a great coder. No one's going to recruit you just because you talk good english and meet deadlines.
- Just that something can be done, doesn't mean it should be done. Respect developers and their efforts! Jk
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
Terrence Dorsey wrote:
You can get far without being a great coder.
I know! Been cleaning up behind them for ages.. What the man means with "being a good employee" does not add up with being a good coder. You're a good employee if you don't complain about the coffee and don't speak against the boss. You're a good coder if you tell the boss that VB6 is dead and that his new Skynet will NOT be developed using a dead language, unless all the documentation will be in Latin.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
so many mixed up "Project Management Skill", "Communication Skill" and "Teamwork" which covers everything from correct grammar to arse kissing (imagine all the other buzz words invented by the HR and management) Good coder = Good programming skill, PERIOD. That's the kind of people I looked for two years ago when I hired developers for our group
dev
-
Rodrigo wouldn't do well in a team environment, but it's hard to believe that Gabriella "hasn't missed a deadline." Delivering buggy code on time isn't my definition of "meeting the deadline". :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
I agree with you on this. But I've had many instances where management has said, "I don't care if it doesn't work, get it into production." Seen many instances where code that is not ready has been released because management is more concerned about meeting the deadline rather than the quality of the product.
-
At the extremely basic level, there are basically two good qualities that each programmer should strive for: programming skill and employee skill. Programming skill is basically the ability to write good, solid, performant, maintainable, and all-the-other-desireable-code-adjectives code. This is what coders tend to spend their time harping on and debating about and reading about. Employee skill is the ability to be a good employee and coworker. This means being responsive, being able to communicate well, hitting deadlines, being open to feedback, being able to explain complex things clearly, stuff like that.
You can get far without being a great coder.
Quote:
However, the point is that managers are the people you need to impress to get jobs and promotions and raises and pats on the back, so in this scenario, Gabriella comes out way ahead.
I don't see the issue here. Gabriella is clearly more suited for management, so she gets promoted into it. Rodrigo continues doing what he does best. Everyone ends up where their skills are most valuable. :doh: