Some ideas for interface development, popular version of the kind of
Before work, before and after the end of a function module, is a task to complete, so the interface development is not how great importance, especially to understand this concept alone.
A person taking the front and back is what it feels like? What you are not satisfied with the place, it would change the chant, behind the front, which want to change on a whim what, no problem at all, after all, wrote it myself, number of heart there.
I really like the work of programmers likened to building a house, a project that is a house, more collaborative projects, is a park. Taiwan before and after taking a person, that is the time to build a house, from construction to renovation, are you a human stem decoration when not satisfied with what is, removed the redo is so capricious.
Once the separation of the front and rear ends, then the problem came
Change other people's code is a big taboo, an inattentive easy to do it. . . . . .
How to do that? We need to do more detailed chant, sets out the detailed functional requirements. Architectural design drawings as each room is doing, what features are clearly written, for example: this room is the library, when construction on the first reserved for cable, air conditioning, a wire pipes, etc., then we must leave the kitchen outlet, gas mouth, the corresponding wire conduit ......
decoration of the time, use these interfaces accessed by a variety of things, a large chandelier or lamp, Gree air-conditioning or millet casual contact, as long as the voltage of the electrical connection, connected to the same water as long as the valve port specifications on the line.
Our programmers requirements document, too, what features you want, write what you backstage to function, and then leave the interface. What is inside the front-end interfaces do not bother, just know inside out what is on the line. Write back-end interface, detailed lists of incoming and outgoing values. These values do take the foreground, back-end do not have control.
The advantage of this is that as long as a back-end, front-end is ios, Android or web, simply do not care.
I like that there is a water pipe interfaces, you just plug in, and then a water heater or solar energy or tap? Do not control, as long as a twist valve water side can water, then the water pipe interface is qualified, as to how to use out of the water, and that is the decoration of the problems of workers.
I stay interfaces, protocols as long as you right, you pass a value over, I spit out a lot of data to you, to work on the back end of the qualification, as the front is ios, Android, web data do take this, who knows?