1. Don&#x27;t do the compiler&#x27;s job<p>2. Larger than 0 does not mean 1<p>3. Copy once, check twice<p>4. Beware of the ?: operator and enclose it in parentheses<p>5. Use available tools to analyze your code<p>6. Check all the fragments where a pointer is explicitly cast to integer types<p>7. Do not call the alloca() function inside loops<p>8. Remember that an exception in the destructor is dangerous.<p>9. Use the &#x27;\0&#x27; literal for the terminal null character<p>10. Avoid using multiple small #ifdef blocks<p>11. Don&#x27;t try to squeeze as many operations as possible in one line<p>12. When using Copy-Paste, be especially careful with the last lines<p>13. Table-style formatting<p>14. A good compiler and coding style aren&#x27;t always enough<p>15. Start using enum class in your code, if possible<p>16. &quot;Look what I can do!&quot; - Unacceptable in programming<p>17. Use dedicated functions to clear private data<p>18. The knowledge you have, working with one language isn&#x27;t always applicable to another language<p>19. How to properly call one constructor from another<p>20. The End-of-file (EOF) check may not be enough<p>21. Check that the end-of-file character is reached correctly (EOF)<p>22. Do not use #pragma warning(default:X)<p>23. Evaluate the string literal length automatically<p>24. Override and final specifiers should become your new friends.<p>25. Do not compare &#x27;this&#x27; to nullptr anymore<p>26. Insidious VARIANT_BOOL<p>27. Guileful BSTR strings<p>28. Avoid using a macro if you can use a simple function<p>29. Use a prefix increment operator (++i) in iterators instead of a postfix (i++) operator<p>30. Visual C++ and wprintf() function<p>31. In C and C++ arrays are not passed by value<p>32. Dangerous printf<p>33. Never dereference null pointers<p>34. Undefined behavior is closer than you think<p>35. Adding a new constant to enum don&#x27;t forget to correct switch operators<p>36. If something strange is happening to your PC, check its memory.<p>37. Beware of the &#x27;continue&#x27; operator inside do {...} while (...)<p>38. Use nullptr instead of NULL from now on<p>39. Why incorrect code works<p>40. Start using static code analysis<p>41. Avoid adding a new library to the project.<p>42. Don&#x27;t use function names with &quot;empty&quot;