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.
(Score: 2) by TheRaven on Tuesday December 05 2017, @02:21PM
Two things:
Does anyone use the software that you've written? Do they make money from it? If yes, then that's the easiest way to get paid. I've been paid to add features to open source projects that I created and others that I contribute to. As to not being able to find jobs, what skills do you have? I'm back in academia now and I get regular pings from people I know in industry to see if I have any competent students that they can hire, or if I know anyone more experienced looking for a job. There are lots of well-paid jobs out there for people with useful skills.
sudo mod me up