Why C++ Code Failed - Common Mistakes and Best Practices

Why C++ Code Failed - Common Mistakes and Best Practices

The Cherno via YouTube Direct link

- Final thoughts and conclusion

18 of 19

18 of 19

- Final thoughts and conclusion

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Why C++ Code Failed - Common Mistakes and Best Practices

Automatically move to the next video in the Classroom when playback concludes

  1. 1 - Hello
  2. 2 - ALWAYS stack allocate if you can
  3. 3 - The cat is back
  4. 4 - API design considerations
  5. 5 - return 0 in the main function
  6. 6 - Organization and code conventions
  7. 7 - Variable intialization
  8. 8 - Deep class hierarchies
  9. 9 - Managing states
  10. 10 - defines
  11. 11 - Avoid copying causing unnessary heap allocations
  12. 12 - More on #define
  13. 13 - Consistent code style
  14. 14 - Compilation warnings
  15. 15 - Logging and release builds
  16. 16 - struct vs class
  17. 17 - Cleaner code
  18. 18 - Final thoughts and conclusion
  19. 19 - Use std::weak_ptr

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.