DevOps Team Lead
A public engineering knowledge base.
I publish notes, guides, incident reviews, and practical approaches from my daily work.
Main topics:
How persisting intent before POST blocks another publication when the outcome is unknown, and why a success log alone cannot guarantee duplicate-free delivery.
How a trusted proxy allowlist protects an IP rate limiter, why forwarded headers need validation, and what application tests cannot prove.
How a maintenance request generator separates model-written text, user requests, and rules the application enforces with ordinary code.
Why a successful GitOps flow does not prove publication, and how checking the expected revision ties a release to the site response.
How bugs in commitlint and a shell check produced false success, and which regression tests now protect the checks themselves.
How LLMs can accelerate contract-test overengineering and why observable behavior matters more than implementation details.
How to turn critical claims about CI into contract tests that make documentation drift visible when the pipeline changes.
Why the definition of done should move from prompts into a verifiable contract, with an independent review of the agent’s result.
Why independent review works better when the second agent sees the task and result but does not inherit the implementer’s explanation.
Why acceptance criteria and verification methods should be defined before implementation, so that the meaning of done is not adjusted to fit the resulting solution.