Debugging Glossary

Browse 103 debugging terms defined in plain English, from the cultural dictionary of computing.

103 Debugging Terms

AI Debugging
The process of investigating and fixing problems in AI systems, such as bad outputs, retrieval errors, prompt issues, latency spikes, or evaluation failures....
Anti-Gravity Bug
A joking term for a bug that seems to defy normal expectations or refuse to behave according to the apparent rules of the system. In engineering slang, it...
API Error
A failure response returned by an API when a request cannot be processed because of validation issues, authorization problems, missing resources, rate limits,...
Async Error
An error that occurs in asynchronous execution, often outside the original call site that scheduled the work. Async errors are harder to debug than synchronous...
Bit Flip
A change of a binary value from 0 to 1 or 1 to 0, whether in memory, storage, transmission, or conceptual debugging shorthand for a tiny state corruption with...
Boss Fight
A humorous way to describe an unusually difficult bug, migration, or technical problem that feels like the main challenge of the current project phase. In...
Break Point
A casual spelling variant of breakpoint, referring to a point where execution pauses so a developer can inspect program state. In day-to-day developer slang,...
Breakpoint Debugging Culture
A team habit of relying heavily on interactive debuggers and breakpoints rather than logs, tracing, or structured diagnostics.
Bug
An error, flaw, or unintended behavior in software that causes it to produce incorrect results or behave unexpectedly — famously named after a literal moth...
Can't Reproduce
A familiar phrase in bug triage meaning the reported issue does not appear under current test conditions. In developer slang, it can be either a legitimate...
Chase the Bug
To follow a bug through logs, environments, and code paths over time until the real cause is found. In engineering slang, chasing the bug usually implies a...
Code Archaeologist
Someone who spends significant time digging through old code, comments, and commit history to figure out why a system behaves the way it does. In engineering...
Code Autopsy
A detailed examination of code after a failure, incident, or abandoned project to understand what went wrong. In engineering slang, code autopsy suggests a mix...
Code Blindness
The tendency to stop seeing obvious problems in code after staring at the same section for too long, often because familiarity and fatigue hide mistakes from...
Code Clinic
An informal session where people bring code problems, design questions, or debugging issues for group diagnosis. In team slang, a code clinic can be a...
Code Detective
Someone who is especially good at tracing symptoms, clues, and strange behaviors back to their actual source in the code. In engineering slang, the code...
Code Doctor
A playful title for someone who diagnoses and fixes sick or fragile code. In engineering slang, the code doctor is valued for knowing how to stabilize a system...
Code Exorcist
A joking title for someone brought in to remove bizarre, haunted-feeling behavior from a system. In engineering humor, the code exorcist specializes in bugs...
Code Migraine
A problem in code that is painful, recurring, and mentally exhausting to deal with. In engineering slang, code migraine describes issues that are not just...
Code Mystery
A bug or behavior that currently lacks a convincing explanation. In engineering slang, a code mystery is what remains after the obvious theories have been...
Code Necromancy
A humorous term for reviving, understanding, or making use of ancient, undocumented, or seemingly dead code that should not still matter but somehow does. It...
Code Path
A specific route through a program's logic determined by conditions, inputs, errors, or feature flags during execution. Thinking in code paths is important for...
Code Problem
A problem or issue that arises in software code, or more informally, a coding challenge that needs to be solved. The phrase is broad, which is why experienced...
Code Puzzle
A technical problem that feels interesting and solvable through careful reasoning rather than pure chaos. In engineering slang, code puzzle is what people call...
Code Rabbit Hole
A line of technical investigation or refactoring that keeps leading deeper into complexity and side issues. In engineering slang, code rabbit holes are...
Code Surgery
A delicate, targeted code change made deep inside a fragile system where the goal is to fix one thing without disturbing everything around it. Teams use it...
Code Therapy
A humorous phrase for the emotional relief or reflective comfort some people get from coding, debugging, or cleaning up software. It can refer to both healthy...
Code Whisperer
A developer with a quiet uncanny ability to understand and calm difficult code without much visible struggle. In engineering slang, the code whisperer succeeds...
Console Log
Output written directly to a terminal, browser console, or stdout/stderr stream for debugging or visibility. Console logs are useful during development, but in...
Container Exec
The act of running a command inside an already running container, often for debugging, inspection, or one-off maintenance. Container exec is powerful but...
Container Shell
An interactive shell session opened inside a running container for inspection, debugging, or one-off commands. Container shells are useful in emergencies, but...
Correlation ID
A unique identifier generated at the entry point of a request and propagated through all downstream services, appearing in every log line and trace span....
Custom Error
An application-defined error type or structured error value that carries domain-specific meaning beyond generic runtime failures. Custom errors make handling,...
Debug Build
A Debug Build is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Debug by Prayer
A joking description of making a change with little confidence in the root cause and hoping the problem disappears. It captures debugging done under...
Debugger
A Debugger is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier to...
Debugging by Printf
A simple debugging style where a developer adds print statements or logs to inspect program state as it runs. It is basic but often effective when heavier...
Debugging Culture
The shared habits a team has around investigating problems, forming hypotheses, gathering evidence, and learning from failures. Strong debugging culture values...
Debugging Tool
A Debugging Tool is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Debug Mode
A mental or operational state focused on investigation, visibility, and root-cause tracing. In engineering slang, switching into debug mode means normal...
Debug Symbol
A Debug Symbol is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Easter Egg Hunt
Easter Egg Hunt in technology refers to the practice of searching for and discovering hidden features, messages, jokes, or secret content intentionally...
Emoji Debugging
A playful style of tracing program flow by sprinkling logs with distinct emojis so events are easier to spot visually in noisy output. It is informal but...
Error Boundary
An Error Boundary is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Error Code
An Error Code is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Error Correction
An Error Correction is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Error Handling
An Error Handling is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Error Log Reading
The practical art of extracting signal from noisy logs during debugging and incident response. In engineering slang, good error log reading is an...
Error Recovery
An Error Recovery is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code...
Error Type
An Error Type is a development concept used to shape how software is built, executed, or maintained in real systems. Developers rely on it to make code easier...
Exception
An abnormal condition that disrupts the normal flow of a program's execution. When raised (or thrown), an exception propagates up the call stack until it is...
Git Bisect
A Git command that performs a binary search through commit history to find the exact commit that introduced a bug. You mark a known-good commit and a known-bad...
Grep Everything
A brute-force debugging or exploration tactic of searching the entire codebase or log set for anything that looks relevant. It reflects how often plain text...
Heisenbug
A software bug that vanishes or changes behavior when you attempt to observe or debug it. Named after Heisenberg's uncertainty principle, because the act of...
Heisenbug
A bug that disappears or changes behavior when you try to observe or debug it — named after Heisenberg's uncertainty principle. Common causes: race conditions...
Inspector
A development tool for examining and modifying the structure, styles, and behavior of a running application in real time. Browser DevTools' Element Inspector...
It's Always DNS
It's Always DNS is a running joke in the IT and DevOps community expressing the observation that a surprisingly large proportion of mysterious network...
It Works On My Machine
The classic developer defense when a bug can't be reproduced locally. Highlights the gap between development and production environments. The entire...
Leak Detection
The process or tooling used to identify memory leaks — allocations that are never freed and accumulate over time — or resource leaks such as unclosed file...
Log Diving
Digging through logs in search of clues about system behavior, usually deeper and longer than anyone hoped. In engineering slang, log diving is part...
Log Everything
A blunt operational instinct to emit as much diagnostic information as possible so incidents become easier to reconstruct. It reflects a real need for...
Logging
Logging is the practice of recording timestamped events, errors, warnings, and diagnostic messages from a running application to structured or unstructured...
Log Level
A severity classification assigned to each log message — typically DEBUG, INFO, WARN, ERROR, and FATAL (in ascending severity) — allowing operators to filter...
Memory Profile
A snapshot or time-series recording of a program's memory usage, showing allocation sizes, frequencies, call sites, and object lifetimes. Tools like Valgrind's...
Mitmproxy
An interactive proxy used to inspect, modify, and debug HTTP and related traffic in transit.
More Logs
A common reflexive answer to uncertainty in debugging, often sensible and sometimes overused. In engineering slang, 'more logs' is both a practical move and a...
No Repro
Short for 'no reproduction,' meaning a reported bug could not be made to occur again in the current test environment. It often signals an environment mismatch,...
Observability
Observability is the ability to understand a system's internal state by examining its external outputs, primarily through three pillars: logs (event records),...
Pair Debugging
A debugging practice where two people investigate a problem together, combining context, observation, and reasoning in real time. It often works well for...
Performance Profiling
The practice of instrumenting a running program to measure where time and resources are spent — typically producing flame graphs, call trees, or hot-spot...
Pretty Print
To format data — typically JSON, XML, code, or data structures — with consistent indentation, line breaks, and syntax highlighting so that it is...
Print Debug
To debug by adding print statements or simple output rather than using more advanced tools. In engineering slang, print debugging is humble, effective, and...
Profile
To measure where a program spends its time and memory, identifying bottlenecks. Profilers instrument code to collect metrics — CPU time, memory allocations,...
Profiler
A tool that measures where a program spends its time and memory, typically by sampling the call stack at intervals or instrumenting function entry/exit....
Profiling
Measuring the resource consumption (CPU time, memory, I/O, function call counts) of a program to identify performance bottlenecks. CPU profilers show which...
Race Detector
A dynamic analysis tool that instruments memory accesses at runtime to detect data races — unsynchronized concurrent reads and writes to the same variable....
Read the Source
A direct suggestion to inspect the actual implementation rather than relying on guesswork, docs, or assumptions. In open-source and library-heavy work, it is...
Red Herring
A clue or explanation that looks important but turns out to distract from the real issue. In engineering slang, red herrings are what make debugging feel like...
Resource Leak
A defect in which a program acquires a system resource — file descriptor, database connection, socket, memory allocation, thread — but fails to release it,...
Root Cause
The underlying reason a problem occurred, beyond the immediate symptom that first drew attention. In incident work, finding root cause matters because treating...
Rubber Duck
Rubber Duck Debugging is a problem-solving method where a programmer explains their code line by line to an inanimate object (traditionally a rubber duck) to...
Rubber Duck (AI)
Using an LLM as a rubber duck — explaining your bug to ChatGPT or Claude instead of a plastic duck. The AI actually responds, which is either more helpful or...
Rubber Duck Conference
Rubber Duck Conference is a humorous concept in developer culture referring to the idea of an entire conference dedicated to the art of rubber duck debugging,...
rubber duck debugging
A debugging technique where a programmer explains their code line-by-line to an inanimate object (traditionally a rubber duck), often discovering the bug in...
Rubber Duck Debugging
A debugging method in which a programmer explains their code, line by line, to an inanimate object (traditionally a rubber duck), and in the process of...
Rubber Duck DNS
Rubber Duck DNS is a humorous tech community concept combining two beloved debugging traditions: rubber duck debugging (explaining your problem to a rubber...
Rubber Ducking
The practice of explaining a bug, design, or code path out loud, often to a rubber duck or other inanimate listener, in order to expose hidden assumptions and...
Rubber Duck (slang)
Used as a verb: 'I rubber-ducked the problem and found the bug.' Means to explain your code out loud to find the issue — whether to an actual duck, a...
Rubber Duck Test
The practice of verifying a business idea, feature spec, or architectural decision by explaining it to someone (or something) uninitiated. If you can't explain...
Runtime Error
An error that occurs while a program is executing, as opposed to at compile time or during static analysis. Common examples include null pointer dereferences,...
Second Opinion
Another qualified person's view on a problem, design, or decision. In engineering slang, a second opinion is often the fastest way to break a team's local...
Shotgun Debugging
A debugging style where many unrelated changes are tried rapidly in hopes that one will fix the issue, rather than isolating the cause systematically. It often...
Sneaky Bug
A defect that hides well because it appears only under particular conditions, looks like something else, or leaves weak clues in logs and tests. The phrase...
Stack Frame
A contiguous block of memory on the call stack created each time a function is invoked, containing the function's local variables, saved registers, the return...
Stack Trace
A sequential list of the active function calls (stack frames) at the point an exception was thrown or a breakpoint was hit, showing the chain of callers from...
Stack Trace Slang
A loose or humorous use of 'stack trace' to mean any visible trail explaining how something went wrong, even outside literal program call stacks. It reflects...
Stepper
A debugger feature that executes code one statement, line, or instruction at a time, allowing the developer to observe state changes at each step. Common...
Time Travel Debugging
A debugging technique that records every state change during program execution, allowing the developer to step backward and forward through time to inspect the...
Trace
A record of a request's journey through a distributed system, composed of spans (timed operations) connected by parent-child relationships. Each span captures...
Trace
A record of the execution path through a system, capturing the sequence of function calls, service hops, or operations. In distributed systems, a trace follows...
Trophy Bug
A particularly difficult or impressive bug that engineers feel proud to have found or fixed. In engineering slang, trophy bugs become stories people retell...
Unreproducible Bug
A bug that is known to exist from reports or evidence but cannot be consistently reproduced on demand, making diagnosis and fix validation difficult. These...
Where's Waldo Bug
A bug that is especially hard to spot because it hides among many distractions. In engineering slang, a Where's Waldo bug is the one tiny wrong thing buried in...

Related Topics