> technical_dictionary

Technical Dictionary

A reference for technical terminology used across TinyCTO.tv.

Incidentpedia/Technical Dictionary

Most Referenced Terms

organizational memoryThe accumulated knowledge of an organization, often residing in people, artifacts, or legacy code rather than official documentation.
50 refs
Developer ExperienceThe overall friction, efficiency, and satisfaction a developer encounters while working within an organization's engineering ecosystem.
40 refs
Platform EngineeringThe discipline of building internal developer platforms, toolchains, and golden paths to reduce operational friction for software teams.
30 refs
Accountability DilutionA phenomenon where the responsibility for a decision or failure becomes so dispersed among a group that no single person is held accountable.
20 refs

Explore by Domain

Software Engineering (29)DevOps (17)Product Management (14)System Architecture (13)

How this dictionary connects to Incidentpedia

Every term in this dictionary maps to its context across Incidentpedia, Episodes, and TinyCTO.tv. The relationships between terms define the conceptual architecture.

247 terms found

Abstraction Layer

A system design boundary that hides implementation details.

Acceptance Criteria

A set of conditions that a software feature must meet to be accepted by a user, customer, or other system.

Acceptance Testing

Formal testing conducted to determine whether or not a system satisfies its business and technical requirements before going to production.

accidental complexity

Unnecessary difficulty introduced by poor technical choices, convoluted architecture, or confusing tooling.

Accountability Dilution

A phenomenon where the responsibility for a decision or failure becomes so dispersed among a group that no single person is held accountable.

accountable spine

A single, unbroken line of accountability within a collaborative platform or architecture.

Adoption Friction

The resistance, difficulty, or cost associated with getting users or developers to use a new tool, platform, or feature.

agent instruction

The specific directives, constraints, and operational goals provided to an autonomous AI agent to dictate its behavior during task execution.

Agentic Runaway Loop Meltdown

An autonomous AI agent failure state where recursive tool-calling without bounded halting conditions exhausts API budgets, CPU quotas, and rate limits.

AI Hallucination

The phenomenon where an AI model confidently generates false, nonsensical, or completely fabricated information.

AI Platform Needs

The infrastructure, compute, and data requirements necessary to run AI models without bankruptcy or tears.

AI Strategy

A buzzword-heavy plan to integrate artificial intelligence into products, often prioritizing investor optics over actual technical utility.

alert design

The strategic configuration of notifications intended to warn operators about actionable system degradation.

Alert Fatigue

The psychological condition where engineers ignore critical system warnings because everything is always beeping.

API Contract

The formal agreement regarding how an API behaves, its expected inputs, and guaranteed outputs.

Application Programming Interface

A defined set of rules and protocols that allows different software systems to communicate with each other.

Architectural Decision Record

A lightweight document capturing a significant architectural decision, including its context, alternatives considered, and consequences.

architectural root cause

When the underlying design, rather than a broken component, is the actual reason for an incident.

architecture accountability

The operational and organizational responsibility for the consequences of architectural decisions.

Architecture Ceremony

Formal, often bureaucratic processes required to approve architectural decisions or deployments.

architecture communication

The process of effectively explaining system design constraints, trade-offs, and intentions to both technical and non-technical stakeholders.

Architecture Diagram

A visual representation of system architecture components, interactions, and responsibilities.

architecture drift

The gradual divergence between a system's documented, intended design and its actual implementation in production.

Architecture Review

A formal meeting where technical designs are evaluated, often mutating into a bureaucratic hurdle rather than a constructive exercise.

architecture storytelling

The practice of explaining complex system behaviors, constraints, and failures through human-centric narratives rather than rigid technical diagrams.

automation guardrail

Hardcoded constraints that prevent automated systems from executing destructive or costly actions.

Backpressure

A mechanism to signal downstream overload to upstream producers to slow down data ingestion and prevent system overload.

Blast Radius

The theoretical and actual maximum damage caused when a specific component fails or a bad deployment happens.

CAB Bureaucracy Deployment Freeze

An organizational gridlock where Change Advisory Boards mandate exhaustive manual approvals, paradoxically increasing incident risk by batching high-risk monolith releases.

cache

A fast, temporary storage layer that serves data quickly, often trading perfect accuracy for speed.

