DevOps Team Lead
A public engineering knowledge base.
I publish notes, guides, incident reviews, and practical approaches from my daily work.
Main topics:
Why a successful GitOps flow does not prove publication, and how checking the expected revision ties a release to the site response.
How LLMs accelerated 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.
How a public draft helps reconstruct a causal chain, expose hidden dependencies, and define the guarantees of an engineering solution.
How an article moves through two repositories, where CI ends, and which part of delivery belongs to Flux.
Why CI could not block Flux after a direct push and how a Merge Request with auto-merge moved validation before the watched branch.
How to turn ticket histories and chat discussions into documentation, checks, and automation that engineers can reuse.