Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Read programmers

2025-04-09 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

Recently, I was very touched by some communication problems in the project. From the earliest programmers, to the later managers, and then to the current programmers, I feel that I should reflect on the deep meaning of some typical words of programmers and avoid some misunderstandings in communication.

1 "it should be done in a week."

When I was a programmer, every time I said this sentence, I would question whether it could really be done, and there was usually a buffer time after the channel was passed. Because programmers are usually honest and optimistic, saying "should" is usually based on the premise of "if all goes well" and "requirements do not change". These are often impossible in the process of software development. If such predictions are easily accepted, projects will usually end up working endless overtime or even delays. So when I later managed a small team, I was careful to accept the programmer's estimate, and after careful confirmation, I usually added some margin. Now "reduced" to programmers, the company culture makes managers generally compress on the basis of programmers' estimates, so plans become a joke, a pile of delayed projects, not postponed but become a special case.

2 "this feature is very attractive"this feature is very difficult to use"

Yesterday, when I communicated a function with the planner, I told the team that I felt a function was awkward and difficult to use. Unexpectedly, the planner replied, "this is the idea of your programmers, and users will not think so." This sentence feels a little familiar, and I have heard it before. That's because the programmer got a reply after giving advice to the planner or project manager: "this feature is very attractive." When programmers think that "this feature is very attractive," they may be really looking forward to it when using the product, or it may be due to the sense of self-satisfaction caused by the technical challenges of implementing the feature. In the face of such words, we should be cautious and understand the intention revealed between the lines. However, this may be the case when programmers think that "this feature is not easy to use". As a developer of a product, it is hard to imagine that they can devote themselves to this product without approval. It is also difficult for a product that cannot be recognized collectively to perform in a competitive market. Therefore, I would like to remind the planning comrades that such words can be said, but not in inappropriate situations, which not only can not solve the problem, but also hurt the feelings among team members.

3 "this is achievable"

Programmers usually leave out the phrase "but …" when they say this sentence. It may require hard coding, special processing, and some obscure techniques. Well, in short, it's a little reluctant. This sentence is different from the categorical "this can be achieved", so special attention should be paid to the "but" that may be missed. If it is hard-coded, you need to consider whether a set of models can be extracted for unified processing. If special treatment is required, you should consider whether the process is unreasonable and needs to be adjusted. If obscure techniques are needed, you should reconfirm whether there are some general-purpose technologies that can also solve existing problems.

4 "Let's do this for now!"

Nine times out of ten, this will be the case when the final product is delivered. The result of delayed improvement is usually not improved under the dual pressure of time and technology. So when you accept this sentence, you should be prepared to "it will be the same in the end".

Finally, the programmer is the developer of the product and the practitioner of thought and planning. If the "voice" from this role is ignored in product development, no matter how good the planning and design will be, it will not be able to really fall to the ground. Whether you are a manager or a programmer yourself, please know the programmer!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report