Programmers hate worthless tasks

Most programmers, as far as I know, the better they are, the more they hate worthless tasks.

Find the value of their work

Over the years, I have seen many successful software developers move into management positions, or other completely different careers. Sometimes the reason is as simple as wanting a higher salary. But it’s also because I’m tired of the exhausting state of constantly needing to learn to keep up with the pace of software development. Of course the most common reasons are boredom or losing interest in the work itself. These people often do so because their work no longer challenges them enough and they believe they are devoting their time and energy to work that has little value.

Software Developers Hate Worthless Tasks

There have been low points in my software development career: a project or task that I spent a lot of time, energy and creativity on was terminated or significantly cut back for some reason. its functional scope. Although I received the same monetary compensation, my expectation before working was to deliver a successful product, so instead of feeling satisfied, I felt very frustrated. It makes me feel like the time and energy I put in is worthless.

Canceling tasks isn’t the only reason to become disillusioned with the value of your work. Unnecessary tasks or other arduous work can also make software development more difficult. These things always look like they are useful or helpful to the task, but have little value.

Processes

From the perspective of many software developers, the biggest enemy of software development productivity is redundant processes. In the book "Process Kills Developer Passion", James Turner writes, "The blind application of best practices throughout the development process has turned us from a creative process into a confinement .”Turner said that all developers are not equally capable, so they cannot be treated in the same way. "Companies need to understand that there are essential differences between developers, so you have to make sure to set the weight for each person, at least not to damage the overall morale and team efficiency."

I think most people are obsessed with this Anyone who has been in the business for many years understands that a certain degree of progress is reasonable and even beneficial. But the "degree" depends on the project, the developer's experience, and the size of the team. Standardization and coding conventions have many advantages. The benefits of unit testing and other quality processes are even more well known. Suffice it to say, the best developers are able to determine what processes are suitable for what situations and when they are inappropriate.

Meetings

Only short, well-run meetings can provide us with huge benefits, most meetings are just a waste of time, especially if the meeting is late and overtime. A good meeting should start on time and address only those issues that must be addressed. For example, some team members are not used to expressing their opinions, so some short, informal meetings to communicate work are necessary. Some difficult design decisions and architectural trade-offs can also be discussed in meetings. It can be said that a well-run meeting has a positive effect: it can help developers establish a clearer direction and improve the overall efficiency of the team.

I have also made a post before about how to hold meetings effectively. The key point is that you should learn to take notes, record who participated at what time, record important decisions for future reference, and can also be used as materials to lend to those who did not attend the meeting.

Not every idea should be implemented

Not every idea has value. Developers often become impatient when they are forced to implement bad or useless ideas. That being said, it’s hard to bring yourself to willingly build something that may never be used, or worse, directly impact the user experience.

Cumbersome scripting tasks

Many developers tend to find other ways to solve particularly tedious scripting tasks instead of performing them manually, even if the time spent on manual execution is almost the same as the time spent on writing. This is also one of the best examples that proves that most developers hate tedious tasks. There are actually positive aspects to this typical approach for developers. First of all, maybe this task that we thought was a one-time task needs to be implemented again. Secondly, the act of writing a script has much higher value than just completing a task: it can not only improve the familiarity of the scripting language, but also provide good ideas or cases for solving related problems in the future.

Use regular configuration

Only when the configuration information is different from the regular configuration, the developer needs to provide detailed configuration information, otherwise just use the regular configuration. This can save developers time and reduce a lot of boring configuration work.

It may seem worthless at first, but it’s not.

In most cases, our judgment of whether a task is valuable or not is generally correct. But there are also tasks that seem useless at first, but later it is discovered that it can indeed provide real benefits and is indeed valuable. This situation also reminds us that we need to keep an open mind about the value of new ideas, not to kill them with a stick, but to carefully analyze their impact. So what a software development manager has to do is assign valuable tasks to developers and make sure they understand the value of those tasks.

Execution

Even a very potentially valuable idea will greatly reduce its value if it is not implemented correctly. Similarly, code review and code quality tools can create huge value if used correctly, and vice versa.

Conclusion

When we like the work we do, when we think what we do is valuable, we can often complete the work perfectly. Tasks with no value or low value are more likely to be considered redundant tasks and therefore cannot be completed well. All in all, it's obvious that developers will be more motivated, passionate about development, and happier if they don't have to be forced to perform worthless tasks.

Get it for freeLAMPBand of BrothersOriginalPHPTutorialCD/ 《DetailsPHP》 Essential version, please contact the official website customer service for details: http://www.lampbrother.net

PHPCMSSecondary developmenthttp://yun.itxdl.cn/online/phpcms/index .php?u=5

WeChat developmenthttp://yun.itxdl.cn/online/weixin/index.php?u=5

Mobile Internet server-side development http://yun.itxdl.cn/online/server/index.php?u=5

JavascriptCoursehttp://yun.itxdl.cn/online /js/index.php?u=5

CTOTraining Camphttp://yun.itxdl.cn/online/cto/index.php?u=5

The above has introduced the valueless tasks that programmers hate, including aspects of it. I hope it will be helpful to friends who are interested in PHP tutorials.