Long-form writing on DevOps and security engineering — incidents, post-mortems, and the parts of infrastructure work that only show up under pressure. For project write-ups with measured outcomes, see the case studies.
RDS and EKS extended support, public IPv4 charges, NAT Gateways, orphaned EBS volumes and logs that never expire — the quiet causes of AWS cost growth, priced from official AWS pages, with read-only commands to find each one and how to fix it for good.
Two critical unauthenticated RCE flaws in the PHP runtime, fixed in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Affected setups, how to inventory every PHP you run, patching and worker restarts, the partial mitigations if you can't patch today, and verification — from the official PHP advisories only.
PHP, Go, Node.js, Next.js, React or Python — when a critical vulnerability lands, how many hours until every production instance is patched, and how would you prove it? A ten-point readiness scorecard, a copyable runbook, and how to upgrade fast without breaking what matters.
One trojaned public repository compromised a developer laptop. Sixty-four days later, the stolen GitHub token was used to inject malware into 35 repositories in 54 minutes. Full timeline, both injection vectors, the commit-forgery tells, blockchain-resolved C2, verbatim IOCs — and the four conclusions the investigation got wrong before it got it right.