add the stop using dd guide page

[carlos-granados]

Adds a User Guide page arguing the case for step debugging over dd(), placed between Watches and Edits and Logging.

The argument is built so it never calls the reader lazy — printing is treated as the rational response it was:

• Why it made sense — hard to install, slow, and therefore not there when you needed it. The third is the load-bearing one: because it was slow it stayed off, so hitting a bug meant stopping and reproducing it, by which time printing had already answered.
• What changed — the same three answered in order, closing on the point that the debugger being off when you needed it was what made printing worth it.
• What printing cannot do — eight concrete scenarios rather than feature names: everything in scope instead of what you guessed, the caller's variables, carrying on afterwards, watching a value change, stopping on the one iteration that matters, catching a throw before any catch, changing a value to reach a branch, and debugging requests whose output you never see. Plus the one nobody mentions: a dd() can be committed, a breakpoint cannot.
• When it is still fine — kept genuinely fair. The line drawn is that printing suits a question you already know the shape of; moving the call, adding a second, or running a third time means you have started searching.
• Worth reconsidering — the ask, framed as trying one breakpoint rather than a conversion.

Each item links to the guide page covering the mechanism; all four deep anchors were verified against the built HTML.

Note: Docusaurus frontmatter titles are plain text, so dd() in the title and sidebar is not monospaced. Getting backticks there would require an in-content h1, which would disable the page-title-in-TOC behaviour the site's ejected TOC components provide.

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-09-14 16:04 UTC