Adding my 2 cents over a number of otherwise good advice: know your tools, maintain them. I have worked years on embedded SW. Often the tools suck: - complicat

Adding my 2 cents over a number of otherwise good advice: know your tools, maintain them. I have worked years on embedded SW. Often the tools suck: - complicated or unreliable build - debugging with traces, sometimes traces are not even reliable - slow flashing - low acceptance of verification: Valgrind (on target), Coverity (on host) - and worst of all: unreliable hardware. Of course each of those items teach you something, although that's mostly patience and rigor :) Suggestions to keep high efficiency, high motivation: - maintain your build, fix it when partial build is broken (no "make clean all"). - optimize flashing speed - find and use a good code indexer - find/buy tools that will help you find bugs early: Valgrind and Coverity are in this category