A bug in computing is a problem, error or issue that produces incorrect results or behaviour.

Today, you will learn how to talk about errors & bugs:

• Part 1: Explaining errors - what, where, when, why

• Part 2: Reproducing a bug

• Part 3: Modals - could vs. should quiz

PART 1: STRUCTURE

Explaining Errors

When explaining errors, be as clear as possible. Use this format:

1. What happens: The app crashes

2. Where it happens: on the dashboard page

3. When it happens: when a user clicks the profile picture

4. Why it matters: It’s preventing users from accessing or updating their profiles

PART 2: VOCABULARY

Reproduce a bug

To reproduce a bug means to try to make the bug happen again in order to solve it.

• If we can’t reproduce the error, it will be difficult to fix.

• Please provide the steps to reproduce the issue so we can investigate it.

• Can you reproduce the bug and send me the logs?

PART 3: GRAMMAR

Could vs. Should

Modal verbs are used to express different conditions.

When to use could vs. should when talking about issues?

Could → something possible but not certain
e.g. The bug could be caused by a missing config file.

Should → something expected
e.g. The user should be taken to the home page when they click this button.

Can you understand modals to a C1 level?

RECOMMENDATION

Writer RAG tool: build production-ready RAG apps in minutes

• Writer RAG Tool: build production-ready RAG apps in minutes with simple API calls.

• Knowledge Graph integration for intelligent data retrieval and AI-powered interactions.

• Streamlined full-stack platform eliminates complex setups for scalable, accurate AI workflows.

Learn more about our production ready RAG tooling here.

THAT’S ALL FOR THIS WEEK. WHAT NEXT?