Rejection pot esoteric back-end development

The following article comes from lonely smoke, the smoke of loneliness

 

In the movie "The East is Red", the wind took once said: rivers and lakes! As long as someone, there is resentment! There are scores, there are rivers and lakes! Person is dead, how you quit ah! "

As the saying goes, people sit in the station, pan from heaven. You are in position, the line and the code of good. A pot naturally befall you. Therefore, as well the development of a twenty-first century, how to learn the correct swing is an essential skill in the workplace pot life!

text

Three esoteric

We have to remember three points. There are three esoteric rejection of pot, we must remember, specifically those below!
First esoteric: rejection pot not panic
a lot of research and development in the novice thrown pot technique, because of not good at communication, others thrown over a pot, immediately flushed, stammered. Remember, once people party, when the idea is in a calm state can not, at this time can not make the right decisions. After many personnel will react calmly, FML, I should not take this pot ah!

Therefore, the rejection of the pot must not panic! Panic is taboo!

Second esoteric: rejection pan does not burst foul language
you recall your own work, which led thrown pot between the time that each burst foul language, are grinning thrown to the pot, right?

Well, mainly two factors, one is with foul language, difficult to listen to. On the other hand, after you bring foul language, people tend to be in in an agitated state! So, if the next person in this state, is unable to make the right decisions! Remember, thrown pot, they must be calm, do not excited, I am so excited make mistakes! Remember!

So, in order to correct thrown pot, please do not bring foul language!

Third esoteric: not crash dump pot
thrown pot technique essentially is a kind of communication skills, an ability to communicate exercise, would not life be thrown pot! As for how to strengthen communication skills, that is another topic, leaving aside here, we just dumped on the pot!

A dirty water poured over some honest people will quietly catch! However, the upshot is that a road spate of dirty water splashed over again!
So, faced with a dirty track, trying to will it to throw to. The result is not important, every dirty water poured out of the process, it is to exercise their own ability to communicate!

Three no's rejection

The first case: the evidence is left behind, you can not throw!
For example, the obvious thing is you do, you left a message in evidence.
Or, your chats was shot, and left evidence.
So, in this case, you go to the rejection, it is sophistry! Nature is very bad, thrown pot is only suitable responsibilities are not clear in some cases!

Second: The number of cases no obvious rejection of the results!
In some cases, pass the buck between each other is not the result of the kick. This time, do not play in another, and directly to high-level decision!
So, what is it this time-tested? OK, leadership trust in you! So, how to increase your leadership trust and goodwill, but also very skilled. Later on we will go into detail, here a little to have said something!
For example we will organize a number of activities in private bar, an analogy, you play in private!
For example feather fight it (I just cited)!
A staff actually a badminton master. A particular line activities and leadership in playing badminton. To win the leadership of three balls, then slowly let the leaders to catch up to the last ball win over A leading a staff.
Think about yourself, the following three questions

  • A staff why so hard to lose, what for him?

  • A staff if you lose too much, will achieve what kind of effect?

  • A staff if the leadership has been pressing play, what kind of results will be reached?


Well, these three issues would like to know, you will be able to understand a lot of things! I've revealed a lot, where the mood, we all go to understand!

Third case: certain objects can not be thrown!
First, do not put the pot training and preparation Single Meng sister paper! Remember, the focus is ... ah ...!
Second, do not put the pot training and preparation newcomers ! You also come from new people, I think he is still new when the helplessness. You have the heart to training and preparation of the new pot it!
Third, do not put the pot training and preparation Leader ! Believe me, leader of thrown pot methodology far better than you, or do not try!

Rejection pot methodology

Remember, for different roles, the method is not the same. Here there are elaborate products, testing, operation and maintenance, development!
For testing, we must emphasize that this is difficult to reproduce the BUG!
For products, we must emphasize that your needs have a problem!
For operation and maintenance, must be stressed, is your operational errors!
For development, no fixed method, resourceful!

The following give a specific situation, we have to exercise it!
An online interface in response to the slow!
For developers: This interface code, I was referring to before you write, you quickly see where a problem!
For test: this situation can be stabilized to reproduce it? Look at you!
For operation and maintenance: Ali cloud is not a problem?
For the product: This function processes too complicated ah. To achieve such a complex process, not no, the response time is slow!

An online interface to appear stupid mistake!
For developers: I'm not asking you about what code review, you actually did not see it!
For the test: such low-level errors, you actually did not cover! What to eat rice!
For operation and maintenance: Do not let your operation so it can not regulate it! Because you do XX operation, resulting in the interface hanging!
For the product: Your function is too complicated. To implement a little error normal, after all, such a complex business scenarios, people BAT products, will be out of the BUG!

Tasks can not be completed on time, delayed
for developers: how do you work it always the water, now make no difference, you say, how do!
For testing: Bug too many times, first reported little bug come.
For operation and maintenance: These simple online questions also always come to us, we know very tight development schedule?
For products: demand you always come and go, unable to complete the task!

Myself messing around, hanging out with someone else's service
for developers: Your business is not doing code review system ah, quick look where that right! Is there something, quick check with blown downgrade!
For Test: how do you measure and how their service just to hang out?
For operation and maintenance: how their services plus a couple of times to call hung up, where the machine configuration is not a problem?
For the product: It is not and you say, XX tone service, this program does not work. You see, people now serve hung up!

Guess you like

Origin www.cnblogs.com/xiang--liu/p/11857306.html