The delete key is your friend. The less code you have, the less code you have understand, the faster the remaining code runs, and your builds will be done sooner. Omit needless junk, aggressively get rid of crap you don’t need, trash that “someday maybe this will be useful” stuff.
The probability of a disk failure is directly proportional to the amount of code that you have checked out but not committed. (I really like source code control systems that make branches and undo operations natural and cheap).
There is a special place in Hell reserved for engineers whose code works the first time.
Effective code review practice #1: “Of course we think that #define is clever.” [Sound of shotgun racking a fresh round, and a dog whines in anticipation]. “We’ll give you five minutes of keyboard time to clean it up to our satisfaction, or a fifty yard head start, your choice.”
When the clueless HR type on the other end of the phone (who is doing screenings) asks if you know “Object-oriented, real-time programming,” just say “Yes.” Don’t try to explain. They think they are asking you if you know how to do “Garbledly shuggoth rumplestiltskin-sh’bop,” and explaining that shuggothery and sh’bop are really aspects of the same narkle-qwerty-doo-wah-wah is just going to make them think you don’t know what you’re talking about. I’m just sayin’.