System Check: Which Microcontrollers Do You Use and Why?

System check! Elektor wants to know: Which microcontroller family do you use most often? How often? What matters most when you select a microcontroller for a new design?

Create your own user feedback survey

Past Results

In the last System Check, we asked community members what frustrates them most during a typical engineering project? Here are the results.
  Engineering projects rarely fail because of a single technical challenge. More often, they slow down under the weight of shifting priorities and unclear expectations. In our recent System Check, the biggest frustration reported by engineers was changing requirements midway through development (27%), closely followed by excessive meetings and status updates (27%). Tight deadlines with limited resources (25%) also ranked high, while poor documentation or specifications (18%) remained a concern. Interestingly, only a small percentage pointed to debugging someone else’s code or design (5%) as their primary frustration. It seems pretty clear that engineers want more time to engineer. They want to spend less time navigating moving targets and process overhead.

When asked about the root causes of project delays, respondents overwhelmingly pointed to unclear or incomplete requirements (29%). This finding aligns closely with the frustrations identified above and reinforces a long-standing lesson in engineering management: problems discovered late are often requirements problems in disguise. Underestimating technical complexity (22%) and poor communication between teams (18%) were also major contributors, while resource shortages (15%) and scope creep (15%) followed. For engineering leaders, it seems investing more effort upfront in defining requirements, aligning stakeholders, and maintaining clear communication may not be as exciting as adopting the latest technology, but it remains one of the most effective ways to keep projects on schedule.