It’s okay because it’s not an important feature this time. Developer : (Oh? I guess I ate some airborne food) Take your time studying magic keywords that are commonly used by developers. If you use terms such as React and Node, you might wonder if this operator has eaten a lot of work. Operators should also learn basic terminology! Even if you are not an engineering native, you can be reborn as a Korean by just interjecting terms. The point here is not to understand, just memorize it. Now, the world of ball substitution will come. 6) When there is a common goal, let’s align the brain structure with the developer. Operator : Thank you for your hard work handling this problem! Developer : I think it will still take a while to solve the problem. Currently, only images are provided from the server.
If this changes I think I will have to set up a separate
Background image and send the schedule one by one from each server. Then, you will Japan Phone Number Data also need to fix the server DB structure. djblahblahblahblah Operator: ( I don’t know, but just listen) Normally, there aren’t many situations where operators have in-depth conversations with developers. So the brain structures of these two groups are quite different. The operator approaches first and asks the developer how well he or she overcame the obstacle. It’s really exciting to talk about. This is also a time when you can feel a sense of kinship with developers and upgrade your development background! Developers and planners have significantly different brain structures than usual. Why are you so indifferent to my words? Let’s explore developer craftsmanship. 7) Developer is not a command input window. Operator : Here is the work statement. Please meet the deadline. This is a situation where you have to request work from an unfamiliar developer.
It seems like it needs to be organized in a neat document
As a result, I end up writing tight work instructions or to-do lists. However, as. I write a India phone data document, as , the situation and context gradually disappear. Just because developers say it’s stiff like a robot doesn’t mean it’s a real computer. It is much better for developers to work if they share ‘intention and context’ rather than just listing facts.No matter how difficult a development task is, if you understand the goal, you will have the will to take on the challenge. If you explain the entire context verbally once again, developers may dance while coding. Commands are given to the computer… 8) Please stop sniping at the developer who created the bug. Operator : It’s a bug! The locals said there was a bug! Developer : (No… that can’t be… it can’t be the code I wrote…) Sometimes I shout out bugs, but sometimes it’s just a shout in the air. It’s been a while since I figured it out and thought I could say something helpful, but the response was so indifferent that I felt frustrated and angry.