Glossary
Plain-English definitions for the DevOps, AI engineering, and MLOps terms TechyCamp teaches — each linked to a full guide.
- Agentic AI
Software that can reason about a goal, decide what steps to take, use tools to act in the real world, and adjust based on the results — with minimal human hand-holding.
Read the full guide →- AIOps
The use of AI — especially machine learning and AI agents — to detect, diagnose, and resolve operational problems with far less human intervention.
Read the full guide →- CI/CD
A pipeline that automatically tests, builds, and deploys code on every push, removing the manual steps between a Git push and a live release.
Read the full guide →- DevOps
The practice of shipping software reliably and quickly by automating everything between "code is written" and "code is running in production."
Read the full guide →- DevSecOps
Building security into every stage of a CI/CD pipeline — dependency scanning, secrets management, and automated checks — instead of bolting it on at the end.
Read the full guide →- Docker
A tool for packaging an application and its dependencies into a container, so it runs the same way in every environment.
Read the full guide →- Infrastructure as Code (IaC)
Describing cloud infrastructure in code (typically with Terraform) instead of clicking through a console, so environments are repeatable, reviewable, and recoverable.
Read the full guide →- Kubernetes
The standard system for orchestrating containers at scale — handling deployment, scaling, and recovery of pods and services.
Read the full guide →- MCP (Model Context Protocol)
An open standard that lets AI agents connect to external tools and data sources through one consistent interface, instead of a custom integration per tool per agent.
Read the full guide →- MLOps
The practices for deploying, monitoring, and maintaining machine learning models in production — logging what a model does and handling its failures gracefully.
Read the full guide →- Observability
The combination of logging, metrics, and monitoring that lets an engineer know when something breaks — ideally before users do.
Read the full guide →- Platform Engineering
Building internal developer platforms that give every engineer in an org a self-service "paved road," rather than each team automating its own deployments separately.
Read the full guide →- RAG (Retrieval-Augmented Generation)
A pattern where an AI system retrieves relevant documents and hands them to a model as context, instead of relying on what the model already "knows."
Read the full guide →- Spec-Driven Development
An engineering workflow where you write a clear, reviewable specification of what to build and why before any code is generated, then build against that spec as the single source of truth.
Read the full guide →- Vibe Coding
Prompting an AI in loose natural language, accepting whatever it generates, and re-prompting until it seems to work — with no written specification guiding the process.
Read the full guide →