I have been working for nearly eight years. In addition, I have been in close contact with the code for more than eleven years since I joined the University for three years. So why can we stick to it after so many years? Doesn't it mean that the code writing is only 30 years old? How long can I stick to it? I can't say that I can stick to it for at least two years.
Why can't some people stick to it? One of the reasons is that the method used last year is still in use this year, and there is no change at all. And next year, there will be no changes, and there will be no improvement (including technology and salary ). So if you can't hold on, you just need to wrap the line.
So why can I stick to it? Because I am constantly improving! Looking back on the hard work of the past few years, the technology has improved almost every year. This is not to say how much new knowledge has been learned, but to solve the same problem, the techniques used are becoming more and more efficient. Over the years, I have been working on information management projects, from websites to internal management programs developed by enterprises. I have been dealing with databases.
Remember that when I was writing code in, I joined the SQL statement, writing the stored procedure, and dragging a widget on the webpage.
In, I summarized a "my data access function library" and wrote the first custom Server Control-Paging control.
In, I began to write form controls, because I didn't want to drag them on the webpage of a widget, because I was very lazy and wanted to find some lazy methods for myself. After the Form Control is written, it will be much more convenient. After you write the configuration information, you can add (modify) the function and you don't have to splice the SQL statement yourself, you don't have to worry about Automatic Control binding and automatic value selection. Of course there are many disadvantages.
In, we improved form controls, query controls, and paging controls so that they can adapt to more scenarios.
In, the website was created. In the past, we used background management (such as CRM) and improved some pages that are not suitable for websites.
In, we continued to work on the project. The project requirements were more complex, and some form controls were not suitable. There were two problems: 1. layout. 2. A form control can correspond to only one table. What should I do? Give up or improve. I chose improvement.
Continue to upgrade various custom controls in. Now we have achieved the intended goal. Not only a single table, but also a Master/Slave table. Layout, formatting, verification
In addition, permissions are constantly summarized, summarized, improved, and improved.
I want to build my own framework. Although it may not be possible, there is a goal after all.
Continuous progress has supported me. This is nothing for you, such as tips, less money, no stream, and non-standard. But for me, this is what I step by step, a few small footprints I stepped on. You may feel that the speed is too slow. Well, I have to write controls and complete projects. Doing a good job in projects is the first requirement. Writing controls is my hobby.