Cache Invalidation

The process of removing or updating cached data so that stale or incorrect information is no longer served.

Capability Boundary

The logical edge of a system or team's responsibilities, defining what it can and cannot do.

capacity planning

The process of predicting future system load and provisioning the necessary computing resources to handle it.

Cascading Retry Storm

A self-inflicted failure cascade where aggressive client and inter-service retries without jitter collapse upstream databases and downstream recovery pipelines.

cloud cost growth

The unchecked scaling of cloud infrastructure expenses over time.

Cloud Cost Ownership

Clear responsibility for the expenses incurred by cloud infrastructure usage.

Cloud Egress Shockwave

An exponential cloud billing crisis caused by unmetered cross-AZ or cross-region data transfer during distributed failovers or data pipelines.

Cloud Region

A geographical area where cloud provider data centers are located.

Code Review

The collaborative process where peers examine source code changes to catch bugs and ensure maintainability before merging.

complexity management

The continuous effort to keep a system understandable, testable, and maintainable as it grows.

Concurrency Limit

A hard boundary on how many tasks can be processed simultaneously to prevent resource exhaustion.

Content Delivery Network Caching

Caching static or delivery content closer to the user to reduce load on the origin server.

Continuous Integration Server

A server that automatically builds, tests, and validates code when changes are pushed to a version control repository.

Cost Center

A department or function within an organization that does not directly add to profit but still costs money to operate.

Cost Control

Mechanisms put in place to monitor and limit expenditures on AI APIs or cloud usage.

Cost Incident

An unexpected spike in infrastructure or API costs, treated as an operational failure.

Critical Path

The sequence of dependent tasks that determines the minimum time required to complete a project.

Cross-Functional Alignment

The state where different departments (engineering, product, sales, marketing) share the same goals and understanding of a project.

Cross-Functional Program

A large-scale initiative that requires coordinated effort across multiple independent teams and departments.

dashboard

A visual interface that aggregates and displays key telemetry data to provide a real-time overview of system health.

Data Boundary

Strict rules and technical guardrails defining what data an AI system or service can access and process.

data governance

The overarching framework of policies, roles, and technical controls ensuring data availability, integrity, and security.

data lineage

The visual and technical map tracing the complete lifecycle of data from its source to its final consumption.

database constraint

Strict, database-level rules that reject any data mutation violating the defined integrity of the schema.

Database Index

A data structure that improves the speed of data retrieval operations on a database table.

Database Statistics

Data about table sizes, row distributions, and index compositions used by the query optimizer to plan execution paths.

Decision Accountability

The requirement for an individual or group to take responsibility for the outcome of a technical or business choice.

Decision Authority

The official power granted to an individual or role to make final technical, product, or architectural choices.

Decision Ownership

The internalized commitment to championing a decision, executing it, and resolving any issues that arise from it.

decision record

A formal document that captures an architectural or technical decision, along with its context and consequences.

decision rights

The explicit authority granted to an individual or team to make choices about architecture, roadmap, or resolution.

decision traceability

The ability to track why a risk was accepted, who made the call, and under what context.

delivery pressure

The organizational urgency to ship features, often leading to ignored warnings and accumulated technical debt.

Delivery Reality

The actual state and speed of a team's ability to ship software, often contrasting with the theoretical or cultural narrative.

Demo Reliability

The deceptive appearance of system stability achieved only when following a highly specific, rehearsed set of steps.

dependency management

The systemic process of tracking, updating, and securing external libraries and packages used by an application.

Dependency Map

A visual representation of how different systems, teams, or components rely on each other.

Deployment

The operational process of moving packaged software code to a target environment so it can be executed.

Deployment Path

The specific route, stages, and approvals software must travel through to move from development to a live production environment.

Deployment Pipeline

An automated sequence of scripts and tools that compiles, tests, and deploys software to various environments.

deployment safety

The degree to which a deployment process prevents production outages.

design trade-off

A deliberate compromise made in system design, where an advantage in one area causes a disadvantage in another.

Developer Experience

The overall friction, efficiency, and satisfaction a developer encounters while working within an organization's engineering ecosystem.

Diagram Theater

The practice of creating highly complex, aesthetically pleasing architectural diagrams that bear no resemblance to the actual, chaotic state of production.

