Simon has been an avid WordPress user since 2008. While working as a Product Manager in a Open Source security company, he also dabbles with writing blog posts and newsletters and talking in podcasts about WordPress. He is an active community member and spends quite some time organizing meetups and helping the community.
[ENG] Who Owns the Plugin That Broke Production?
Vibe coding has found its way into CMS workflows. Extensions and Designs are prompted into existence, or assembled from loose suggestions and thoughts. Intentions turn into somewhat shippable products without a full read-through. That's not necessarily a problem. But it does shift something in how responsibility is distributed, and that shift hasn't been talked about much yet. This talk comes from looking at that question from three distinct angles. As a product person, a developer, and a security company. From watching how AI-assisted development interacts with CMS security, and where the gaps tend to appear. Let's take a look at how shit can hit the fan and more importantly how to avoid it.
