What John said – and:
Peer / supervisor / PM / client feedback and code reviews. The direct supervisor should be doing regular code reviews and over 3 months that should give him / her a very good idea of the quality of the coding – according to their own subjective views. How well the dev molds their coding to the local paradigm and their attitude is important also – but again it is a subjective evaluation. I know of no way to generate any real metrics. From: [email protected] [mailto:[email protected]] On Behalf Of John M Bliss Sent: Thursday, January 29, 2015 7:17 AM To: [email protected] Subject: Re: [houcfug] measuring quality for developers? When I was a consultant, it was stuff like: * hours billed to clients * revenue from completed projects - salary paid for hours to complete those projects = P/L * feedback from PM's and clients * feedback from teammates (developers, designers, DBA's, etc) And, yes, I found out that one of those companies had software running on workstations to count keystrokes. So if one or more of the above sucked and you weren't typing much, they saw it as a pattern. On Wed, Jan 28, 2015 at 7:32 PM, Mark Davis <[email protected]> wrote: One of the joys of working for a large company is having to set goals for each year. These goals have to be something realistic, challenging and measurable, so "showing up to work at least once a week" or "sleeping with Heidi Klum" just won't cut it. Unlike a salesperson, it is very hard to derive metrics for developers. Number of lines of code written would be idiotic. Even something as number of bugs is very difficult to define as to how and when a bug came to be and who is responsible for introducing it. Maybe server uptime, but what if you don't control your own servers? So, for those of you lucky enough to deal with corporate crap like this, what have you done in the past to define quality work by developers? Thanks Mark -- -- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en --- You received this message because you are subscribed to the Google Groups "Houston ColdFusion Users' Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- John Bliss - http://www.linkedin.com/in/jbliss -- -- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en --- You received this message because you are subscribed to the Google Groups "Houston ColdFusion Users' Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout. -- -- You received this message because you are subscribed to the "Houston ColdFusion Users' Group" discussion list. To unsubscribe, send email to [email protected] For more options, visit http://groups.google.com/group/houcfug?hl=en --- You received this message because you are subscribed to the Google Groups "Houston ColdFusion Users' Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
