AI and humans have more in common than we think: both need clear guardrails to consistently produce the right outcomes.
AI doesn’t always follow the exact same pattern every time, and that’s where guardrails become essential. When designed thoughtfully, they can help us harness AI while creating seamless editorial experiences that stay aligned with your brand guidelines, much like the systems and processes we use to guide human teams.
Join me as I explore how to build AI-powered editorial experiences that follow your brand guidelines with minimal deviation, while making AI practical and reliable useful for WordPress teams.
AI in WordPress talks usually stop at “look what Copilot/Cursor can do for your code.” This one goes further. Over the last two years, I’ve watched AI change how a WordPress engineering team actually runs — first as a developer using AI-assisted coding, then overseeing a QA team using AI for test generation and bug triage, and now as an Engineering Director using it for planning, process improvement, and code review.
In 15 minutes, I’ll share what genuinely changed (and what didn’t) at each of those levels — where the productivity gains are real, where they’re overstated, and what it means for how you staff and structure a WordPress team going forward. You’ll leave with three concrete things to evaluate before you scale AI adoption in your own team or agency, not another tool demo.
Palliative medicine is one of medicine’s youngest subspecialties. Clinical practice often sits at the intersection of internal medicine, oncology, supportive care, ethics, sociology, and law, requiring clinicians to navigate uncertainty in highly individualized, context-dependent situations. Much of the available guidance is derived from Western populations and healthcare systems, while the realities of everyday practice in India frequently demand adaptation, interpretation, and independent critical reasoning. As a result, postgraduate training may not always address the full complexity encountered at the bedside.
My WordPress-based academic blog, “Pall MED Prep”, was created to help bridge these gaps by exploring challenging clinical questions from the perspective of both a trainee and a practicing specialist in palliative medicine. Rather than serving as a repository of answers, the blog documents the process of asking better questions, examining evidence critically, and understanding the rationale behind clinical decision-making.
This session explores the role that generative AI has played in shaping that process. Using the evolution of a single blog post as a live case study, I will demonstrate how iterative dialogue with AI can challenge assumptions, identify gaps in reasoning, compare international guidance, refine arguments, and expand the epistemic context surrounding complex clinical decisions. The emphasis is not on using AI to generate content, but on using it as a conversational partner that supports reflection, scholarship, and intellectual curiosity while preserving human judgment and domain expertise.
The session will offer practical insights for educators, clinicians, researchers, and content creators interested in integrating AI into knowledge work responsibly. Attendees will gain an understanding of how WordPress can become a platform not merely for publishing content, but for documenting an evolving dialogue between human expertise and artificial intelligence.
That’s the paradigm shift in the Content Market. Local goes global. Regional content is no longer niche—it’s the primary driver of engagement. – Rise of vernacular creators in India – Tier-2 & Tier-3 dominance – Monetization gaps & opportunities
I built Idara Reading Time — a published WordPress.org plugin — with AI assistance. Things broke that I didn’t expect: an infinite loop from do_blocks() recursion, a slug collision caught only at review, and a viewScript pattern the AI confidently suggested from outdated docs — wrong for the modern block editor, and convincing enough that I almost shipped it.
In 15 minutes, I’ll take you through these three specific places AI reliably slips in WordPress-specific code — and why each one is easy to miss even for someone reviewing carefully.
No tool demo. Just one shipped plugin, its bugs, and the one habit I now run on every AI-generated patch before it ships.
Senior Fullstack Developer, WebMS Consultancy and Idara Studio
Speaker profile
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, please see here:
Cookie Policy
