4 ms·
> A developer’s skill is measured in one parameter: how well he writes code. While this could be a valid viewpoint, one thing I’d caution against is that this
by mathgeek 7y ago
> A developer’s skill is measured in one parameter: how well he writes code.
While this could be a valid viewpoint, one thing I’d caution against is that this type of measurement inevitably leads to the commoditization of developers. Rating skill on a single point will lead to “you’re only worth what this metric says you are worth” and eventually to constant competition between developers instead of cooperation. At least that’s the experience I had in such positions during my younger years.
- Nursie 7y agoIt's also wrong - if a developer can't communicate, interact well with team mates, sensibly translate requirements to program structure, discover requirements, pitch technological decisions to management, keep up on OSS tech that could prove useful, document well, review others code, etc etc... they're not at the top of their game. Being able to write code well is just one of the skills needed in a good developer. It might be the main one, but without the rest it's not really enough.
- booleandilemma 7y agoActually I’ve found that a lot of development is actually about image projection, or how good you make other people think you are. This is especially true with non-technical folks, who don’t know 1/2 of what developers do anyway. Our office’s “rockstar” dev has his 3 widescreen monitors tilted vertically and he uses a split keyboard. He’s so quirky and leet.
- draw_down 7y agoNot everything is an affectation.