Embedded Linux system software development

If the underlying software developers and all programmers want to design the software well (with good structure and portability) and adapt to changes in new projects, they must follow the following principles: & middot; the most important thing is to understand the basics.

The underlying software developers and all programmers should follow the following principles if they want to design the software well (with good structure and portability) and adapt to changes in new projects:

· The most important thing is to understand basic concepts (such as operating systems) and master the design principles (such as interface layering ).

· Second, experience accumulation. Practical experience is more valuable than book knowledge, which can greatly improve the efficiency of subsequent work and learning.

· Third, focus on new software technologies to improve your understanding of software design.

It should be noted that a complete and fixed learning route is difficult to determine. One is that it varies from person to person, and the other is that technology advances rapidly.

This was taken from the top of todaygood's blog. todaygood's learning efficiency is higher than mine. maybe it's better to train people in a work environment. In terms of the learning philosophy of embedded system software development, our views are consistent. I still pay attention to these three aspects. Basically, during the daytime, I learned how to summarize and improve my learning methods based on my accumulated project experience, in the evening, I will study the software design basics and theoretical basics. The rest time interspersed in the middle can be used to create forums, read blogs, pay attention to new software technologies, and learn how such technologies are developed.

Of course, the premise of these work is to determine a basic knowledge system framework, lay a good foundation for the framework during the school period, and expand as much as possible. After the work, we will continue to refine the work to form expertise. This is my learning philosophy.

One thing to add is that you need to learn to write documents for two reasons. First, you need to exercise your expression skills. if you can understand your skills, you can write a document to see whether it can be understood by others. if you can, this proves that your understanding is in place. at the same time, you can find the blind spots you understand through discussion and deepen your understanding. second, you can back up your technical experience and use them quickly when necessary, you don't need to waste a lot of searching time on the internet. if the system goes down, you can quickly restore it. it can be said that this is your own experience and wealth, and you can manage these resources, it is of great help to you.