If you're wondering what makes a good firmware, it's not about maths and language, although they are an important skill to have. It's about pure common sense, or in my terms "coding sense". The real world where machines and controllers interact with is far from the ideal scenario. My coding philosophy is to keep things simple and to always keep Murphy's law in mind. An example, was when I took over a failing automated barrier project, where the automated barrier is hitting on vehicles. The fix is as simple as adding a simple digital sampling on the loop detector's input. If you're looking for the average coder, who's all about theory and jargons, I'm not the right fit for you. But if you're looking for someone who believes in simple yet logical coding that has high portability and ease of maintenance, then let's talk. After all, firmware development is not only about creating lines of error-free code, but also solves problems in an elegant manner.