To be responsible for the
“The pragmatic programmer takes responsibility for his own career and is not afraid to admit ignorance or mistakes,” he says. After years of programming and understanding of the profession, popularity within a company, among colleagues, and when working on projects in collaboration is the most important thing after hardcore ability
No matter it is the responsibility, if a person can handle, complete and feedback the progress in time from the beginning to the end, I think such technical personnel can be said to be the best, no matter it is a function development, a three-party demand docking, and multi-department communication and coordination.
Iteration in many development projects, often to meet new people take over project teases so-and-so code before it’s too bad the function of the lead to develop their own always bugs, such and such function is not to write their own don’t come to me, but if all things can do their duty to the whole project in good running, is not each of us do technical value? In a lot of daily scheduling development, I often encounter that the progress of the arranged partner is not completed as scheduled, nor reported in time, as if everyone is pretending to be confused as long as I don’t ask. Such technicians are also not loved by their colleagues. Put yourself in the position of an analogy, like his work handed to a person, if that person did not finish on time, his heart must be wondering whether this is done? Where are we? Is there any difficulty? I think people with a strong sense of responsibility will pay attention to the degree and quality of the completion of the event, so as not to make a thing unknown.
Offer options and no lame excuses
Solve problems instead of excuses. A leader confessed to xiaozhang a development of the public number to pay the function, two weeks passed, asked the progress is that the public number needs so-and-so operating personnel to apply, he has no authority. This is the kind of thing you’ll encounter in the workplace. How would you react if someone, such as the bank counter clerk, auto mechanic, or shop assistant, gave you a lame excuse? What would you think of his professional operator?
Don’t put up with broken Windows
Don’t leave “broken Windows” unrepaired. Such as poor design, bad decisions, or bad code that you don’t fix, fix as you find it, and always leave it cleaner and more elegant than it was when you saw it. If there is not enough time to make proper repairs, nail it up with a board, note that the situation is under control and optimize it as soon as there is time. The broken window effect is that once a window starts to break, it deteriorates fairly quickly, leading to software rot.
If you are tired of reading the text, you can search for “Shar-pei 2021” at station B to enjoy the charm of knowledge by listening to it.
Portal: space.bilibili.com/407643589
Shar-pei 2021
\