Several mistakes that IT professionals are most likely to make

1) after we graduated from school, we thought it was time to enjoy our life.. In fact, learning and enjoying life are orthogonal. We can learn and live well. There is no doubt that we live in a competitive environment. What is the basis for competition? Is our capability. Everyone should know that what we have learned in our school is not enough to become our core competitiveness in practical work. To build your core competitiveness, you must learn and learn in your spare time. Of course, work is also a learning method, but this learning method is not easy to create a lot of ability discrimination. In addition, learning is an effective way to maintain passion. I have been working in the software industry for nearly 12 years and have been working in the software industry for about 10 years. However, I still maintain a great passion for work. This is my comments from many of my colleagues, I think this is very relevant to my continued learning. Learning is something I never gave up after I graduated from school! If you learn more, you will naturally want to change something to make us passionate. When I interview someone else, I must have a question: do you usually read books? What books do you read? A person who does not read a book cannot have a high level of competence, and the depth of the problem cannot go deep. By reading books, we can accumulate knowledge and experience more quickly. Some detours we don't need to go on our own, some mistakes we don't have to make to know, some good methods and ideas do not have to think about ourselves, reading books can make us stand taller and farther. Of course, what we learned should be converted into our own.

2) think that your abilities are in direct proportion to the year of work. This idea may be incorrect in some industries, but in the IT industry. If you know about the transistor, I think the relationship between our capabilities and the year of work is more like a volt-ampere characteristic curve. At the beginning, it was linear (because we did not know anything after graduation), but it was always a saturation zone from a certain point, the changes in capabilities are very small. It should be pointed out that this curve emerged because we have adopted the same original method to treat our work since we joined our work. If we are good at changing our work and learning methods, we will not get a volt-ampere characteristic curve, but may be a line close to a straight line. If a person who has been working for seven or eight years has not formed some of his own ideas (such as design ideas), then I think there is a problem and I should think about why. The prime time for learning is the first seven or eight years.

3) unknown importance of "internal strength". Internal strength here refers to systemic analysis and view of problems, or other capabilities (such as software design capabilities ). Some people will learn this today and tomorrow, and will always like to learn new technologies. But they forget to link what they have learned to systematically master the things behind these technologies. In fact, once we learn the same thing, many things are the same, so that we can easily grasp new things quickly. Let's talk about software development and learning.Programming LanguageIt is simple, basic, and not all about software development. What software development needs to learn is how to design a good software. To do this, we must master certain principles and methods, for example, the "four features" I mentioned in "what elements should a good design have" can serve as some principles of our design. Software design capability is essential, while programming language is just a tool to express design. When our "internal strength" is better, we can learn quickly, do well, and learn deeply. This is the same as practicing kung fu.

4) Fear of changes. Embracing changes often gives us the opportunity to improve. We all have our own comfort circles, and we are afraid of changes to break our comfort circles. But the breaking of the comfort circle does not mean we do not have a comfortable circle, but it means our comfort circles are getting bigger and bigger. I dare say that some people are using Visual C ++ 6.0 for development, but now Visual Studio 2008 is the latest one (2010 is coming soon ), this is not because visual c ++ 6.0 is easier to use than Visual Studio 2008, but because we don't want to change it. We also have an excuse to say that "Visual C ++ is too classic ". The fact is that Visual Studio 2008 can help us identify problems more quickly. Don't believe it! In my opinion, the ability of a person who has the courage to embrace change is often easier to improve.