# Bug

Concept · [Technical basics](https://ecosystem.samcarlton.com/technical)

Also called: bugs, defect, glitch, error, issue, crash

A mistake in software that makes it behave in a way nobody intended.

**For example:** Customers who type a space after their email address cannot [log in](https://ecosystem.samcarlton.com/authentication). That is a bug.

## Connects to (8)

- [Testing](https://ecosystem.samcarlton.com/testing): Checking that software does what it should, before your users find the problems for you.
- [Technical debt](https://ecosystem.samcarlton.com/technical-debt): Shortcuts taken while building software that save time now but make later changes slower and riskier until someone cleans them up.
- [Backlog](https://ecosystem.samcarlton.com/backlog): The running list of new abilities, fixes and ideas waiting to be worked on, usually in order of priority.
- [Beta](https://ecosystem.samcarlton.com/beta): A version of the product released to a limited group of people so you can find problems before the full launch.
- [Version control](https://ecosystem.samcarlton.com/version-control): A system that records every change to the code, who made it and when.
- [Automated check](https://ecosystem.samcarlton.com/automated-check): A test or rule a computer runs to catch problems without a person looking, such as tests, type checkers and style checkers.
- [Red-green-refactor](https://ecosystem.samcarlton.com/red-green-refactor): A way of writing code in three steps: write a test that fails (red), write just enough code to make it pass (green), then clean up the…
- [TypeScript](https://ecosystem.samcarlton.com/typescript): JavaScript with types added.

Map view: https://ecosystem.samcarlton.com/bug