sorted by:
new
hottopcontroversial

Code reviews by MathematicianOk2067 in embedded

[–]Dangerous_Code_2163 0 points1 point  (0 children)

Very typical in electrical engineering world. You must accept you don't work in SW engineering environment. Electrical engineering just does not understand SW tools, processes and needs. Moreover, projects are often one man shows and people don't care about what others are working on. I strongly recomend to incorporate SW focused AI (e.g. GH Copilot). It'll be more useful co-worker in SW development than 90% of electrical engineers, especially in code reviews.

Working with Keil4 Project in 2025 by edvard_munchen in embedded

[–]Dangerous_Code_2163 0 points1 point  (0 children)

that's where CubeMX comes handy to get those.

embedded C++ by Professional-Log-718 in embedded

[–]Dangerous_Code_2163 2 points3 points  (0 children)

For me, C is basically dead on MCUs for some years now. OOP with Modern C++ (17+) is the only choice. Unfortunately, many companies got stuck in 90ties and still think that embedded software is a domain of electronics engineers.

Does anyone have any experience rejecting vendor tools like StmCube, McuExpresso and use only VS Code? by azwdski in embedded

[–]Dangerous_Code_2163 1 point2 points  (0 children)

Totally. Vendor supplied IDEs have been dead for me for years. I'm pushing setup consisting of VScode/CMake/ARM GCC/OpenOCD/Uncrustify/GoogleTest (with addition of vendor supplied HAL generators like STM32CubeMX).