layman/terms
When things break

Log

log

In shortA running record a program writes of what it's doing, used to find out what happened when something goes wrong.

A ship's captain writes down everything: the weather, the speed, every course change. If anything goes wrong, the logbook tells the story.

A ship’s logbook records everything on a voyage: times, weather, speed and every change of course. Most of the time, nobody reads it. But when something goes wrong, it’s the first place anyone looks.

A log is that logbook for software. It’s a running record a program writes about what it’s doing: who signed in, what was saved, what failed and when.

What a log line looks like

2026-03-14 09:12:03 ERROR Payment failed: card declined

Why they matter

When a customer says “it broke at about nine”, the log shows exactly what happened at 09:12. Without logs, debugging is guesswork.

What it isn’t

It isn’t the same as the data an app stores. Logs are notes about what the app did, not your account or your orders.

Where the comparison breaks down

A captain writes a few lines a day. A busy app can write millions of log lines an hour, so teams use special tools to search them.

How the words fit together

Logs record events. An error message is what the user sees. A stack trace in the log shows exactly where the code failed.

Watch out

Logs should never contain passwords, card numbers or other secrets. It's a common mistake. Logs are often read by more people than you'd think.

When you'll hear it

“Check the logs.” Read the program's running record to see what happened.

“There's nothing in the logs.” The program didn't record anything useful about the problem.

“Turn on debug logging.” Make the program write down much more detail, to help find a problem.

Say it in a meeting

“When something goes wrong, can we see what happened from our logs?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Watch a log file live ↗