Closing Your Source Code Doesn't Close Your Vulnerabilities
Links from the Episode
- DOP 366: How to Prevent npm Supply Chain Attacks
- DOP 367: Zero-Human Companies Still Need Humans
- DOP 368: The AI Productivity Paradox
- DOP 369: Vibe Coding Without the Slop
- AI Is Exposing The Open Source Ecosystem’s Remediation Gap
- Getting started with the Mantis harness to find and fix bugs
- How Cloudflare enforces engineering standards using AI
- Specification - Model Context Protocol
- Docker Brings Sandbox Kit Spec to the CNCF
- Native support for Prometheus metrics in GKE
- GKE adds native scale-to-zero capabilities
- AWS Elastic Beanstalk introduces Cluster Mode
- Saving another 100TB of RAM with math (and Rust)
- Two Upgrades to My AI Stack: Vigil and Idea-to-Video
- How to Think About the Difference Between Choice and Score in Jev
- ax
- git-pkgs
- LLM Inference Explained: 12 Concepts You Actually Need to Know
- Is Jenkins Dead? No, And That's Much Worse
- LLM Inference Is a Memory Problem, Not a Compute One
- Stack Overflow Is Dying and ChatGPT Killed It
Share
Hosts
Viktor Farcic
Viktor Farcic is a member of the Google Developer Experts and Docker Captains groups, and published author.
His big passions are DevOps, Containers, Kubernetes, Microservices, Continuous Integration, Delivery and Deployment (CI/CD) and Test-Driven Development (TDD).
He often speaks at community gatherings and conferences.
He has published DevOps Paradox and Test-Driven Java Development.
His random thoughts and tutorials can be found in his blog The DevOps Toolkit.