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 Snotnose on Tuesday December 05 2017, @12:50AM (1 child)

    by Snotnose (1623) on Tuesday December 05 2017, @12:50AM (#605431)

    You call a meeting to "communicate" your political goals. You call a meeting to show your superiors your worker bees are "informed". You call an hour long meeting to impart info that I could have grokked reading a 1 minute email. I'm under schedule pressure, you call a mandatory hour long meeting with 5 minutes of information, followed by "so Snotnose, how was your weekend?" You can't remember who is doing what, so you call meetings to remind you what $random_monkey is working on. Never mind if you ask Fred what he is working on I can give you detailed information. As well as Wilma, Barney, Betty, and Bam Bam. You're failure to remember WTF we're working on should not translate to me going home an hour later.

    --
    When the dust settled America realized it was saved by a porn star.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by Snotnose on Tuesday December 05 2017, @01:22AM

    by Snotnose (1623) on Tuesday December 05 2017, @01:22AM (#605449)

    Back in the day, when I was a manager, I did not have weekly status meetings. When I did call a meeting, if I had 10 minutes of info to impart the meeting lasted maybe 15 minutes. None of that "I booked this room for an hour, I'm gonna use this room for an hour". No, it was "we're done, back to work".

    My worst boss story? I married a woman who worked weekends. She was sales, half her weekly income came from working weekends. She worked out a deal to get every other saturday off. All of my co-workers knew this.

    So, suddenly this high priority project comes up that absolutely has to be done by Monday morning. That Saturday was my wife's every other weekend off. All my co-workers, including my boss, knew this. I busted my ass all week, going in early, getting home late (did I mention the wife got home about 7 PM, and I was responsible for having dinner ready?). I busted my ass, got my part done by Thursday. So friday rolls around, boss comes in and "you'll be here tomorrow, right?". "Um, no. I busted my ass getting my shit done, my wife has tomorrow off, fuck off". After some 20-30 minutes I was convinced to show up Saturday, because it was a "team building experience". We won't mention my part was done, I had nothing to do that really needed doing, and was just there for "team building". The rest of the team, including the boss, knew I'd been working 12-13 hour days all week to meet an artificial deadline, so I could have Saturday off with my wife.

    Best part? Turns out the whole "team pulls together on Saturday" was my boss' idea of a team building exercise. Considering all the team knew how hard I'd worked to get Saturday off, plus the goal was a bullshit thing that didn't matter to anything, it pretty much backfired.

    --
    When the dust settled America realized it was saved by a porn star.