Skip to the content
Dorris

Word

Log

A log is the running diary your app writes about what it did, so you can find out what happened after it happened.

Also called: logs, output, console output

Every time it starts, handles a request, or hits a problem, it writes a line with a timestamp. When something goes wrong at six in the morning, the log is the only witness you have.

Reading one fluently is not a skill you need. Finding one is. Learn where your app's logs sit on your machine and where they sit once it is online, and when something breaks, copy the lines around the failure and hand the whole thing to your agent rather than your summary of it.

The mistake to avoid: customer details and keys written into logs, which get copied and pasted around.

All words

Paste this first

Something broke

I just did this: <what you clicked or typed, in a few words>
This is what I got: <paste the error here, or drag in a screenshot>

I don't know what it means. Work out what went wrong and fix it. Then tell me in one plain sentence what was wrong and what you changed, and stop.

Is this really for you?

1 of 7 Where do you sell online?
2 of 7 Would you like software built around exactly how your business works?
3 of 7 When something in your software needs changing, how do you want that to happen?
4 of 7 Have you ever written code?
5 of 7 If something breaks, what kind of help do you need?
6 of 7 Do you pay monthly for an app where you only really use one or two of its features?
7 of 7 Building your app means using an AI assistant like Claude or ChatGPT on a paid monthly plan. Are you OK with that?