Comentarios y sketches limpios

Code is read far more often than it is written. Comments are notes you leave so future-you understands the sketch. 📝

Type two slashes and the rest of that line is a comment. The board ignores it completely when running your code.

You can drop a comment after real code on the same line. It explains that exact step without breaking anything. Handy for quick context.

For longer notes, wrap text between a slash-star and star-slash. This block can span several lines and is great for descriptions.

Anything inside a comment is invisible to the board. It is purely for readers, so it never affects how your device behaves.

Good comments say why a line exists, not just what it does. Note the reason, since the code already shows the action.

Lines inside braces should be pushed in a few spaces. This indentation shows what belongs together and keeps logic easy to scan.

A clear name beats a comment. Calling a pin ledPin instead of just a number tells the reader exactly what it controls.

Temporarily disable a line by adding slashes in front. Commenting out lets you test without deleting code you might want back.

Do not narrate every line. A comment like adding one to x adds clutter, not value. Save notes for the parts that truly need explaining.

Tidy spacing, clear names, and useful comments make a sketch easy to fix months later. Readable code is reliable code.

Let's check what a comment does.

You learned to use comments with // and slash-star, indent inside braces, and name things clearly. Readable sketches stay easy to maintain. 🎉