Diff

A visual representation of the line-by-line changes made between two versions of a file or codebase.

Discovery

The initial phase of product development focused on understanding the user's problem before deciding on a technical solution.

Distributed Denial of Service (DDoS)

A malicious or accidental flood of traffic designed to overwhelm a system and make it unavailable to legitimate users.

Distributed System

A system whose components are located on different networked computers, often applied metaphorically to human coordination.

Edge Case

A rare problem or situation that occurs only at extreme operating parameters or unusual combinations of events.

Edge Computing

Running code or storing data at the edge of the network, close to the user.

Enterprise-Ready

A marketing claim suggesting software can handle the security, compliance, and scale demands of large corporations, often requiring massive operational overhead.

essential complexity

The unavoidable difficulty inherent in solving a specific business or technical problem.

Estimation

A developer's highly optimistic guess at how long a task will take, usually weaponized by management as a hard deadline.

Evaluation Loop

A continuous, automated process for assessing the performance, safety, and accuracy of AI models against a set of benchmarks.

Eventual Consistency

A consistency model guaranteeing that, in the absence of new updates, all nodes will eventually return the last updated value.

Evidence Gap

The missing traceability between an AI model's output and the authoritative source data that proves its validity.

executive metric

A high-level number tracked by leadership that often fails to capture the messy reality of engineering.

Executive Visibility

The degree to which upper management is aware of a project, usually leading to superficial optimizations designed to impress them.

Exponential Backoff

A strategy of waiting longer between repeated attempts to connect to a failing service.

Failure Path

The sequence of code execution and events that occur when something goes wrong.

feature flag

A configuration toggle that allows teams to enable, disable, or test specific code paths in production without deploying new code.

feedback loop

The cycle in which a system's output becomes input for future operations, shaping its stability over time.

Financial Exposure

The potential monetary loss a company faces due to an engineering risk, outage, or poorly optimized architecture.

Freshness Contract

An agreed-upon timeframe indicating how long cached data can be served before it is considered unacceptably stale.

Golden Path

The recommended, supported, and most friction-free way to build, deploy, and maintain software within an organization.

Governance Board

A group of stakeholders responsible for overseeing and approving decisions, often disconnected from the actual engineering work.

Governance Bypass

The act of intentionally circumventing established security, architectural, or release processes to deliver work faster.

governance overhead

The bureaucratic cost of compliance, approvals, and review processes that slow down development.

governance theater

Processes or documentation that give the illusion of control without actual operational accountability.

health check

An automated diagnostic endpoint or process used to verify if a service is healthy and capable of handling requests.

hidden dependency

An undocumented or unmanaged reliance between system components that only reveals itself when it fails.

High Availability

A characteristic of a system that aims to ensure an agreed level of operational performance.

hotfix process

A rapid, out-of-band deployment procedure designed for resolving critical issues in production.

hypercare

A period of elevated monitoring and rapid response immediately following a major release or migration.

Idempotency

The property of certain operations where they can be applied multiple times without changing the result beyond the initial application.

Ignored Assumption

A fundamental business or technical reality that is politely disregarded during planning, only to catastrophically fail in production.

ignored risk signal

A clear warning of impending system failure that is systematically dismissed by teams or leadership.

Implementation Ambiguity

A lack of clear technical direction or precise requirements, leading to unpredictable execution and systemic misalignment.

incentive

The organizational pressures and rewards that shape how architecture is actually built, often overriding stated engineering values.

Incident Commander

The person officially in charge of coordinating the response during a major outage.

incident follow-through

The disciplined execution of action items identified during a postmortem to prevent the recurrence of an incident.

incident rehearsal

A simulated exercise where engineering teams practice their response to a hypothetical production failure.

Incident Reproducibility

The ability to reliably recreate a bug or outage in a controlled environment.

Incident Response

The structured process of recognizing, mitigating, and resolving a system outage.

Incident Trigger

The specific event or condition that initiates a production failure.

institutional memory

The collective knowledge of an organization, often lost when people leave but retained cryptically by the code.

Latency

The delay before a transfer of data begins following an instruction for its transfer, or the time it takes for a data packet to travel from a source to a destination.

Latency Geography

