Thinking triggered by a trivial matter

Over a month has passed, and our educational administration system is still in full swing. To tell the truth, I feel really tired (psychologically ). Think about it. Every day for more than a month, students, teachers, courses, teachers, and so on will inevitably get bored. However, I also learned a lot in the process. Let's talk about a small matter.

 

The day before yesterday, Jie (our team lead) assigned us some tasks for us to complete in half a day. To be honest, the tasks assigned by jie should be almost completed in half a day. However, when I was writing code, I found that Jie's pictures were somewhat faulty, in some cases, the logic is not very thorough. As a result, I tried again and implemented it according to my own ideas. In this way, the progress slows down and the task is completed on time.

 

Upon hearing this message, Jie was angry: The task could not be completed, so you want to do so much, how can I draw it. To be honest, I felt quite wronged at the time. Clearly, you have a problem with your graph, and the logic is not fully considered. I just want to do something perfect. Is it wrong?

 

Wrong. A big mistake. Where is the error?

First, the task assigned by the team lead is not completed on time. No matter what reason you have, the final result is incomplete.

 

Secondly, in the process of cooperative development, I did not recognize my role. In the project development process, the team lead is the general and the team members are soldiers. Soldiers follow commands as the primary principle. In the process of software development, the team leader's diagram is a military order, which is similar to the decree. It must be executed unconditionally. Even if you feel that this is wrong, you must strictly implement it.

 

Finally, without the approval of the superior, modifying the logic without authorization directly leads to inconsistency between the diagram and the code (even if it is wrong, it must be consistent), causing trouble for later development.

 

Actually, no matter what you do, it should be like this. This is a rule! The so-called "no rule" is not a square view. However, if you do not want to do anything and follow these rules, you are the real coders. What should we do? We must abide by the rules, but we cannot constraint them. We can have our own ideas, but only when you have completed the task according to those rules can you be qualified to speak and your ideas be accepted. Otherwise, people do not give opportunities to explain, even if you are right.

 

Recognize your roles, clarify your tasks, and do the right thing at the right time! I don't want to be a code farmer. I want to have my own ideas. I know that it is far from enough to get rid of codoon. It is most important to know when to express your thoughts. Come on!