Evidence
Evidence is information, observations, or material used to support, challenge, or assess a claim, conclusion, event, or outcome.
Writing for Developers: Blogs that get read
Detailed observations, measurements, artifacts, and test results used to reconstruct the causes of a software failure.
- How it is used
- Supports technical claims and bug investigations by giving skeptical readers inspectable grounds for judgment.
- How deep it goes
- Defines evidence broadly, gives replacement patterns, and catalogs diagnostic artifacts without teaching their underlying tools or analysis.
- Examples
- Uses benchmarks, code samples, monitoring graphs, flame graphs, tracing data, attempted fixes, dependency graphs, and memory tests.
- What you can do after
- Diagnose/debug with it by collecting artifacts and testing arguable explanations against concrete results.
Read how Writing for Developers: Blogs that get read explains evidence →
Timeless Algorithms, The Foundational Ideas
Evidence is information or observations considered in support of a claim or conclusion.
- How it is used
- Uses observations to update hypotheses and support decisions under uncertainty.
- How deep it goes
- Explains Bayesian updating and hypothesis-test conclusions while stopping short of treating either outcome as certainty.
- Examples
- Uses medical diagnosis and testing, plus a courtroom acquittal analogy, to illustrate evidential limits.
- What you can do after
- Evaluate conclusions in proportion to evidence, state uncertainty, and avoid claiming more than a test establishes.
Read how Timeless Algorithms, The Foundational Ideas explains evidence →
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
Information that helps identify the location and cause of a software defect.
- How it is used
- Directs debugging toward the real defect location after triage and before isolation.
- How deep it goes
- Defines evidence, lists operational sources, and stops short of prescribing a fixed collection procedure.
- Examples
- Uses logs, error reports, request traces, user reports, Kubernetes tooling, call stacks, and code version metadata.
- What you can do after
- Diagnose/debug with it by narrowing investigation toward the real defect location.
Fabulous Adventures in Data Structures and Algorithms
Evidence is an observed fact or data value that changes the probability assigned to a hypothesis or event.
- How it is used
- Updates beliefs about causes after observing effects, supporting diagnosis and evidence-based decisions.
- How deep it goes
- Explains evidence through priors, likelihoods, joint distributions, filtering, projection, and posterior computation, including counterintuitive base rates.
- Examples
- Uses cold-and-sneezing survey data, a rare-disease medical test, and repeated coin-flip observations.
- What you can do after
- Apply Bayesian reasoning in probabilistic programs to compute posterior beliefs from priors, likelihoods, and observations.
Read how Fabulous Adventures in Data Structures and Algorithms explains evidence →
Architecting Autonomous Agentic Systems
Information or an artifact retained to support claims and reconstruct an interaction after completion.
- How it is used
- Defines what must remain after a bounded agentic interaction to support accountability and reconstruction.
- How deep it goes
- Explains evidence qualification and event correlation, including where artifacts may reside, without specifying an evidence-store implementation.
- Examples
- Uses a production-lot investigation and a retailer–supplier dispute to illustrate retained records and candidate evidence.
- What you can do after
- Evaluate whether linked records can explain an action and whether candidate material is qualified for its intended use.
Read how Architecting Autonomous Agentic Systems explains evidence →
Designing AI Agents
Information that supports or substantiates a claim or decision.
- How it is used
- Uses evidence to establish action outcomes, support governance decisions, and reconstruct failures.
- How deep it goes
- Details acceptance records, staged checks, trust escalation, and incident investigation, including latency and state-change limitations.
- Examples
- Uses dry runs, deployment return statuses, critic findings, and an excess-coupon incident to illustrate different evidence needs.
- What you can do after
- Diagnose/debug with evidence by tracing a proposal through policy decisions to business outcomes and creating regression cases.
Data-Oriented Programming in Java
Evidence is information that demonstrates that a required data condition or capability has been established.
- How it is used
- Uses validation to establish safe preconditions before feature work begins.
- How deep it goes
- Defines evidence through records and loading steps, while leaving the validation implementation interchangeable.
- Examples
- Uses AddItemsRequest, ValidAddItemsRequest, Item, pricing data, inventory counts, and product details.
- What you can do after
- Build it from scratch by converting raw inputs into types that encode validated preconditions.
Read how Data-Oriented Programming in Java explains evidence →
Effective Data Analysis
Evidence is information that supports or challenges a hypothesis, theory, or conclusion without making it irrevocable.
- How it is used
- Supports hypothesis evaluation while keeping conclusions open to revision in experiments, quasi-experiments, and stakeholder decisions.
- How deep it goes
- Defines evidence against proof and discusses subgroup comparisons, interaction effects, and Type 1 error risk without detailing analysis procedures.
- Examples
- Uses subscription renewal, tutoring outcomes, website engagement, subgroup trends, and quasi-experimental group assignment as examples.
- What you can do after
- Evaluate/understand claims without treating supporting data as irrevocable proof.
Also covered in
- The Architecture of ReasoningIn early access (MEAP)
- LLM Evaluation and Alignment, The Foundational IdeasIn early access (MEAP)
- Fundamentals of CybersecurityIn early access (MEAP)
- Machines that ThinkIn early access (MEAP)
- AI Agents for Offensive SecurityIn early access (MEAP)
- AI Model EvaluationIn early access (MEAP)
- Grokking Statistics
- Data-Driven Cybersecurity
What to know first
- AI agentAn AI agent is a computational system that uses artificial intelligence to interpret information and select or perform actions toward goals while interacting with an environment.
- complianceCompliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
- authorizationAuthorization is the determination of which actions or resources an identity or other entity is permitted to access under defined permissions or policies.
- hypothesisA hypothesis is a proposed proposition, explanation, prediction, or model whose validity or plausibility can be assessed against evidence.
Related concepts
- dry runproduced by · A dry run is an execution mode that previews, validates, or reports an operation’s prospective behavior without carrying out the effects being previewed.
- Bayesian inferenceused by · Bayesian inference updates probability distributions over hypotheses or unknown quantities by combining prior information with observed evidence and a likelihood model.
- monitoringproduced by · Monitoring is the ongoing observation and measurement of a system or process to assess its behavior or condition and detect changes, failures, or other problems.
- experimentationproduced by · Experimentation is the planned investigation of a question or hypothesis by conducting trials or interventions and observing their outcomes.
- Bayes' theoremuses · Bayes' theorem relates conditional probabilities, expressing a posterior probability in terms of a prior probability, a likelihood, and the evidence.
- corepart of · A blog-post optimization group concerned with focus, logical organization, and adequate technical support.
Questions about evidence
What is evidence?
Evidence is information, observations, or material used to support, challenge, or assess a claim, conclusion, event, or outcome.
Which Manning books explain evidence?
Writing for Developers: Blogs that get read, Timeless Algorithms, The Foundational Ideas, Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform, Fabulous Adventures in Data Structures and Algorithms, Architecting Autonomous Agentic Systems, Designing AI Agents, Data-Oriented Programming in Java and Effective Data Analysis.
What should I know before learning evidence?
Manning books that teach evidence usually introduce AI agent, compliance, authorization and hypothesis first.
What is evidence part of?
Evidence is part of core. A blog-post optimization group concerned with focus, logical organization, and adequate technical support.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.