The impact of physical distance on network communication delays and system performance.

launch readiness

The state of a system and team being fully prepared for production deployment.

leader election

A consensus algorithm process where a cluster of nodes coordinates to designate a single node as the primary coordinator.

legacy system

Old or outdated software that remains in production because it supports critical business functions.

Lighthouse Diagram

A high-level, idealized architectural diagram often used in presentations that lacks technical detail or implementation.

load testing

Simulating expected production traffic on a system to measure its capacity, performance bottlenecks, and failure points.

Merge

The action of officially incorporating a branch of code changes into the main codebase.

metric quality

The degree of accuracy, consistency, and reliability of a business or technical metric used for reporting.

Microservices

A loosely coupled architectural style where services are fine-grained and deployed independently.

Migration

The risky and often prolonged process of moving data, users, or systems from an old environment to a new one.

Migration Plan

A step-by-step technical strategy to safely apply schema or state changes without causing downtime or data loss.

migration planning

The meticulous preparation process required to execute data movements, schema updates, or infrastructure transitions safely.

migration risk

The calculated probability and impact of data loss, corruption, or prolonged downtime during a system transition.

Model Confidence

A numeric score assigned by a machine learning model indicating how certain it is that a specific prediction or generated output is correct.

Monolithic Architecture

A software architecture where components are tightly coupled and deployed as a single unit.

Morale Symbol

Superficial items, such as mascots or stickers, deployed by management to boost team spirit without addressing underlying systemic dysfunctions.

Observability

The ability to understand internal system states by examining external outputs like logs, metrics, and traces.

observability blind spot

A component, interaction, or edge case in a system that lacks adequate metrics, logging, or tracing.

operational behavior

How a system actually functions in production under real loads, regardless of its theoretical design.

operational confidence

Trust in the system's and team's ability to operate effectively.

operational contract

A strict agreement defining who responds to and fixes issues in a service.

Operational Latency

The delay introduced into a process or system by human approvals, organizational red tape, or inefficient handoffs.

operational support

The active effort required to keep a service running, including on-call response.

Operational Truth

The actual, measurable state and behavior of a system in production, regardless of how it was designed or documented.

Operationalization

The process of taking a functional piece of software and making it robust enough to run reliably in a production environment.

optional dependency

A system component designed to be non-critical, but which inadvertently causes hard failures when it goes down.

organizational forgetting

The tendency of leadership or teams to forget the constraints, failures, and shortcuts embedded in the system over time.

Organizational Interface

The formal and informal boundaries, APIs, and communication structures between different teams.

organizational learning

The rare process by which a team successfully integrates lessons from past incidents into future behavior and architecture.

organizational memory

The accumulated knowledge of an organization, often residing in people, artifacts, or legacy code rather than official documentation.

Page

An automated alert sent to an on-call engineer requiring immediate attention.

Payload

The actual, meaningful data transmitted within an API request, response, or event message, excluding metadata and headers.

Platform Engineering

The discipline of building internal developer platforms, toolchains, and golden paths to reduce operational friction for software teams.

platform governance

The mechanisms and rules by which a shared platform is managed, owned, and evolved.

Platform Ownership

Clear responsibility, roadmap control, and decision-making authority over a shared technical platform.

postmortem

An analysis conducted after an incident to understand causes and prevent recurrence.

Postmortem Evidence

The logs, metrics, and timelines collected after an incident to understand what happened.

predictable chaos

Incidents that appear random but were entirely foreseeable if earlier signals had not been ignored.

Premature Optimization

The anti-pattern of complicating code to improve performance before knowing if that specific code is actually a bottleneck.

premortem

A meeting or document predicting how a project might fail before it is launched.

Problem Statement

A clear, concise description of the specific issue or pain point that needs to be solved, stripped of proposed solutions.

Production

The live environment where real users interact with the system.

Production Fix

A code or infrastructure change deployed directly to resolve a live issue.

Production Incident

An unplanned event that disrupts or reduces the quality of the live service.

Program Inflation

The unnecessary expansion of a simple task, feature, or bug fix into a massive, multi-quarter organizational program.

Prompt Governance

The framework, policies, and technical controls used to manage, version, and approve the prompts sent to large language models in a production environment.

prophetic decoration

