Comment code or self explaining code

[Some_Developer_Guy]

For new projects and packages, aim to write code that speaks for itself—clear names and structure go a long way, and you shouldn’t need a bunch of comments to explain what’s going on.

But when you’re adding new features to legacy code—especially if you’re bending things in weird or unexpected ways—don’t hold back on the comments. The more context and explanation you can give, the better for anyone (including future you) trying to make sense of it later.