Skip to content

Code documentation

↑

Prefer self-explanatory naming; write comments when they add reasoning the code cannot show. Document public contracts precisely, including behavior, invalid inputs and meaningful exceptions.

Start with one concept, work through a small example, and verify your prediction. Follow linked topics when a prerequisite or related idea needs more explanation.

Articles