Developers, don't let anyone kidnap your work pace

[Editor] listens to users' opinions, but needs to control the pace, objectives, and processes of the entire work.

As a software developer, your work is far more than writing code. There are also some things you are responsible:

• Estimated work cycle
• Understand the features of software you have never written
• Simplify complex problems
• Break down complicated problems into several small problems
• Adjust code to reserve space for Iteration
• Discover and fix vulnerabilities
• The above questions are completed in collaboration with other members
• If you interact directly with your users, there are more suggestions:
• Translate user requirements into improvement plans;
• In simple terms, the complex meaning is delivered to users in a simple way;
• Clarify every problem to be resolved.

However, based on these responsibilities, the most important thing is to set the goal based on understanding the target users.

Setting goals means to maintain control over the pace and process of your work and ensure that your work can proceed. This means that we need to predict risks and let users know the potential risks, so as not to be caught off guard temporarily. This requires a series of rules and processes.

If the method is proper, whether or not to set a target may cause two completely different results: suffering and enjoying work in some cases.

As a developer, you are a craftsman. You can use any tool area to create a product. You cannot set others' expectations above your creative freedom. You must control the creation process on your own.

If you place the user's Will above your creations, the following results may be possible:

• Your users will "think" when the work should be completed. At that time, you may only have to prepare half-products and cannot meet users' expectations;
• If your work fails to follow the user's expectation, they will feel frustrated and lose confidence;
• Users' expectations will force you to do something you don't agree.

Of course, the ideal situation is that the user will respect each of your goals, but this situation is not feasible. Remember at any time: In the process of software development, you are the person who decides when to achieve the goal.