Nine things developers need more than money
On Habré communicates a considerable number of managers of Internet projects and not less developers: designers, programmers. From my experience I know that there are often moments of misunderstanding of one another. In order to somehow help both reach an understanding, I offer a summary of Rob Walling's article :
Money is a strong motivation, but sometimes it is not the final and decisive factor in the struggle for good workers.
1. Start to succeed
')
This is a sad truth, but many software projects fail. Each developer has history and counter-examples of poor project management in stock.
Realistic deadlines are the basis of project success. Developers want to make software that not only works, but which is not a shame to show, and which they can then be proud of. This principle is often at odds with the goals set by the management, which wants to get just working software.
In general, the first thing that suffers with a lack of time is quality and reliability. The most evil that you can bring to the developer is to make him make a bullshit. What pride in your work then can we talk?
Work needs to be done not only quickly, but also efficiently. One developer I spoke with said: “Quality is as important as budget and functionality.”
2. Excellent leadership
Good project management is important both for the project itself and for people who will be motivated by excellent management. This means being able to listen to an independent point of view, to know what it costs to develop a quality product, to be able to make quick decisions and to be able to take responsibility for the whole team.
3. Learning something new
Studies of people's behavior show that we feel more comfortable when we learn new things. Two researchers from Columbia University concluded that workers are willing to give up an average of 20% increase if the work becomes more diverse or requires more extensive knowledge of the subject. In fact, we choose a lower salary in favor of a fun, interesting work for us, which also allows us to expand and deepen our knowledge.
Every developer I know loves to play with new technologies. The ability to saturate the need to learn new things should be for everyone. Allow your employees to learn, and they will be happy at work even in a windowless basement, where stale food is served through a small window. And they do not mention a word about promotion.
4. Creativity and solving real problems
Developers love being challenged. Without a fight, they are bored: they start checking email, visit Digg and Slashdot, read blogs and see which friends are online just to chat about their uncle, IDisposable interface or a piece of toast shaped like St. Mary.
How many times have I seen developers who have solved technical problems before dawn even when they were not asked to do so, and no one even stuttered about overtime. The best developers just live solving problems. Most of these people will not leave the case until the problem is resolved, and even more they delay the fact that the task will require a non-standard approach.
5. The right to vote
Developers are those people who are the first to find out about a non-working system or process. I once heard: “I want someone to listen to my problems and take them seriously. I worked in several places where the amount of memory, the number of hard disks and the processor clock frequency simply did not interest the company management. Every time I had to delete temporary files, because there was not enough disk space. You know, working with outdated equipment is just annoying. ”
When a developer says, someone should listen to him. When several developers talk about the same thing, then someone is obliged to listen to them and act quickly.
6. Recognition for hard work
Developers love hard jobs and jobs that impress themselves and their friends.
7. Creating something important
We are not doctors in Bosnia or even food porters in Sudan, but nevertheless, many people feel that they would like to do something good for the world, something social and technological at the same time. A system engineer who has created a logistic system that will reduce the mileage of the track made by machines for everyday distribution of the press will have more joy than a programmer who has written a program that will be launched 15 times a whole year.
Copy-peist pieces of code with changes to labels is not really such an interesting job as it may seem.
8. Creating software should not be accompanied by excessive bureaucracy
I worked under the contract for three years since 2001. During this time I wrote a lot of web applications. I easily wrote code when I knew exactly what and how to do. Together with one developer, we wrote tons of software for a couple. And, here, on my next job, software production could be compared to dragging with a weight. Creating each new page required the convening of six people to approve the changes. Development stretched 5 times longer. This is pretty annoying. The ability to make decisions without sitting in a group of people makes work very, very easy.
9. Few restrictions
Horrible code, interface bugs and poorly developed data model do not like anyone. Too many restrictions reduce the creative component, make gathering for making decisions on changes and in general, discourages all the desire to give all the best in the work on the project.
Money is a strong motivation, but sometimes it is not the final and decisive factor in the struggle for good workers.
1. Start to succeed
')
This is a sad truth, but many software projects fail. Each developer has history and counter-examples of poor project management in stock.
Realistic deadlines are the basis of project success. Developers want to make software that not only works, but which is not a shame to show, and which they can then be proud of. This principle is often at odds with the goals set by the management, which wants to get just working software.
In general, the first thing that suffers with a lack of time is quality and reliability. The most evil that you can bring to the developer is to make him make a bullshit. What pride in your work then can we talk?
Work needs to be done not only quickly, but also efficiently. One developer I spoke with said: “Quality is as important as budget and functionality.”
2. Excellent leadership
Good project management is important both for the project itself and for people who will be motivated by excellent management. This means being able to listen to an independent point of view, to know what it costs to develop a quality product, to be able to make quick decisions and to be able to take responsibility for the whole team.
3. Learning something new
Studies of people's behavior show that we feel more comfortable when we learn new things. Two researchers from Columbia University concluded that workers are willing to give up an average of 20% increase if the work becomes more diverse or requires more extensive knowledge of the subject. In fact, we choose a lower salary in favor of a fun, interesting work for us, which also allows us to expand and deepen our knowledge.
Every developer I know loves to play with new technologies. The ability to saturate the need to learn new things should be for everyone. Allow your employees to learn, and they will be happy at work even in a windowless basement, where stale food is served through a small window. And they do not mention a word about promotion.
4. Creativity and solving real problems
Developers love being challenged. Without a fight, they are bored: they start checking email, visit Digg and Slashdot, read blogs and see which friends are online just to chat about their uncle, IDisposable interface or a piece of toast shaped like St. Mary.
How many times have I seen developers who have solved technical problems before dawn even when they were not asked to do so, and no one even stuttered about overtime. The best developers just live solving problems. Most of these people will not leave the case until the problem is resolved, and even more they delay the fact that the task will require a non-standard approach.
5. The right to vote
Developers are those people who are the first to find out about a non-working system or process. I once heard: “I want someone to listen to my problems and take them seriously. I worked in several places where the amount of memory, the number of hard disks and the processor clock frequency simply did not interest the company management. Every time I had to delete temporary files, because there was not enough disk space. You know, working with outdated equipment is just annoying. ”
When a developer says, someone should listen to him. When several developers talk about the same thing, then someone is obliged to listen to them and act quickly.
6. Recognition for hard work
Developers love hard jobs and jobs that impress themselves and their friends.
7. Creating something important
We are not doctors in Bosnia or even food porters in Sudan, but nevertheless, many people feel that they would like to do something good for the world, something social and technological at the same time. A system engineer who has created a logistic system that will reduce the mileage of the track made by machines for everyday distribution of the press will have more joy than a programmer who has written a program that will be launched 15 times a whole year.
Copy-peist pieces of code with changes to labels is not really such an interesting job as it may seem.
8. Creating software should not be accompanied by excessive bureaucracy
I worked under the contract for three years since 2001. During this time I wrote a lot of web applications. I easily wrote code when I knew exactly what and how to do. Together with one developer, we wrote tons of software for a couple. And, here, on my next job, software production could be compared to dragging with a weight. Creating each new page required the convening of six people to approve the changes. Development stretched 5 times longer. This is pretty annoying. The ability to make decisions without sitting in a group of people makes work very, very easy.
9. Few restrictions
Horrible code, interface bugs and poorly developed data model do not like anyone. Too many restrictions reduce the creative component, make gathering for making decisions on changes and in general, discourages all the desire to give all the best in the work on the project.
Source: https://habr.com/ru/post/3020/
All Articles