Los símbolos de puntuación en inglés: nombres y ejemplos para developers

I end every commit message with a — it's our style guide rule.

This separates the two parameters so the function knows where one argument ends and the next begins: foo(a, b)

I added a at the end of this line because our linter's style guide requires it, even though JavaScript doesn't need it: const x = 5;

This right after the variable name declares its type in TypeScript: let age: number

The bug is right after the on line 12 — it negates the check, so the function runs when it shouldn't: if (!isReady) { ... }

This right after 'user' is doing optional chaining — it stops the error when user is null: user?.profile?.avatar

This review comment says the error message isn't informative — I used an to write the contraction 'isn't'.

In this JSON file, wrap every key and string value — single quotes aren't valid here: {"name": "Alice"}

I changed the string from double quotes to because our linter prefers them for this project: 'Alice'

The between 'kebab' and 'case' is just part of the naming convention for this CSS class: kebab-case-example

This between 10 and 15 means a numeric range in the documentation, not a minus sign: pages 10–15

I added an here to insert a side comment into the sentence without a full parenthetical: She opened the PR—without running the tests—and merged it.

These right after the function name are what actually calls it — without them, you're just referencing the function: doSomething()

The crash is happening inside those — we're accessing index 5 on an array that only has 3 items: items[5]

Those three dots — the — are the spread operator here, copying every item from the old array into the new one: [...oldArr, newItem]

The syntax error is because the never get closed — the function body has no matching brace: function run() { console.log('hi');

Those around 'string' are declaring the generic type for this array in TypeScript: Array<string>

Every in this URL marks the start of a new path segment: /api/v1/users

I added a right before the quote to escape it, otherwise the string ends too early: "She said \"hi\"."

That in the glob pattern matches any file in this folder, no matter the name: **/*.ts

The condition never passes because there's only one instead of two — it's being read as a bitwise AND, not a logical one: if (isValid & isReady)

I added the before her username in this comment so she gets notified about the review: @alice can you take a look?

That at the start of the line turns everything after it into a comment in Python — it's ignored when the script runs.

This is the modulo operator here — it returns the remainder after dividing 10 by 3: 10 % 3 === 1

That before HOME tells the shell to read it as a variable, not as literal text: echo $HOME

I renamed the variable to use an between each word instead of camelCase, since this file follows snake_case: user_id

That is sending the output of grep straight into wc so we can count matching lines: grep 'error' log.txt | wc -l

That before the version number means npm can install any compatible patch update, nothing bigger: ~1.2.3

I switched to using a here because we need to interpolate the variable directly inside the string: `Hello, ${name}!`

That in package.json means npm can install any newer compatible minor version, not just patches: ^2.0.0