work experience essay

On March 3, 2016, I briefly recorded my work experience in the past few years. I

    recently changed a job and participated in many company interviews during my job search. Due to my strong expressive ability, I received a lot of company's interviews. Offer, but the most prominent problem in the interview is that my technical details are not enough, so that I either answer truthfully and have no experience in developing a certain technology during the interview, or rely on other methods to avoid the problem.
    When I took a company's written test, most of the questions I encountered were basic questions, the most common of which was the difference between abstract classes and interfaces. In fact, most developers must know this question, and I have also studied it carefully, but In the written test, I still did not answer this question well. So after I went home, I studied them again. Although I mastered the basic principles, I still did not consider the application scenarios of abstract classes. So I checked all the enterprise-level management projects I had done before, and finally found that almost all of them used interfaces instead of abstract classes. This is probably the reason why I couldn't really remember the principles of abstract classes, although I repeatedly learned them. Because in enterprise-level applications, objects generally directly correspond to business tables in the database, the attributes are almost consistent with the dictionary of the table, and the design of the table usually does not have much correlation, so there is no need to abstract the attributes into the parent class or methods, even if there are public parts do not use abstract classes. In addition to the enterprise-level system background, MVC is used. In the Controller layer, it is usually divided into Action layer, Service layer and DAO layer. The Action layer mainly handles the parameters passed from the foreground to the background, and calls the Service according to business requirements. Layer, and the real processing business logic is the Service layer. Finally, when there is a processing result and the CURD operation of the database is required, the DAO layer is called. Therefore, from the perspective of this form of development, it seems that there is no need for abstract classes to exist, because the calls between Action, Service and DAO are always implemented by injecting interfaces, which leads to the problem that abstract classes are hardly used. However, as the Service layer with the most complex business logic, there may be large-scale procedural-oriented programming, large functions and large objects may be seen everywhere. Therefore, it is possible to apply abstract classes in this layer, and it is also the part that should implement object-oriented programming.