Close a release with smoke and rollback evidence
2 min
Building an image does not prove that users can use a healthy path. Bind the tested commit to the running image and run a real DB-reading smoke after readiness.
#readiness
Posts tagged readiness
Categories
AI & LLM
9AI/LLM topics — agents, prompts
Web Fundamentals
7HTML, CSS, JS, HTTP, URL basics
Languages
4TypeScript, Java, Python, Rust
Programming
4Data structures, Big-O, patterns
Frontend
18React, Next.js, Tauri, Tailwind
Backend
19Spring, FastAPI, SQL
Agent tooling
15Claude Code · MCP · Context7 · Figma — overview of AI coding tools
Cloud
22Deployment options and decision criteria
Data
20PostgreSQL · Kafka · data strategy notes
Infra
10Docker, Compose, Caddy, SSH
Environment
11Windows vs Mac and other dev-environment notes
Mobile
4Cross-platform options compared (Tauri · Flutter · RN)
Dev tools
12pnpm, uv, Gradle, Git, regex
Philosophy
10KISS · DRY · YAGNI · naming — development philosophy
Security concepts
9OAuth · JWT · security fundamentals
Quality / Tests
11Testcontainers, Vitest, pytest
Learning
6Searching, reading docs, debugging
Posts tagged readiness
Separate required readiness from optional capabilities
2 minA live process, a service ready for its critical path, and a service with every optional feature working are different facts. Putting them into one ready value can turn an optional model outage into a full restart, whil…
Compose readiness and partial rollback boundaries
2 minA running container may still lack a database connection, required tables, or an internal dependency. Liveness says the process is alive; readiness says it can receive user traffic.