Reproduce one problem
Why it matters: Trim the sample until it still shows the issue but no longer includes unrelated project code.
Code-sharing guides for useful technical reviews
Good code sharing preserves more than indentation. A reviewer needs the runtime, expected behavior, relevant inputs, and a safe amount of surrounding evidence. This collection focuses on reproducible, reviewable artifacts.
Code Sharing at a glance
A reviewer needs a reproducible example, the relevant environment, and an explicit expected result.
Name the environment
Why it matters: State the language, runtime, command, input, expected result, and actual result a reviewer needs.
Keep the final fix elsewhere
Why it matters: Use a paste for discussion, then move lasting code and decisions into version control or documentation.
Code Sharing learning path
Practical guides for sharing code snippets, diffs, logs, SQL, and reproducible bug reports without losing technical context.
How to Share Code Online Without Losing Formatting
Preserve indentation, runtime context, expected behavior, and a reproducible example while removing secrets and project details the reviewer does not need.
Read guide →How to Share Error Logs Safely and Usefully
Share the smallest useful diagnostic window, preserve timestamps and causal stack frames, redact secrets consistently, and expire the link after the incident.
Read guide →How to Share SQL Queries for Review
Give reviewers the SQL dialect, minimal schema, representative synthetic rows, expected result, and relevant plan without exposing production data.
Read guide →Command-Line Paste Workflows with curl
Create paste links from curl or trusted shell scripts with explicit JSON, timeouts, safe token handling, status checks, and bounded retries.
Read guide →How to Create a Minimal Reproducible Example
Reduce a software problem to the smallest runnable example with the environment, exact command, input, expected result, and actual result included.
Read guide →How to share large text files online
Measure, trim, split, redact, and share large logs or text files online within a 1 MB paste limit - And know when object storage is the better tool.
Read guide →Direct answers for this topic
How small should a code example be?
Remove unrelated code until the example is short but still reproduces the same behavior with synthetic inputs. Read the complete explanation.
Which logs help a reviewer?
Include the lead-up, complete error, correlation values, and short aftermath while removing credentials and personal data. Read the complete explanation.
When is a repository better than a paste?
Use a repository when review needs multiple files, executable history, authorship, tests, branches, or a durable final change. Read the complete explanation.
How to use these guides
Start with the minimal-example guide, add only the log or runtime context needed to reproduce the fault, and move the accepted fix into version control.
Try the paste editor →