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: 1, Interesting) by Anonymous Coward on Monday December 04 2017, @07:20PM (2 children)

    by Anonymous Coward on Monday December 04 2017, @07:20PM (#605221)

    On an "agile" team where every breath or arm movement must have a documented story or task aassociated, this is impossible. If you create a proof of concept to illustrate your point without it being pulled into the current sprint, you've broken the rules and will be punished appropriately. If your idea is dismissed out of hand, you won't be given permission to created the proof of concept.
    No working under the radar, all activity is held to account at the daily standup.

    Starting Score:    0  points
    Moderation   +1  
       Interesting=1, Total=1
    Extra 'Interesting' Modifier   0  

    Total Score:   1  
  • (Score: -1, Redundant) by Anonymous Coward on Monday December 04 2017, @07:31PM (1 child)

    by Anonymous Coward on Monday December 04 2017, @07:31PM (#605228)

    Do the work you're told to do, but if you have conviction, then you'll do your own work, too.

    What?! Are you implying I should work outside of paid hours?!

    That's the kind of question a codemonkey would ask.

    • (Score: 0, Funny) by Anonymous Coward on Monday December 04 2017, @07:39PM

      by Anonymous Coward on Monday December 04 2017, @07:39PM (#605234)

      Obligatory code monkey song:
      https://youtu.be/kWrjYdD0Tg0 [youtu.be]