Perl Monk, Perl Meditation | |
PerlMonks |
Re: Measuring programmer qualityby talexb (Chancellor) |
on Oct 25, 2007 at 21:08 UTC ( [id://647278]=note: print w/replies, xml ) | Need Help?? |
I understand the desire of non-programmers to want to tie 'quality' or even 'kwalitee' to hard numbers. I think this is a futile quest. Or kwest. As a programmer (I like to call it "software engineer", la-de-dah), I have certain ideas about how to measure someone's quality. You'd probably want to look at the following:
I hope I meet a lot (if not all) of the criteria in the first list -- I'm proud of my code, and I believe it's high quality stuff -- one of my scripts has been in Production as version 1.4 (the third revision) for over two years -- it's a little over 100 lines, but it does exactly what it needs to do, and well. Conversely, a programmer who hoards information, whose code looks horrible, who cannot fix any of their own code, who refuses requests to do a code review -- that's someone I'd stay away from. These are more qualitative measurements, but I think they're just as valid. Oh, and one more thing -- programmers need to be able to communicate well, because without communication, nothing's going to get done on time.
In Section
Meditations
|
|