Design Patterns for Embedded Applications

Get the full course on Udemy at www.udemy.com/course/object-o...
Recently, I conducted a poll on LinkedIn, asking a vibrant tech community, that “Which Programming language or languages they thought was, or were most dominantly used in F35 aircraft” out of Ada, Java, C/C++ and Python.
The majority picked the C and C++ combination and that is quite right, as far as the question goes. Because, according to various sources that are available online, the millions of lines of code that power the F35 fighter jet - one of the most advanced fighters at this time, has about 53% of its code written in C language. 35% written in C++, 7% in Assembly language, and just 5% written in Ada.
But there is another aspect of looking at this poll data. And that is, more than half... precisely speaking, 54% of the community, is wrong here. In fact, I was expecting, that C and C++ will have a tie against Ada. You can well understand, how I felt by looking at Python at the second number? the choice of 29% of voters. Nothing against Python as a programming language, but it is not used for this kind of purposes. At least, at this time.
To me, it simply shows that the majority is not right in this case. Perhaps, the huge number out there in the software industry, doesn’t know the embedded world well enough.
You can find so many people telling, how to design your software, and what the best practices are in this field. So, the question arises that, how much does the advice on software design is valid for embedded software or firmware development?
After all, they seem to be the same thing, from many perspectives…
Let's find out the answer to this question in this course with practical examples, and nuances to consider for.