The old programmer said: stop translating the world, developers should return to programming

      

During this epidemic prevention , Everyone is free , all Sum up .    Recently developed a personal interest project . Just to summarize the thinking that this project brings to me .java Programmers , Is there such a situation , Use third-party software , Especially instrumental , Framework software , perhaps jar package . Often report some inexplicable mistakes . Then search the Internet for half a day , Check for half a day . Really not line , Open official documents , Open principle . Even go to the source . Are you familiar with the scene ？ Struggle in pain , It was a fluke that solved countless problems , But there are countless problems , countless jar Waiting for myself . Countless pits are waiting for themselves . Fatigue will always come one day in the future . In countless tired , In a thousand sighs , Can you think about why ？ There are so many problems in the world , There are so many pits ？

     Maybe java Something's wrong with the world , If it is , What's the problem ？

     My long-term development experience , And insight , I have an impression ： Developers spend most of their time modifying the definition of a class , Storage . The existing JavaWeb Development , Whether it's based on tradition War Package mode , still SpringBoot The micro service model of . Design class , Design persistence layer ORM, Database design this is occupied 30% About the workload . Especially in the early stage of development . And subsequent changes ,CRUD Business logic .

       Any system , A project has its own unique field , For this system , Always design a concept , And then the system is polished . Every cross field . We have to design such a set ： Concept , Model , Class system , Persistence layer , database . It's up to the developers to keep debugging , Joint tune . Embracing change , You also have to do supplementary design at any time , That means , The system needs to be developed iteratively , Constantly being compiled , Continuous deployment and distribution .

       Years of experience ,OOP Style code , Especially lengthy . redundancy . Even after reusing the relevant code . After constant refactoring , Still can't solve these problems in essence .

      OOP The biggest problem is that any data is expressed as a class situation , This means that as the business changes , As the structure changes , Continuous development . A dynamic world , Need such a group in order to meet the business needs , Update the code at any time , To achieve the normal expression of business . Embrace change with the youth of such a group of people . Dao begets One , One begets Two , Our vision-be , On the way to express everything , How many young programmers are consumed in the process of creating everything .

      Developers should not translate , It shouldn't be a microphone . Let the work of creating everything turn over to a relevant business person , Experts and professionals in related fields .

     Programmers should be able to provide this kind of possibility , Let the business students , Let the life of all things , Become a track to follow 、 A pattern to follow . The searcher is discovering the law , And let the rules be programmed . Architects , Program , It's not about stacking things , Stacking business , Stack information of a certain kind of literal code . Good refactoring , Programs with high reuse rate may need to be done by people . Knowledge based projects , Projects with high reuse rate , It needs constant polishing . In the literal world , Let's refactor more , More reuse rate . It doesn't fundamentally solve the living things , Make everything , The process of modeling everything .

java The program is very good at literal translation . One corresponds to the world .  Especially some data , Data is data , The concept of object-oriented makes data an object , The object is the data . And a set of ORM layer . And then again ORM In the world of . indulge in self-delusion .

from ORM Leave the world . So many Select,Update,Delete, Come here you wrote ？ None of this should be done by programmers . Give this part to the business people , Operations staff . Back to programming . Procedure is the law , It's the big rule , It's not trivial . The minutiae is business , Give business stuff to business people .

Good procedure , It shouldn't be literal translation , It should be knowledge , Data type , Streamlined projects . Good software , It's not a literal project , Software volume will not increase with business changes or growth programs .

Good software , Young programmers' dreams should not be wasted , Interest in , hobby , Even life .