Follow + star our official account, don’t miss out on the exciting content
Author: HywelStar
Hello everyone, some friends previously asked about entering the embedded field and choosing a direction. Taking advantage of the weekend, I’d like to share some of my personal views, which are just my opinions.
1. Software or Hardware? MCU or Linux?
Many people struggle at the beginning: should I focus on software or hardware? Should I choose MCU or stick with Linux?
Choosing between software and hardware: There is no standard answer to this question; it all depends on personal interest. Whether you lean towards software or hardware, as long as you are willing to delve deep, there are great development prospects.
Linux direction: Strong scalability, high ceiling, and generally higher salaries. However, the learning curve is steep, with complex knowledge points and significant difficulty.
MCU direction: The semiconductor industry is currently developing rapidly, and “domestic substitution” is the trend. If you can seize this opportunity to enter a leading semiconductor manufacturer, it is definitely a very promising direction.
2. Application Layer vs. Low-Level Drivers: Different Career Development Logics
Choosing application development (Application) or low-level drivers (Driver/Kernel) determines the differences in your future career path:
Application Development (Industry-Focused):
Applications are strongly tied to business. Choosing the application layer means you must pay close attention to the “industry attributes.” The rise and fall of the industry directly determine your salary and opportunities. For example, the currently hot robotics sector is in an upward phase, and the prospects for related application development are very good.
Low-Level Drivers (Technology-Focused):
Driver development is not as deeply tied to the industry as applications; it relies more on chips and underlying technologies. This means your technical migration costs are relatively low, making it easier to switch industries. As long as you understand the underlying principles, transitioning from automotive to IoT is not too difficult.
3. About Industry and Trends
The current mainstream battlefield for embedded systems is in: automotive electronics, consumer electronics, medical, robotics, IoT, industrial control, etc.
When job hunting, while technical matching is certainly important, it is even more crucial to learn to “observe trends”. Research whether the industry you choose is currently in an upward phase, stable phase, or decline phase. The industry dividend has a huge impact on personal growth acceleration.
4. Rejecting “False Learning”, Projects are the Touchstone
There is an abundance of learning materials available now, and many people follow development board tutorials and feel they have “learned”. However, when it comes to actual interviews or work, they find they can’t produce anything.
Why? Because tutorials help you avoid all the “pits”.
How to break through?
Must have project implementation: Don’t stop at demos; have a complete project to showcase your skills.
Time and Practice: Much of the experience is gained through “stepping on pits”. Be patient, do more in your work, and absorb knowledge by solving actual bugs. In the embedded field, experience is very valuable.
In Conclusion
For beginners, I recommend choosing a direction early and producing a tangible project outcome to prove yourself;
For experienced friends, I suggest stepping out of your comfort zone and paying more attention to driver architecture, system optimization, and new technologies like edge AI.
That’s all for today’s casual discussion. If you have more questions or thoughts about embedded systems, feel free to leave a comment for discussion!
Click “Read the original text” to recharge together!