I have been working on embedded systems for several years, and I feel more or less qualified to summarize the pitfalls I have encountered, as well as some professional development planning issues. Combining your own experience can also give some enlightenment and mental preparation to those who are just entering the industry.
Non-superstitious technology
Technical strength needs to be improved. This is a prerequisite for completing the work on time. However, technology must not be superstitious. Embedded systems are often application-centric, and technology is only a means to achieve functions. Often the products available on the market are not always written by the best design code. The fact is that the product captures the needs of customers, so what I want to say is that there is a market first, then there is demand, and then technology can be derived. If I locate the technology at the beginning, and then determine the requirements according to the technology, and finally build the product, it will fail to a large extent. These are the lessons that several projects have taught me. Another thing is that if things are done well, the expected market feedback will not necessarily be received. The actual factor is the unfair project competition under national conditions.
Superstitious technology will only get deeper and deeper, so that the real demand cannot be seen, so that the whole picture of the entire project cannot be seen clearly, and there are various problems in what is being done.
Should not give up thinking
I also met many people on this road, and they only do the work arranged by the technical director every day, and there is nothing to think about. In the end, I did it for several years and I only wrote stm32 bare-metal code debugging driver, which was completely abolished. Really speaking, work and life really need to be handled separately, and the boss's arrangements need to be done according to the boss's will, but you must have judgment standards in your heart and know how to do better. If you encounter a stubborn boss, you can keep it. Your own opinions, but you must understand in your heart that if you do your own design, how you can do it better, this is product thinking. Once this kind of thinking is formed, when someone asks you to do something in the future, you can also afford it. You can also receive projects without relying on the company's platform and do better.
Do not forget the early heart
Stick to your own way and don't give up. This is the most important thing. In society, people are subject to various temptations, such as money, fame and fortune, etc., as well as all kinds of suspicions from others, and the boss's ears. Anyway, when the embedded system first started, even I would doubt whether I was walking in the right way, why it was so difficult, the wages were low, and the overtime work was too much, which was far worse than the Internet. But you still need to stick to the path you choose, don't care what others say, and don't listen to the boss drawing cakes there. Because everyone has their own life, no one can empathize, stick to their own path, and will not regret their choice. One's own path still needs to go step by step. The so-called morality is not coordinated, and there will be disasters. Only when one's own strength has a height that others can't reach, can you form your own influence.
1. It is said that many software engineers envy hardware engineers
2. Several communication interfaces commonly used in microcontrollers, such as I2C, SPI, UART, etc.
4.5 yuan changed to 70, hey, the chip is out of stock again
5. How does the RISC-V processor design the instruction set? What's so special
6. Macro definitions commonly used by embedded engineers
Disclaimer: This article is reproduced online, and the copyright belongs to the original author. If you are involved in the copyright of the work, please contact us, we will confirm the copyright based on the copyright certification materials you provide and pay the author's remuneration or delete the content.