Originally published on kuryzhev.cloud
A pager goes off at 3 a.m. with dozens of notifications for the same disk-pressure event on one node, spread across three teams who all have the node exporter alert wired to their phones. By the time someo...
Same-session tests are not evidence. If an agent writes a production hunk and the assertions in one pass, a green build often means the two files agreed on a private story, not that the public contract holds. Score the overlap first. Then rewrite the oracle in a session that never sees the patch.
This is not a flake policy and not a fixture lock. Those gates ask whether a test is stable...
A lot of “late payment” problems begin before the invoice exists.
The client is busy, your work is done, and the payment date is suddenly a negotiation. A few small decisions at the start of a project can make getting paid much more predictable:
Don’t leave “due soon” in a proposal. Use a clear due date or terms such as Ne...
Expo monorepo CI gets slow and flaky for the same reason: we treat all caches as one thing. Then builds run from the repo root, one app reuses another app’s Metro state, or native cache is blamed for a problem in dependency install. The result is a pipeline that looks fast until it starts failing in ways you cannot trust.
The fix is to give each layer a clear boundary. Run EAS commands ...
On 30 July 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) published an alert stating that it was observing a significant increase in cyber threat actors targeting programmable logic controllers (PLCs) in the Water and Wastewater Systems (WWS) Sector. The ale...
Hi everyone! We want to share our experience writing and reviewing a Kubernetes audit policy.
A Kubernetes audit policy is one of those things that gets written once during cluster setup and then lives "as is" for years, accumulating exceptions for new components and almost never being reviewed as a whole. At some point it's no longer a security policy — it's a layer of three-year-old c...