What exactly is being adjusted by adjusting the interface, and where is the workload?

As an IT practitioner who does not understand technology, I often hear people say that today I am adjusting interfaces, and it takes a long time to adjust several interfaces. It feels like a huge workload. I would like to ask, what exactly is being adjusted by the adjustment interface? Where is the workload? I hope the technical experts can give me some popular science in simple terms. Many thanks! (If I can’t explain it in simple terms, it’s better to go deeper. I’ll check the encyclopedia slowly, haha. Thanks again!)

Reply content:

Mediation is about the different understandings of the same needs between you and your colleagues. This kind of thing is immeasurable. Who made you not work closely together from the first day. This is why I object to two people writing the server and client. IT has been around for so many years. Wouldn't it be better to treat people as CPU super-pipelines? You first do the server, and when you are done, you do the client. Even if you are forced to write the server and client together for temporary reasons, you should start the real server and client at the same time every time. If something goes wrong, don't worry about blocking others. The two of you can work together to solve it.

Although time seems to be wasted in the early stage, if you take a long-term view, the overall efficiency will be improved several times.

Ideal situation.

server: I’m OK, just call it!

client: My test call is ok, ready to test!

Actual (domestic) situation.

server: I’m OK, just call it!

client: 500

server: Let me take a look, it seems that a certain old code is abnormal. .

(Half an hour later)

server: I’m OK, you can call it!

client: Still 500

server: Forget it, I will refactor the old code.

(Two hours later)

server: I’m OK, you can call it!

client: Still 500. . Did you change the parameters?

server: It has been refactored. Adjust it according to the new parameters.

client: This interface is ok, but that one is down again.

server: I have changed the parameters. You should change them too.

client: Make a document. Bar

server: There is an online fault that I need to deal with urgently

client: ok (then make a cup of tea and browse Zhihu)

(an hour later)

Client team leader: Is the joint debugging ok? Our client needs to release a new version as soon as possible. You seem to be very busy.

client: Waiting for the server to give you new documents

Client team leader: Wait for a p and finish it quickly, otherwise your performance will be -1s

client :Server, come here, we can fix the interface quickly, this is going to kill someone

server: Damn it, the fault hasn’t been solved yet, I’ll help you for ten minutes

Server Team Leader: Has the fault been rectified? We have to ensure the quality of our services

server: I will come over later after joint debugging with the client

Server team leader: Contact me, please fix the fault quickly, otherwise the performance will be -1s for you

client&server: I am really screwed Dog

The essence of interface adjustment lies in "waiting" The workload is just being adjusted. The reason why software production is called development and not manufacturing is because it requires constant trial and error. Jointly debugging the interface with a related system,
0 agreed on the day of joint debugging, and they told me that they had just started development and would wait for two days for joint debugging.
1 They can change the interface document into three versions, and the parameter names in each version are different.
2 The promised five output parameters suddenly turned into two. After being notified of the defect, it took half a day to roll back and fix it. Two days before going online, there were only two output parameters again.
3 The calling sequence of the two interfaces AB was informed during the National Day overtime, but ten days later it was found that the order was still wrong
4 During the online verification, I found that D was called when calling the C interface. I didn’t sleep well last night
Everyone I work in IT, hum╭(╯^╰)╮ Isn't it my boss who asked? The standard project process is this.

PM produces project requirements document and MRD -> PM contacts relevant personnel for MRD review -> Designer makes design drawing based on MRD -> Back-end engineer produces server interface document based on project requirements, MRD and design drawing -> ; Front-end engineers conduct interface document review -> Front-end and back-end engineers develop in parallel and conduct independent self-tests -> After the front-end and back-end development is completed, interface joint debugging is carried out -> Testers conduct testing -> After testing is completed, release and go online -> Online Service function return

If you develop according to this process completely and every step goes well, it will naturally be ok. However, due to back-end engineers' confidence in themselves, they often do not conduct sufficient self-tests (or even test them at all). As a result, when the front-end and back-end are jointly debugged, the front-end finds that the back-end is unavailable, and then the back-end repairs the problem. Naturally, time is lost in the back-end. (There is a problem with the front end, and the back end doesn't know about it), and the project is delayed. Similarly, if the interface document is not written clearly, the front-end and back-end will have different understanding of parameters, which will also lead to modification of the interface or front-end implementation. If the number of times is too high, the project will be delayed.

Since this kind of thing is so common, the joint debugging time generally includes the self-test time, so once this test time is added, the joint debugging time will naturally become longer.

I don’t think Brother Lun’s method is a good method. There are specialties in the art, and people’s energy is limited. Even if a person is a full-stack engineer, there is one thing he is better at. Furthermore, different languages ​​and development at different ends have their own development specifications. If they are rotated frequently, a lot of energy will be wasted, and switching language development will also reduce the cost. Development efficiency. Besides, a large project cannot be developed entirely by one person. As long as there are multiple people collaborating, this kind of problem will occur. If the code of the same module is modified, problems are more likely to occur, even if it is not in the joint debugging stage. Will it not reduce efficiency if something goes wrong during the development stage? Process problems should be solved through standardized processes, rather than tearing down the east wall to make up for the west wall. First of all, assume you are talking about the key (second tone) interface, not the key (fourth tone) interface. Because there is no workload problem in the latter.

The answer to a previous question was about the problems encountered when re-issuing an expired passport, which is consistent with the problem of debugging the interface.

