A new heath project has recently been launched and heath is familiar this week with some of heath's development documents, the volume, the content and the quality of the documents. It is indeed worth learning by many manufacturers, and it also has a lot of awareness and confusion。
For the ic industry, where the technology is so rapidly being updated, the technology is constantly being updated, from the armv7 structure to the armv8 structure, and now the m series, based on low-capacity, real-time processing, with an increasing number of platforms being updated on a daily basis, with each manufacturer treating each platform differently. Now, for example, the mainstream is using the android architecture for mobile terminals, and in the case of the current mainstream producers, the gothon, mtk, exhibition, and all-in-the-development models are based on kernel+android, but each one of them has a lot of differences for people at the bottom of the line like us。
In the case of development models, which are determined by the market location of the product and the competitiveness of the product, the service needs to be better, with fewer development cycles for clients and fewer requirements for high-quality software engineers. To go to the big platform, where we can get access to newer technologies, to a better division of labour, and to a deeper understanding of technology, the small platform needs us to endure loneliness, to think more about work, to do more, to do better, and to spend more time and effort to absorb them. Large companies, which may eventually develop well, will become technical experts in this field, while small firms will move more to the systemic level。
Having access to heath, i found that a new model might be coming closer, on the one hand, as each manufacturer now emphasizes its core competitiveness, and on the other hand, as the algorithms for artificial intelligence, etc., become increasingly core competitiveness for a company, and, on the other hand, as the system becomes more complex, the platforms become more and more, the requirements for manufacturers to reduce the version, the compatibility of the platform, etc., emerge in the abstract of the platform. The following development models will become normal for us, and the following development models will become normal for us, as shown below
What's in this development model? What can we do
What about me? Look at the manual, look at the manual, look at the manual, say the important things three times. What's going on in the manual? So we're going to understand the rationale for these things, like that thing that's operating in an unknown library, and the results are different, and then we're going to have to end up at the bottom, what is the image of the hardware, the register, and we're going to look at it through the register, and we're going back to the process。
Work on bottom development, regardless of the company, is now largely based on secondary development provided by the chip manufacturer, and perhaps most of the work is based on some of the most basic adjustments and transfers. So how can we do better than being a business engineer, we all face a team that is too busy without training, too busy working hours, too busy learning time, and ali's technocratic life has come up with a lot of advice, all in all, to do more, to do better, to do exercise, for us, we need to be at the foundation of our technology, and we need to build the foundation to be safe in this renewal。
