Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Monday December 04 2017, @05:18PM   Printer-friendly
from the it's-easier-to-deal-with-computers-than-with-people dept.

The Do's and Don't's of Managing Programmers:

Why are some programmers such jerks?

Too many managers believe the problem lies with [the disgruntled programmer]. If he was a better employee, dedicated worker, or at least cared more, then this wouldn't happen. Right?

Unfortunately, no.

The first suggestions matter a lot
How you handle ideas from new programmers sends an important signal. Good or bad, it sets the stage for what they expect. This determines if they share more ideas in the future... or keep their mouth shut.

Sure, some ideas might not be feasible in your environment. Some might get put on the back burner to be discussed "when we're not busy". Some ideas seem great, but they run against unspoken cultural norms.

No matter what the reason, dismissing or devaluing your programmer's ideas — especially in the first few months — is a bad move.

Damaged by all the naysaying, he'll try a few more times to present his ideas differently, aiming for a successful outcome. If he continues to feel punished, though, he'll realize that the only way to win is not to play.

Which is exactly what you don't want your programmers learning.

He will stop presenting ideas, asking to meet customers, and genuinely trying to understand the business.

Ultimately, it's a lose lose.

If you want programmers to become mere code monkeys, treat them like code monkeys.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by fyngyrz on Tuesday December 05 2017, @11:16PM

    by fyngyrz (6567) on Tuesday December 05 2017, @11:16PM (#605878) Journal

    That assumes that the software already does everything that the user wants.

    No, it doesn't. That's not support of individuals, that's evolution of the software. If your software doesn't evolve and grow, doesn't matter if it's free or for-fee; it's going to get left beside the road with all the other dead products.

    I add features all the time. Sometimes on a daily basis. I'm careful not to obsolete what's already there, or break it (ya gotta love automated testing), but in my area, sure there are always more features to add. Doesn't mean the new features need support, or that they are support. It's just product growth. If you charge for new features, you might as well charge for old ones. Same thing – just hiding under an excuse.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2