Suppose Xiao Ming (our side) wants to go abroad now and needs to apply for a passport (business requirement).

Xiao Ming went to the Public Security Bureau website (interface provider) to check the certificate application guide (interface document). It said that applying for a passport requires:

• A photo
  
• ID card
  

These materials (parameters). Xiao Ming can make an appointment online (interface 1), get a reservation number (call result of interface 1), and then go to the public security bureau where his household registration is located to apply. Or you can go directly to the Public Security Bureau (Interface 2), but you may not be able to make an appointment on the same day.

Xiao Ming decided to try making an appointment online, but the website showed "appointment successful" (the interface is inconsistent with the documentation). And then you think, OK, that worked (an oversight on our part).

Xiao Ming went to the Public Security Bureau with his photo and ID card. As a result, the girl from the Public Security Bureau spread her hands and said: Where is the number?

What’s your number?

Reservation number?

No?

No, it doesn’t count. Otherwise, you can make an appointment online and get the appointment number, or you can make an appointment on site. (The result is different than expected, try again)

Xiao Ming thought, I will make an appointment on the spot. When I was about to make an appointment, I heard another staff member telling my little girl that the system was being upgraded recently and there might be some problems. Many people had made reservations but had not received a number (the provider was upgrading and restructuring). When the little girl saw how pitiful Xiao Ming was about to get fucked by his boss for asking for a day off, she just let it go and asked Xiao Ming to do it today (both parties negotiate a solution).

Xiao Ming was happy, took out his photo and ID card, and prepared to apply for the certificate (calling interface 2).

The little girl looked at it and said: What are you doing?

Photos...huh?

No, you are not following the rules. Passport photos must be standardized. Photo Gallery A is our special partner. You go to them to take photos. The data will be sent directly to us. Just bring your ID card (the second provider).

Xiao Ming was speechless. Why don't you make it clear on your website?

The little girl said that if you look at the website, our website was built the year before last, and the policy has changed long ago (the documentation has not been kept up).

Xiao Ming had no choice but to go to Gallery A.

A I heard it at the photo studio and thought, oh, I know, you can take a photo.Then he took it and said, OK, I will upload it to their system for you, and you can go directly.

Xiao Ming returned to the Public Security Bureau.

Little sister: Wait, the Internet is a bit slow today, and the photos have not been transmitted (interface calling problem between providers).

Waiting and waiting, until it was almost time to get off work, it finally came through.

Little sister: Okay, it’s finally downloaded and you can start.

Xiao Ming breathed a sigh of relief.

Little sister: Wait, no, our system submission channel is closed.

Xiao Ming:? ? ?

Little sister: That’s right, our boss loves us very much, so when we were designing the office system, he asked us to close the business channel when we get off work in half an hour, so that we can tidy up the table and talk about where to eat in the evening. .

Xiao Ming:? ? ?

Little sister: I’m sorry, I’ll go early tomorrow.

Xiao Ming had no choice but to go to the Public Security Bureau the next day.

Little sister: I’m so sorry. The pound sterling plummeted last night, and suddenly more than 2,000 people came to apply for passports and go shopping in the UK.

Xiao Ming:? ? ?

Little girl: Our system is a bit old. As long as there are more than 255 people in the queue, it will crash (unexpected situation).

Xiao Ming:? ? ?

Little sister: Our person in charge of the system is getting married for the second time today and will be back tomorrow.

Xiao Ming:? ? ?

Little sister: I don’t know when it will be repaired. You can call me tomorrow or the day after tomorrow and ask.

Xiao Ming vomited blood.

============

Adjusting the interface is such a process.

The workload and troubles are nothing more than:

• The supplier’s description of the business is incomplete. The reasons may be: 1. Not thinking clearly; 2. Lazy or unmotivated; 3. Failure to keep up after upgrades or business changes; 4. Deliberately causing trouble. Therefore, you need to constantly communicate, confirm repeatedly, or call the interface to see if the results are as expected.
• There are cooperation problems between us and various suppliers, as well as between suppliers and other suppliers. Problems in one step affect the overall situation. This is something that happens all the time - I look both ways when I cross a one-way street, because even if you can make sure you do it well yourself, you can't guarantee that others will do the same thing. The logic is the same. Therefore, we need to wait, or reconcile it, or find other ways to solve it.

In addition to these, the interface may have unexpected problems under certain unexpected circumstances (such as high concurrency), which also need to be debugged.

After knowing this, you will give a thumbs up to Qin Shihuang’s feat of unifying weights and measures, because he avoided communication between different standards and interfaces. The whole world uses the same interface, and communication costs are greatly reduced.

So, when it comes to adjusting the interface, you are the elder, you are the one who adjusts the interface, and you are the younger brother, you adjust your mentality.

The boss went to the bun shop and asked, do you have burgers? The boss ran to the McDonald's across the street to buy a hamburger in a few minutes, then replaced the filling with fresh meat and held it up with both hands with a smile. There is no workload, and the other party can adapt to you.

On the contrary, you can only go to McDonald's and buy a hamburger, buy a fresh meat bun, take out the fillings, endure the glares of others, and eat the burger silently.

The workload is naturally huge. Just like when you go to the bank to apply for a card Fortunately, our team has js running through the front-end and back-end. A requirement can be written from the migration file to the front-end effect. The design deliverable given by the designer is to get a display page of relevant CSS information by clicking on the graphic, so there is no chance of wrangling.