Warnings, logs, or dashboards that correctly predict failure but are ignored because they lack owners or actionable triggers.

Pull Request

A formal request to merge proposed code changes into a main branch, subject to team review.

Query Plan

The step-by-step execution strategy chosen by the database engine to retrieve data for a specific SQL query.

Queueing Systems

Architectural mechanisms to buffer workloads waiting for processing.

Quick Win

A fast, seemingly low-effort implementation meant to deliver immediate business value, which usually creates long-term technical debt.

RACI Matrix

A formal matrix used to clarify roles and responsibilities (Responsible, Accountable, Consulted, Informed) for tasks or decisions.

Refactor

Restructuring existing code without changing its external behavior.

refactoring risk

The danger of breaking hidden behaviors or edge cases when modifying code structure.

Release Friction

Any technical or administrative barrier that slows down, complicates, or discourages the process of shipping software.

release gate

Strict checks that can actually block a release if requirements aren't met.

release risk

The likelihood of a failure during software deployment.

Release Train

A scheduling strategy where software releases occur on a strict, regular cadence, regardless of which features are ready.

Release Train

A structured release management process where multiple software components are bundled and deployed on a fixed schedule.

Repeatability

The ability to consistently recreate an experiment, process, or deployment with the exact same results.

repeated failure mode

Incidents that occur multiple times because the underlying system incentives, architecture, or organizational habits remain unchanged.

Requirement Drift

The slow, silent expansion or modification of project requirements after the initial scope has been agreed upon.

requirements discovery

The painful process of understanding what users actually need, usually discovering it only after shipping what they requested.

resilience gap

The hidden vulnerability between how a system is supposed to handle failure and how it actually behaves during an incident.

Response Authority

The organizational power and capability explicitly granted to an engineer or team to act when a risk materializes into an incident.

Response Capacity

The cognitive and technical bandwidth a team has available to handle system failures.

response duties

The explicitly assigned responsibility to acknowledge, investigate, and resolve incidents and outages for a specific service.

Retry Policy

Rules determining how and when failed operations should be attempted again.

Retry Storm

A cascading failure caused when clients aggressively retry failed requests, overwhelming a recovering service.

risk acceptance

The explicit agreement to take on known technical risks rather than mitigating them.

risk acceptance

The formal or informal decision to acknowledge and proceed despite known risks, ideally with an accountable owner.

Risk Register

A formal document or system used to track potential technical or business risks.

Roadmap

A strategic visual document defining a high-level goal and the major deliverables expected over a timeline.

roadmap memory

The false organizational assumption that deleting a technical debt item from a roadmap deletes its consequences from the production system.

roadmap planning

The strategic scheduling of features and releases, often degenerating into a fantasy document divorced from engineering reality.

Roadmap Risk

The probability that planned features and strategic initiatives on the roadmap will be delayed, descoped, or completely derailed.

Rollback

The process of reverting a system to its previous functional state after a flawed deployment.

rollback plan

A pre-defined procedure to revert a system to a previous state.

Rollback Plan

A documented and tested procedure for reverting a specific release gracefully.

Root Cause

The fundamental underlying flaw that allowed an incident to occur.

Root Ownership Problem

The underlying lack of clear responsibility that causes an issue to bounce between teams, escalate unnecessarily, or be entirely ignored.

Rumor-Driven Development

Developing features, integrations, or architectures based on unverified conversations and assumptions rather than formal contracts or documentation.

Runbook

A written compilation of step-by-step procedures for handling specific system operations and incidents.

Runtime Pager

The responsibility of being on-call to fix a system when it breaks in production.

Schema Change

A structural modification to a database, such as adding tables, altering columns, or creating indexes.

Schema Drift

The silent divergence between the expected structure of data and its actual schema in production databases.

Scope Creep

The continuous, uncontrollable expansion of project boundaries and requirements leading to delays and architectural instability.

screenshot-driven development

Building software based solely on static images without behavioral specifications.

Semantic Drift

The process by which teams use the exact same terminology but gradually adopt fundamentally different meanings.

Service Level Agreement (SLA)

A formal, contractual commitment regarding the reliability, availability, and performance of a service.

Service Mesh

An infrastructure layer that handles communication between microservices.

service ownership

