1. Share the first experience: "Education represents the past, ability represents the present, and learning ability represents the future." In fact, this is a research result from the field of foreign education. I believe that friends who have worked for several years or more than ten years have some experience with this truth. But I believe this is also very important: "If you understand the important truth too late, you will regret it for the rest of your life!" So put it in every article, so that friends who have just graduated can see it sooner!
2. Be sure to determine your own development direction and make a feasible plan for this purpose. Don't say, "I just graduated, I still don't know what I might do in the future?", "Follow your feeling, do it first." Because, such a point of view will imply through your subconscious that your actions are idle and mediocre. Always do technology, become an expert in the future? Go in the direction of management and become a professional manager? Familiarize yourself with the industry and field first, will you stand on your own? Or should I start out in the industry and change careers to do something else in a few years? This is very important, it will determine what you do in the next few years, ten years to do the right thing!
3. In the software development team, technology is not omnipotent, but no technology is absolutely impossible! In a technical team, technology is as important as character, and of course looks are also more important, especially in teams with more mm. In the software project team, the technical level is an important weight that is valued and respected by people. Whether you do management, system analysis, design, coding, or product management, testing, documentation, implementation, and maintenance, you must have a technical foundation. Even if I am ignorant, I have never seen a layman lead a software development team to successfully complete a software development project, even if it is only one. However, I once saw a "highly educated expert" (non-technical type) lead a group of people to complete a project. On the second day after the project was delivered, the project team members threw a sentence "I can't take it anymore!" go their separate ways. The "success" of that project can be imagined.
4. Develop your own software development professional knowledge learning plan in detail, and pay attention to timely correction and adjustment (software development technology changes too fast). Remember: "If a software developer hasn't updated his knowledge in 1 or 2 years, he is no longer in the industry." Don't tell yourself that you don't have time. The famous "three-eight principle" from the field of time management warns us: how to use the other 8 hours will determine your life or failure! Since I graduated, my average daily study time is more than 2 hours.
5. Books are the ladder of human progress, especially for software developers. Books are the most effective way to learn knowledge. Don't expect too much to meet "experts" at work and take the trouble to teach you. As for spending money on books, my personal experience is: don't buy books from those people in China! I bought books from those guys, !00% regretted them all, no exceptions. What's more annoyed is that these books are difficult to sell on the second-hand market stalls. "Having books does not mean having knowledge; having knowledge does not mean having skills; having skills does not mean having culture; having culture does not mean having wisdom."
6. Don't limit yourself to the superficial use of a certain technology, even if you only use it once or twice occasionally. "Follow everything" is a quality that should not be possessed by engineers in any industry. Develop windows applications, look at the design, loading, and execution principles of windows programs, analyze the pe file format, and try to develop a windows application program from scratch with sdk; use vc++, delphi, java, net to develop applications, take time to research Take a look at the framework design or source code of mfc, vcl, j2ee, net; in addition to using excellent open source products or frameworks such as j2ee, jboss, spring, hibernate, etc., take the time to see how the masters abstract, analyze, design and implement those similar problems general solution. Try to do this, and you will encounter fewer problems in your future work that make you unclear and confused, because you "know and know why" of many things!
7. Program in one language, but don't tie your mind to it. "Code Encyclopedia" says: "Go deep into a language programming, don't superficial." It is far from enough to go deep into the development of a language. Any programming language has its own reasons for its existence, so no language is a "panacea" for "cure for all diseases". Examples abound of the influence and constraints of programming languages on the way developers think and solve specific problems. My experience is: when developing some key modules with object-oriented tools, why can't we learn from the modular packaging methods of c, c51, and assembly? When using traditional desktop development tools (currently mainly vc++, delphi) to design the system structure, why can't we refer to the design ideas of ioc and aop from the java community, or even use excellent open source frameworks such as spring, hibernate, jboss, etc.? When designing and implementing functions such as real-time communication and data acquisition, why can't we refer to the excellent system frameworks and patterns from real-time systems and embedded systems? Why does everything have to be solved with an individual, a team's heritage or experience with a development language of course? ? ? "Stones from other hills, can learn".
8. Develop the habit of summarizing and reflecting, and consciously refine the results of daily work, form your own personal source code library, a general system architecture for solving certain types of problems, and even evolve into a framework. As we all know, for software developers, a significant difference between experienced and inexperienced is: inexperienced people start from scratch when they complete any task, while experienced people often solve problems by reorganizing their reusable modules and class libraries ( In fact, this conclusion should not be limited to the field of software development, it can be extended to many aspects). This does not mean that all reusable things must be implemented by yourself, and the mature test results of others can also be collected, organized and integrated into their own knowledge base. However, it is best to implement it yourself, so that there are no intellectual property rights, copyrights and other issues. The key is to truly master this knowledge point and have this skill after you implement it yourself.
9. Emphasis on theory and practice, both internal and external. The connotation of an engineer is: to observe and analyze things and the world with the eyes of an engineer. A qualified software engineer is a person who truly understands the essence of software products and the ideological essence of software product development (personal views, welcome to discuss). Mastering software development languages, applying language tools to solve specific problems in work, and completing target tasks are the main tasks of software engineers, but from the perspective of software engineers, this is only an external thing, not an important and essential work. It is the job of a real software engineer to learn and master the theoretical knowledge of software product development, software development methodology, and to understand and apply software product analysis, design, and implementation ideas in practice to solve specific software product development problems. Thinking, analyzing, and solving problems from the height of mature theory and reliable methodology, and verifying and revising these ideas and methods in specific practice, and finally forming our own theoretical system and practical methodology.
10. The more open the mind is, the more open the vision is. Don't hold on to your own technology and achievements, wait until they are outdated and become garbage, and then take them out to shame. Please release your research results in a timely manner: the developed products, creative designs or codes, and publicize them for everyone to communicate or use, so that your results will have the opportunity to evolve and sublimate. Think about the Windows system tools that I developed in XX years. Today, 5 or 6 years later, it is still the same. Many popular Windows system tools are later than their own, but they have evolved very well and are used by so many users. . And, don't keep your own technology and ideas, communicate and share with others as much as possible, or pass it on to the members of the development team. "After exchanging apples with people, everyone still has only one apple; but after exchanging ideas, everyone has two ideas", everyone understands the truth, but how many people can really do it?
11. Try to participate in the development of open source projects, or develop some of your own products with friends. Don't do it because you don't have money to make. The Internet is no longer just a "virtual world". There are many open source projects, cooperative development projects, and outsourcing projects on the Internet. This is an excellent opportunity to dabble in knowledge other than work, and to get to know a wider range of people. Don't just because your job is doing ERP, you won't learn and understand embedded, real-time, communication, network and other technologies, and vice versa. If someone else is looking for you to cooperate with a contract, but you can't do it, and you are not familiar with it, you will regret it.
12. Don't limit your knowledge only to technical aspects. The research results of Professor Simon, the Nobel Prize winner in economics, show that: "For a person with a certain foundation, as long as he is really willing to work hard, he can master any subject within 6 months." The educational psychology community is grateful for Professor Simon's research results, it is named Simon learning method. It can be seen that mastering an unfamiliar knowledge is far less difficult and profound than one might think. Learn from multiple sources and dabble extensively. Try to consolidate your circle of influence and expand your circle of attention as much as possible. Knowledge of finance, economics, taxation, management, etc., take the time to look at it, keep a low profile, and plan ahead.
13. Summary and reflection of this article:
a: Don't be a technical master unless your goal is this. Although this article is about improving your software development knowledge, being a technical master is something I've always disapproved of. You can improve your expertise, but only if you're up to the job.
b: Improving software knowledge and technology is only the surface of the problem. The essence is to improve the ideological height of self-understanding, analyzing and solving problems. Many methods and principles of software expertise can be easily extended and applied to other aspects of life.
c: On the basis of being competent for the job, immediately go to dabble in professional knowledge in other fields, enrich your knowledge system, and improve your overall quality, especially those friends whose goals are not technical.
Summary of the work of software developers
20xx is destined to be an extraordinary year, with joys and sorrows. The rare rain and snow disaster in the south at the beginning of the year and the 5.12 Wenchuan earthquake let us see the huge power of natural destruction and the vision of those who lost their loved ones. I also saw that under the correct leadership of Mr. Yu, the people of all ethnic groups in the country are united and united to fight the earthquake and have experienced a major disaster. Our nation is like the wood that has been sunk in water and the steel that has been quenched and will inevitably be greatly improved in quality. .
In 20xx, for our IT software development team, there are also many memorable places and many experiences to absorb. During the year, with the care and help of the central leadership team and other departments, we worked hard and studied hard. , I have done several projects, with achievements and deficiencies. I will report some situations to the leaders and colleagues as follows:
1. The completion of the main work
(1) Completed the overall planning scheme of “Digital Water Supply”, and signed the contract with the National Water Supply Bureau for the Basic Implementation Plan for “Digital Water Supply” and the “R&D of the First Year Planning System of “Digital Water Supply”, before April The investigation of the project was completed, the project research and development was completed from April to August, the system was put into trial operation at the end of August, and the relevant personnel of the Water Supply Bureau were adjusted and revised according to the work needs, and the first phase of the "digital water supply" project research and development was completed. Based on the frontier of high-tech application development, starting from the analysis of the business needs of modernization of production and management of water supply in the Yellow River Diversion, aiming at the technical problems that need to be solved in the management of water supply in the Yellow River Diversion, fully considering the realistic possibility and future development trends, put forward the "digital water supply”; implement the guiding ideology of “advanced and practical, fast and accurate, application traction, key breakthroughs, and gradual implementation”. Taking the development of water supply production and water supply project management and maintenance decision support as the core, starting from the high-quality collection of water supply management information, relying on the public platform constructed by the "Digital Yellow River" project, and using information to serve the modernization process of water supply production management in the Yellow River Diversion, Comprehensively improve the informatization level of modernization of production and management of water supply to the Yellow River. Begin to discuss, implement the project demand analysis in the second year of the "Digital Water Supply" master plan, and establish the software R&D plan and planning.
(2) Further improve the national water administration law popularization website system to realize the integration of the water administration law popularization website system (1+8 mode); the system is the publicity, interaction, office automation and After the system is running, information sharing and collaborative office can be realized within the network, thereby greatly improving the office efficiency and improving the modern management level. The technical report and acceptance materials of the project were compiled, and the company actively contacted the relevant departments of the provincial bureau, and passed the acceptance in December.
(3) Completed the development of the ** River Affairs Bureau's government affairs open network system and put it into operation. The operation of this system will greatly improve the speed of informationization of Shandong's overall government affairs disclosure, and make the office efficiency achieve twice the result with half the effort. The government affairs disclosure website mainly sets up columns such as "policies and regulations, information disclosure, public announcements, engineering construction, planning plans, institutional functions, institutional measures, and government procurement". The opening of the government affairs disclosure website is not only a specific measure to implement the "Regulations of the People's Republic of China on the Disclosure of Government Information", but also an important platform for the Shandong River Affairs Bureau to expand its external publicity influence and strengthen its social service function. With the opening of the government affairs open network, it can not only publicize the government more widely to the society and let the public understand the Yellow River, but also has great significance for promoting administration according to law, and promoting the continuous, healthy and harmonious development of government governance, development and management. It has laid a technical and market foundation for the next step to discuss the implementation of the government affairs disclosure network system at the municipal bureau level.
(4) Completed the ERP system of the National Engineering Bureau. After more than 2 months of hard work, the project software R&D personnel worked overtime. From project design, demand analysis, installation and commissioning to operation and maintenance, the development and technical personnel worked on every link of the system. After detailed analysis and design, the development process is meticulous, and it strives to diversify system functions to meet the development needs of customers to the greatest extent. The successful development of the ERP system has been praised and recognized by the application unit, accumulated experience for the R&D team, greatly improved the knowledge of the R&D team, and established a good technical support and environmental platform for the application and development of future projects.
(5) Actively negotiated and demonstrated with the Office of the Economic Bureau on the system of statistics, declaration and summary of economic conditions.
(6) Completed the IP address replacement work of nearly 50 units in Shandong Global in three days off. The IP address replacement involves multiple units and multiple departments, including routers, firewalls, Layer 3 switches, VPNs and other equipment, as well as applications The address of the system is equivalent to rebuilding a new network of Shandong Bureau. Our technicians carefully analyze the data, organize the data, contact and communicate with the Municipal Bureau and the directly affiliated units in time, and reach a consensus, so that the IP address replacement work can be successfully completed.
(7) Repaired the server of the finance department and the server of the water department of the flood control office. These two servers are quite complicated. The server of the finance department is a double-click backup. The two servers of the water department were paralyzed by virus attacks. (Accordingly, these are not ours. Scope of work), but we know that we are a service unit. When people propose it, we must try our best to solve it. Comrade Yidong and I used one night to repair the server of the financial department, and the server of the water department took 4 days to repair. Well, the leaders of the two divisions are very satisfied.
(9) Assist the technicians of the network management center to solve some network or office automation failures.
2. Some experiences in work:
(1) Establishing ideals, ideals are the basis for doing a good job, ideals can also be understood as planning, that is, planning out what things to do and what things can be done, and implement them step by step according to the plan. In practice, the plan that stays on paper is just a decoration. Only by implementing it according to the plan can we make greater achievements.
(2) Be diligent in learning, knowledge is the essence of doing a good job, knowledge can also be understood as ability, knowledge can be learned at any time and in any workplace, and knowledge obtained in practice is reliable and can be obtained. Tested. Especially now with the rapid development of society, it is necessary to have professional knowledge in order to occupy a place in the fierce and complex competition.
(3) Unity and cooperation, a lyric is written like this: Unity is strength, and the same is true at work. Only by unity and cooperation can we do a good job. How to be united and cooperate well, what I understand is to do things for others. Think about it, instead of thinking about the problem in your own head, "Humble, respectful, courteous", and don't talk about empty words and big words.
3. Deficiencies in work
(1) Knowledge is not strong enough. Whether it is software development experience and ability, or network construction and anti-virus, in-depth research is required, and many knowledge are still not mastered and familiar.
(2) The vision is not broad enough, and the problem is only considered from one's own thoughts, and the problem cannot be viewed or analyzed from the perspective of an industry, which leads to deviations in grasping and understanding things.
(3) The consideration of the problem is not comprehensive enough, and it only focuses on one thing and cannot consider extended problems.
Fourth, next year's work plan
Actively assist the section chief to complete the repair and maintenance of network failures, actively explore with software developers, and strive to reach a new level in software development capabilities and levels. Advantages, give full play to the initiative of people's supervisors, and concentrate on making the software well. In a word, focus on development and focus on development.
The parameters of the hard disk
Read policy
Write policy The data write policy of the virtual disk
and the strip size are
based on performance considerations. These three parameters are very important. How to balance the actual online environment?