hmmm - since we are government, won't be able to do those type of rewards.
Though I do have a mean brownie recipe that many of my coworkers are fond of... | [reply] [Watch: Dir/Any] |
Hey, that's a pretty good idea ... you can give out "brownie points"
- literally! As a "team motivator", keep an eye on the situation, and
give out points, and when the team reaches 20 points, you bring in a
batch of brownies...
Although, admittedly, it would be much nicer if everyone just got
along and you didn't need to bribe 'em.
Personally, I am the one that gets to dictate the coding standards
for perl in our team, and I've found that pointing out problems during
code reviews is extremely useful in getting people to think my way.
That is, pointing out what scenarios the person's code doesn't handle,
why it isn't flexible, what type of future requirements to keep in mind
when coding.
And then I also point out in future code review sessions where these
changes have come in useful. Changing requirements sometimes end up
meaning no code change because of how flexible the code is1.
And it's those lightbulb moments that really get us all on the same
page. Our manager sees "changing requirements" and equates it to
"delta work" (extra work we didn't sign on for). And when we actually
don't do any extra work, even though our manager thinks we did, that
just improves our perceived performance. And my teammates
love it.
1 I didn't take any computer science, so bear with me if
my terminology is a bit off. I subscribe not only to object-oriented
methodologies2, but also to what I call data-oriented
methodologies. What I mean is that I put the common stuff into a data
store of some sort (even if that's a hard-coded hash or array), and
then loop through the data to do what I need instead of unrolling the
loops and duplicating code. 90% of our data for my primary project is
stored external to the code, and I'm trying to find ways to get the
other 10% moved out, too. I do this in perl, C, C++, Java ... and am
trying to do it in shell script, too, but Bourne shell is extremely
limiting for this ;-)
2 I like OO, but I am not a purist. I probably use OO
more than many people, but definitely not 100%. Not everything is an
object. Lots of stuff is, but not everything. For example, using
perl6-isms, I'll probably like to be able to do something like
@list.=sort(). But that's largely due to a more generic
built-in (non-OO) sort that will be available from the core, using
callbacks (such as sort in perl5).
| [reply] [Watch: Dir/Any] [d/l] |
Ugh. Developers who have to be "motivated" in such a childish fashion ought to be fired. | [reply] [Watch: Dir/Any] |