The explicit accountability for the operation, maintenance, and incident response of a specific software service.

Shadow Delivery Path

Unofficial, covert workflows developers use to bypass strict, slow official deployment processes.

shared ownership

A highly dangerous organizational anti-pattern where multiple teams own a service, meaning no one actually owns it.

Shared Ownership

A scenario where multiple individuals or teams are nominally responsible for a system, which predictably results in no one actually taking responsibility.

Shared Services

Centralized technical capabilities or infrastructure teams utilized by multiple different product groups within an organization.

Shared State

A unified, real-time understanding of system conditions across all responders during an incident.

Shortcut

An expedited implementation path taken to meet a deadline, bypassing standard quality controls.

Source of Truth

The definitive, trusted system or location for specific data or knowledge.

source of truth drift

The divergence between documentation, system diagrams, and the actual live codebase over time.

Source Path

The definitive location, endpoint, or system of origin from which a specific data asset is extracted.

specification governance

The bureaucratic process of managing, versioning, and arguing about official system requirements.

Sprint

A time-boxed iteration in Agile frameworks, typically lasting one to four weeks, designed to deliver a specific increment of value.

Sprint Goal

A concise statement defining the primary objective and business value a team aims to achieve during a sprint.

Stale Data

Information retrieved from a cache or replica that no longer matches the primary source of truth.

stale read

An operation that returns outdated data because the read replica or cache has not yet synchronized with the primary data store.

Stop Condition

A defined logical state or rule that prevents an automated loop, workflow, or retry mechanism from running infinitely.

Strong Consistency

A consistency model guaranteeing that any read operation will immediately return the most recent write.

Success Metric

A quantifiable measure used to objectively evaluate whether a product, feature, or architecture change actually achieved its intended goal.

System Constraint

The physical or logical limits within which a system operates.

system design consequences

The long-term operational and organizational impacts resulting from an architectural decision.

system feedback

The observable signals—like latency, errors, or resource exhaustion—that a system emits under stress.

system pattern recognition

The ability to look at multiple discrete software failures and identify the shared architectural flaw causing them.

systemic incident

Incidents that arise from the complex interaction of components and historical design choices rather than isolated component failures.

technical debt

The accumulated cost of shortcuts, deferred decisions, and rapid solutions that require future rework.

Temporary Workaround

A suboptimal fix applied quickly with the intention of replacing it later, which almost never happens.

Throughput

The rate of production or the rate at which a system can process a volume of data or requests over a specific period.

Ticket

A formal, tracked item of work, bug, or request representing a single unit of execution within a project management system.

Time to Live

A mechanism that determines how long a cached item remains valid.

Token Loop

A cycle where an AI agent continuously generates tokens without reaching a stop condition, driving up costs.

Trade-off

A conscious architectural or organizational decision that accepts a specific negative consequence in exchange for a desired positive outcome.

Transformation Theater

Superficial organizational activities designed to create the appearance of modern engineering culture without actually changing how work gets done.

Tribal Knowledge

Information that is known by a group but not formally documented.

unclear accountability

An organizational anti-pattern where it is not explicitly defined who holds decision-making authority or incident ownership for a specific system, component, or process.

Undocumented Decision

A critical architectural or business choice made informally and never recorded.

Uptime

The percentage of time a system is available and successfully serving its intended function.

Urgency Inflation

The organizational habit of artificially escalating the priority of every feature request.

Validation

The process of verifying that data meets expected constraints before allowing it to proceed.

Worker Pool

A finite set of active threads or background processes managed together to execute concurrent tasks.

Workstream

A series of related activities within a larger project, often used to create the illusion of progress.

Loading terms...

Frequently Asked Questions

What is the Technical Dictionary?

A reference index of all technical terminology used across TinyCTO.tv, explained in a dry, satirical tone.

How are terms selected?

Terms are added as they appear in new episodes or articles.

AI Summary

The Technical Dictionary serves as the central knowledge graph for TinyCTO.tv. It provides standardized, satirical definitions for industry jargon, mapping canonical concepts to their localized equivalents and establishing the semantic foundation for the entire universe.

Explore the system

Engineering Field Manual→Read the incident index→Browse the stacks→Explore the topics→Explore the systems→Watch the episodes→Agents→