Follow+Star Public Account Number, don’t miss out on exciting content
Author | strongerHuang
WeChat Official Account | Embedded Column
It is often heard that someone says: “For such a small project like a microcontroller, why consider software architecture…”
Although microcontroller projects are small, they are still projects, as the saying goes, “Though the sparrow is small, it has all the vital organs.”
Those who have actually done projects know that without planning (software architecture), writing wherever you think will lead to either unfinished projects or painful bug fixes later…
Of course, the “software architecture” mentioned here is not comparable to large software architectures; it may just be a few dozen lines of main framework code and a few lines of module code, etc.
You will definitely retort, “I am just doing a lighting project, do I still need software architecture?”
Though lighting is simple, can you guarantee that this lighting project won’t require modifications/additions of features? For example, increasing the flashing frequency, etc.
Can you guarantee that the hardware of your project won’t change? For example, switching to a different microcontroller.
Of course, beginners often disdain software architecture, thinking they are great, only to realize their code is not good when bugs arise in the project.
(After years of coding, looking back at the code I wrote, I feel it is still quite poor)
So do we need software architecture? Below is a video that visually describes the difference between doing microcontroller projects with and without software architecture.
● Column “Embedded Tools”
● Column “Embedded Development”
● Selected Tutorials from Embedded Column
Follow the public account and reply “Join Group” to join the technical exchange group according to the rules, reply “1024” to see more content.
Click “Read Original” to see more shares.
