Risk
Risk is the possibility of an adverse outcome arising from uncertainty, together with its potential consequences.
Investing for Programmers
Investment risk is the possibility that an investment will produce an unfavorable outcome, including loss or lower-than-expected returns.
- How it is used
- Frames risk as the basis for investment decisions, portfolio construction, and disciplined challenge of optimistic claims.
- How deep it goes
- Explains classification, systemic threats, risk matrices, hedging, and portfolio pairing through practical scenarios rather than dense quantitative modeling.
- Examples
- Uses LiDAR stocks, AI companies, Coca-Cola, Apple, Pfizer, speculative technologies, risk matrices, and stable-versus-speculative allocations.
- What you can do after
- Evaluate/understand investment risk by identifying threats, ranking severity and likelihood, challenging assumptions, and selecting mitigation approaches.
Software Testing with Generative AI
The possibility that an action, system, or technology will cause harm, loss, failure, or another undesirable outcome.
- How it is used
- Guides testing toward specific quality concerns before selecting techniques, prompts, test cases, or exploratory sessions.
- How deep it goes
- Develops identification, prioritization, mitigation, and LLM augmentation, while stopping short of a fixed procedure for discovering risks.
- Examples
- Uses fast-food ordering, file upload, booking reports, generated test cases, and exploratory charters to make risk-focused testing concrete.
- What you can do after
- Apply it to identify concerns, challenge LLM suggestions, select proportionate testing activities, and prioritize exploratory work.
Read how Software Testing with Generative AI explains risk →
AI Governance
Risk is the possibility of an adverse outcome arising from uncertainty about an activity, system, or decision.
- How it is used
- Uses risk to decide where AI systems can operate and under what conditions.
- How deep it goes
- Provides review questions and operating conditions, while emphasizing that the goal is informed use rather than risk elimination.
- Examples
- Illustrates risk with a claims assistant’s expanding capabilities and the EchoLeak attack against Microsoft 365 Copilot.
- What you can do after
- Evaluate AI deployments by their access, actions, potential damage, and ability to support an incident response.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
Risk is the possibility that uncertainty will adversely affect an objective, investment, or change initiative.
- How it is used
- Prioritizes modernization opportunities by exposing threats to timely delivery and their consequences.
- How deep it goes
- Frames risk through causes and consequences in a context-specific scorecard rather than prescribing a universal scoring model.
- Examples
- Uses a workflow automation subdomain, promised customer features, a modernization initiative, and a legacy monolith.
- What you can do after
- Evaluate modernization candidates by comparing delivery threats with business value and learning value.
Delivering Machine Learning Projects: From design to deployment
Project risk is the possibility that uncertainty in a project will cause adverse effects such as cost escalation, unmet targets, or failure to deliver.
- How it is used
- Uses pre-project investigation and governance to reduce uncertainty before committing resources and accepting delivery obligations.
- How deep it goes
- Descends from risk sources to registers, mitigation confidence, premiums, documentation, review meetings, and accountable sign-off.
- Examples
- Uses risk registers, mitigation estimates, $500-to-$1,000 premium examples, weekly stakeholder reviews, and fixed-price delivery scenarios.
- What you can do after
- Apply it via a risk register, mitigation estimates, risk premiums, budget review, documentation, and accountable sign-off.
Read how Delivering Machine Learning Projects: From design to deployment explains risk →
Fundamentals of Cybersecurity
Risk is the potential for adverse impact arising from threats exploiting vulnerabilities in assets or environments.
- How it is used
- Guides cybersecurity decisions by comparing potential harm and directing attention toward the most significant risks.
- How deep it goes
- Explains likelihood, impact, assessment, treatment, residual risk, and monitoring, while stopping short of detailed quantitative methods.
- Examples
- Uses malware, authentication bypass, outdated firmware, interface misconfiguration, and an obstacle-crossing analogy to compare risk levels.
- What you can do after
- Evaluate risk, prioritize treatment, select mitigation measures, and monitor residual exposure.
Decision Engineering
A risk is a potential adverse event or consequence that may affect a decision or its results.
- How it is used
- Frames compliance-control choices and external-product evaluation around potential security, legal, operational, and continuity consequences.
- How deep it goes
- Develops qualitative comparisons of safeguards and vendor incentives, without specifying a numerical risk model.
- Examples
- Uses cloud storage encryption and access reviews alongside Layer’s shutdown and Talend Open Studio’s retirement.
- What you can do after
- Evaluate/understand whether safeguards are proportionate and whether an external product’s business circumstances threaten continuity.
Functional Design and Architecture: Examples in Haskell
A risk is a potential problem whose occurrence can increase the cost, delay, or failure likelihood of a software project.
- How it is used
- Guides architecture, simplicity, planning, and testing decisions intended to keep delivery and maintenance problems manageable.
- How deep it goes
- Illustrates architectural and complexity risks through scenarios, then identifies testing approaches without providing a complete risk-management procedure.
- Examples
- Uses incompatible independently built components, overcomplicated code, and black-box, white-box, functional, and integration testing.
- What you can do after
- Diagnose threats arising from architectural mismatch and overcomplication, then recognize testing as a way to reduce specific project risks.
Read how Functional Design and Architecture: Examples in Haskell explains risk →
Build High Value Software Systems
The possibility of harm or loss, assessed here through the probability and impact of a failure and the time it remains undetected.
- How it is used
- Uses risk to size delivery safeguards and place tests where they can catch costly defects early.
- How deep it goes
- Maps defect containment across unit, integration, end-to-end, and production detection using impact and time undetected.
- Examples
- Contrasts logging, authentication, and payment failures, and maps login, retrieval, calculations, and user journeys to test layers.
- What you can do after
- Evaluate safeguards and test placement by weighing failure likelihood, impact, and how long defects may go undetected.
Data-Driven Cybersecurity
The potential for loss, harm, or adverse impact arising from a threat exploiting a vulnerability or hazardous condition.
- How it is used
- Frames risk assessment as a bounded method for analyzing assets, threats, vulnerabilities, likelihood, and impact.
- How deep it goes
- Explains scope, assets, threats, and vulnerabilities procedurally, but stops short of teaching complete threat assessment.
- Examples
- Uses products, changes, implementations, critical assets, locations, data centers, and custom software without CVE entries as examples.
- What you can do after
- Evaluate risk by defining scope, identifying relevant threats and vulnerabilities, and relating likelihood and impact to reporting.
Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and Terraform
Deployment risk is the possibility that releasing a software change will cause failures or disruption in an application.
- How it is used
- Uses deployment risk to justify service boundaries and independent updates in microservices.
- How deep it goes
- Explains localized failures and rollback consequences but stops short of prescribing deployment procedures.
- Examples
- Uses service updates, partial application failures, and rolling back a small system part as concrete examples.
- What you can do after
- Evaluate how service boundaries can localize failures and make rollbacks smaller.
Authorization in Action
Risk is the possibility of an unfavorable outcome or failure arising from dependence on uncertain actions or conditions.
- How it is used
- Uses risk to select authorization signals, assurance, freshness, and delegation controls for different operational decisions.
- How deep it goes
- Connects risk to signal freshness, data quality, latency, and authority boundaries, stopping short of formal risk calculation.
- Examples
- Uses document viewing, production deployment, customer platforms, employee access, and engineering tools to contrast risk-sensitive decisions.
- What you can do after
- Evaluate authorization designs by matching signal assurance and freshness to the consequences of stale or insufficient context.
Timeless Algorithms, The Foundational Ideas
Risk is the possibility of an undesirable outcome together with uncertainty about its occurrence or impact.
- How it is used
- Frames risk as a decision constraint in hypothesis testing, with acceptable error risks specified before data analysis.
- How deep it goes
- Explains control of Type I and Type II errors within a sequential testing framework, without supplying error-rate formulas.
- Examples
- Uses the Neyman–Pearson framework to illustrate balancing error risks when evaluating competing claims.
- What you can do after
- Evaluate statistical conclusions by considering how decision rules balance specified error risks under uncertainty.
Read how Timeless Algorithms, The Foundational Ideas explains risk →
Also covered in
- Statistics Every Programmer Needs
- The Art of Code
- Lead Developer Career Guide
- Experimentation for Engineers
- Grokking Software ArchitectureIn early access (MEAP)
- How Large Language Models Work
- Architecting for AutonomyIn early access (MEAP)
- Machine Learning Algorithms in Depth
- Automating API Delivery
- Designing AI AgentsIn early access (MEAP)
- Evaluating AI SystemsIn early access (MEAP)
- Tech Startup Toolkit
What to know first
- language modelA language model is a computational model that represents patterns in linguistic sequences to assign probabilities, predict, generate, or evaluate language.
- artificial intelligenceArtificial intelligence is the field of computing concerned with creating systems that perform tasks associated with intelligence, such as learning, reasoning, perception, and decision-making.
- assetAn asset is a resource, item, right, or capability that has value to an individual or organization.
- complianceCompliance is conformity with applicable legal, regulatory, contractual, policy, or other governing requirements.
Related concepts
- credit riskincludes · Credit risk is the possibility that a borrower, issuer, or counterparty will fail to meet financial obligations, causing financial loss.
- existential riskincludes · Existential risk is the possibility of human extinction or a permanent, drastic, and globally catastrophic reduction in humanity’s future potential.
Questions about risk
What is risk?
Risk is the possibility of an adverse outcome arising from uncertainty, together with its potential consequences.
Which Manning books explain risk?
Investing for Programmers, Software Testing with Generative AI, AI Governance, Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Delivering Machine Learning Projects: From design to deployment, Fundamentals of Cybersecurity, Decision Engineering, Functional Design and Architecture: Examples in Haskell and 5 more.
What should I know before learning risk?
Manning books that teach risk usually introduce language model, artificial intelligence, asset and compliance first.
What kinds of risk are there?
Kinds of risk include bankruptcy risk, concentration risk, credit risk, disclosure risk, ESG risk and existential risk.
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.












