Entering the embedded industry with a dream of technology, only to find a huge gap between reality and ideals. Here are several common misconceptions that new engineers are likely to have.
1. Work Content: Not Writing Code Every Day
Fantasy: Focus on researching advanced algorithms and writing core code.
Reality: Most of the time is spent reading old code, debugging hardware, modifying parameters, and writing documentation.
2. Development Rhythm: Debugging Dominates Everything
Fantasy: Smooth coding and quickly implementing features.
Reality: 80% of the time is spent debugging, and 20% writing code. Unstable hardware, abnormal signals, and timing issues are the norm.
3. Skill Focus: Proficiency in Both Software and Hardware is Required
Fantasy: Strong software skills are enough; someone else handles the hardware.
Reality: You must understand hardware. You need to be able to read schematics, analyze signals, measure waveforms, and even solder and follow production lines.
4. Collaboration Mode: Not a Lone Wolf
Fantasy: Quietly writing code and conversing with the computer.
Reality: Frequent communication with hardware, structure, testing, and product managers; meetings and discussions take up a significant portion of time.
5. Development Environment: Not the Latest and Coolest
Fantasy: Using the latest architectures and trendy technologies.
Reality: Mostly old chips and architectures focused on stability. Code standards are strict, prohibiting flashy operations, emphasizing reliability and maintainability.
6. Growth Path: Slow and Twisted
Fantasy: Being technically skilled leads to rapid promotion.
Reality: Growth depends on project experience accumulation and problem-solving abilities. It requires immense patience, starting from fixing small bugs.
This article is an original piece by Wanyi Education, please indicate the source when reprinting!