Artwork

Content provided by Ross Hunter and The New Best Practices. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Ross Hunter and The New Best Practices or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Code Comments

54:01
 
Share
 

Manage episode 197174641 series 1981042
Content provided by Ross Hunter and The New Best Practices. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Ross Hunter and The New Best Practices or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Outline

  • Definition of comments: “Metadata in source code that describe what code fails to communicate. Some languages and frameworks opt to use the mechanism of comments as formal documentation for code, but these two concepts should be separated.
  • Strive to make code self-documenting
  • Formal Documentation vs. Code Comments
  • Using tests to document your code
  • Considering strong types as a type of documentation
  • Docstring Tests
  • The value of documenting types
  • Worthless comments should be avoided
  • Don’t use comments to “vent” your emotions

Links

  continue reading

9 episodes

Artwork
iconShare
 
Manage episode 197174641 series 1981042
Content provided by Ross Hunter and The New Best Practices. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Ross Hunter and The New Best Practices or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

Outline

  • Definition of comments: “Metadata in source code that describe what code fails to communicate. Some languages and frameworks opt to use the mechanism of comments as formal documentation for code, but these two concepts should be separated.
  • Strive to make code self-documenting
  • Formal Documentation vs. Code Comments
  • Using tests to document your code
  • Considering strong types as a type of documentation
  • Docstring Tests
  • The value of documenting types
  • Worthless comments should be avoided
  • Don’t use comments to “vent” your emotions

Links

  continue reading

9 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide