How to Keep Your Best Programmers (2012)

Re:How to Keep Your Best Programmers (2012) by quotemstr on Wednesday May 31, 2017 @02:00PM (#14454573)

Process is the enemy. Reward people for business impact, and fairly evaluate that impact, and all else will follow. When something goes wrong, don't react by adding process to prevent the thing that will go wrong.

The costs in slowed developer velocity and increased developer frustration are largely invisible, but cumulative, and they lead to unhappiness and organizational paralysis.

[ Parent | on HN ]

Re:How to Keep Your Best Programmers (2012) by khaledtaha on Wednesday May 31, 2017 @02:09PM (#14454667)

>Process is the enemy.

Nowhere in the article is process mentioned. So I'm not sure how you concluded that process was to blame.

Let's say that process is the cause. How would you evaluate and reward people for 'business impact', presuming we have a method of determining it? Wouldn't it be through a process?

Perhaps what you meant to say was that poorly designed processes or a process driven culture cause problems, one of which is employee boredom.

[ Parent | on HN ]

Re:How to Keep Your Best Programmers (2012) by timClicks on Wednesday May 31, 2017 @02:15PM (#14454711)

FWIW it doesn't need to be in the article for someone to provide their own viewpoint and experience

[ Parent | on HN ]

Re:How to Keep Your Best Programmers (2012) by unit91 on Wednesday May 31, 2017 @02:37PM (#14454854)

> Reward people for business impact

Very easy.

> and fairly evaluate that impact

Very hard.

[ Parent | on HN ]