Salesforce Metadata | Technical Debt, Code Analyzer, Packaging | Defragging the Franken Org - E2
Salesforce metadata is not just configuration anymore — it is execution context. In 2026, bad metadata does not merely make your org untidy. It makes Flows brittle, Apex risky, deployments painful, and AI agents confidently chaotic. In this session, we walk through how a Salesforce Technical Architect should assess metadata quality across schema, code, automation, security, UX, and configuration. We’ll use modern Salesforce practices and tools including Salesforce Code Analyzer, VS Code integration, Prompt Builder / Agentforce patterns, Unlocked Packages, and source-driven cleanup governance. What we cover how to assess Salesforce metadata through an architect lens what “good” looks like for Apex, LWC, Flow, schema, and configuration how to identify technical debt safely how to prioritise cleanup for Agentforce readiness how to use Salesforce Code Analyzer in the 2026 workflow how to track cleanup progress and enforce quality gates in delivery Who this is for Salesforce Technical Architects Solution Architects Senior Developers Design Authority Leads Admins modernising legacy orgs Session promise By the end, you’ll have a practical way to answer the question: “Is this metadata healthy enough to scale automation, AI, and future delivery?” Salesforce Developers: Aura introduction / use LWC instead of Aura https://developer.salesforce.com/docs... Salesforce Developers: Migrate Aura components to Lightning Web Components https://developer.salesforce.com/docs... Salesforce Developers: Code Analyzer ESLint engine https://developer.salesforce.com/docs... Salesforce Developers: Code Analyzer release notes https://developer.salesforce.com/docs... Salesforce Developers: Security for Lightning Components https://developer.salesforce.com/docs... Salesforce Developers: Lightning Web Security introduction https://developer.salesforce.com/docs... Salesforce Developers: LWS sanitization https://developer.salesforce.com/docs... Salesforce Developers: Enable LWS in an org https://developer.salesforce.com/docs... Salesforce Developers: Aura validation using ESLint https://developer.salesforce.com/docs... Salesforce Developers: Supported JavaScript for Aura https://developer.salesforce.com/docs...

Legacy Salesforce Org Audit LIVE: Are You Agentforce Ready? | Defragging the Franken Org - E1

The Future of AI Agents with Andrew Ng | Interrupt 26

Dapr 1.18 Celebration Event Webinar

Salesforce Well-Architected Framework: ADAPTABLE — Resilient & Composable Architecture

Claude Architect: Multi-Agent Orchestration

Talk on “Bias in LLMs (Large Language Models): Awareness, Impact, and Action”

Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker

What is SonarQube | Introduction SonarQube | SonarQube Tutorial | SonarQube Basics | Intellipaat

Andrej Karpathy: From Vibe Coding to Agentic Engineering w/ Stephanie Zhan

Model Context Protocol (MCP) Explained for Beginners: AI Flight Booking Demo!

Instant Focus Mode – 40Hz Gamma Brainwave Music for Deep Focus & Productivity

Full Walkthrough: Workflow for AI Coding — Matt Pocock

Andrew Ng: Building Faster with AI

System Design Explained: APIs, Databases, Caching, CDNs, Load Balancing & Production Infra

What do tech pioneers think about the AI revolution? - The Engineers, BBC World Service

Assess, Prevent & Fix Your Legacy Data for Agentforce 360 | Defragging the Franken Org - E3

Spec-driven Development with Kiro

How Instagram Scaled Postgres to 2 Billion Users

Salesforce Well Architected - TRUSTED - Building Solutions That Don't Betray You

