Salesforce Winter '26 release notes: Trusted Mode and Flow testing with CLI

🎥 Every Salesforce Developer needs to hear this... When I started my journey as a Salesforce Developer, I made almost every mistake possible. Code that broke in production. Triggers that didn’t scale. Hardcoded IDs that haunted me weeks later 😅 But here’s the truth — mistakes are not failures. They’re lessons in disguise. Every broken deployment taught me how to build better. Every error message made me a stronger developer. In my latest YouTube video, I’m sharing the Top 5 Mistakes Salesforce Developers Make — and how YOU can avoid them. These are the lessons I wish someone had told me earlier — the ones that separate average developers from exceptional ones. If you’re serious about becoming a world-class Salesforce Developer, this video will save you countless hours of frustration (and maybe even a few gray hairs 🤣). 🎯 Learn what NOT to do — and how to build clean, scalable, and future-proof Salesforce code. Because great developers aren’t born… they’re built through mistakes, discipline, and consistency. 💪 #Salesforce #SalesforceDeveloper #Apex #TrailblazerCommunity #CareerGrowth #Motivation #Learning 👉 Watch here: https://lnkd.in/gm4HUhZg

😅 Salesforce Dev Confession: I’ve lost count of how many times I’ve hit the dreaded error: 👉 “You have uncommitted work pending. Please commit or rollback before calling out” 😶 The first time it happened, I thought “ok… Salesforce just doesn’t like me today”. But nope ... the real issue is: ❌ I mixed DML and callouts in the same transaction. ✅ How I fixed it (and kept my sanity) Callout first, then DML , quick example: public class AccountNotifier implements Queueable {   public void execute(QueueableContext context) {     // Callout     HttpRequest req = new HttpRequest();     req.setEndpoint('callout:MyAPI');     req.setMethod('GET');     HttpResponse res = new Http().send(req);     // DML     Account acc = [SELECT Id FROM Account LIMIT 1];     acc.Description = 'Synced with API';     update acc;   } } Or use @future(callout=true), Queueable, or Continuation to separate them. Now, whenever I see this error, I just laugh… and then refactor my code 😅. 💡 Pro tip: Queueable jobs are a lifesaver here clean, simple, and async-friendly. 👉 And you? Have you already been haunted by this error? How did you survive it? #Salesforce #Apex #Integration #DevLife #OopsMoments

🔥 The Biggest Lesson I Learned in My First Year with Salesforce 🔥 It’s not Apex. It’s not Flows. It’s not even mastering security or automation. 👉 The biggest lesson? Salesforce is less about code… and more about people. ✅ Build with the user in mind. ✅ Communicate with your team. ✅ Learn from the community. Because features don’t drive adoption — experiences do. My first year taught me that success in Salesforce isn’t just technical. It’s human. 💡 Curious — what’s the biggest lesson you learned in your first year with Salesforce (or tech in general)? 👇 #Salesforce #TrailblazerCommunity #CareerGrowth #LearningJourney

🧠 Salesforce Pros — This Free Video Course Is for You. Even if you’ve never written a line of Apex, you’re still building software. Whether you’re a Developer, Architect, or Admin, your real job is translating business needs into systems that actually work. That’s why I’m reframing my “Soft Skills for Software Developers” series for a broader audience: Software Solution Builders. The first course, Gather Ye Requirements While Ye May, focuses on mastering the business-understanding side of solution design — before you ever touch configuration or code. It’s just as relevant to Salesforce Admins, Architects, and Developers. Same best practices. Same make-or-break gotchas. It all compiles to code in the end. Implementation is secondary. Planning is primary. Link to video in first comment. #Salesforce #SalesforceAdmins #SalesforceArchitect #SalesforceDevelopers #BusinessAnalysis #SolutionArchitecture #Codality #AIforDevelopers

🚀 Are You Writing Apex Like a Developer… or Like an Architect? Most Salesforce developers start with "make it work." But as your org grows, messy code turns into technical debt, performance issues, and sleepless nights before deployments. That’s where architect-approved coding standards come in. ✅ Clean, modular code ✅ Scalability in mind ✅ Reusable design patterns ✅ Error handling done right ✅ Bulkification as second nature Think of it this way: Good code solves today’s problem. Great code prevents tomorrow’s problems. I’ve written a detailed breakdown of Apex best practices every developer should adopt to level up their coding game. If you want to write Apex that your future self (and your architect) will thank you for — this is for you. 👉 Read the full blog here: https://lnkd.in/ggSwu5UU #Salesforce #Apex #BestPractices #SalesforceArchitect #CodingStandards

Write Cleaner, Smarter Apex! ⚡ Sharing a few tips and best practices from real-world — designed to help you write cleaner, faster, and more maintainable code. Whether you’re an Admin, Developer, or Architect, these insights will help you avoid common mistakes, optimize performance, and build scalable solutions with confidence. 📝 Slides reused from my session at Salesforce Dev Days 2023. 💬 Have questions about Apex? Let’s talk and connect! #Salesforce #Apex #SalesforceDeveloper #BestPractices #TrailblazerCommunity

𝐈𝐟 𝐲𝐨𝐮𝐫 𝐟𝐢𝐫𝐬𝐭 𝐢𝐧𝐬𝐭𝐢𝐧𝐜𝐭 𝐢𝐬 𝐀𝐩𝐞𝐱, 𝐲𝐨𝐮’𝐫𝐞 𝐚𝐥𝐫𝐞𝐚𝐝𝐲 𝐝𝐨𝐢𝐧𝐠 𝐢𝐭 𝐰𝐫𝐨𝐧𝐠. Here’s the truth 👇 I’ve seen too many Salesforce developers jump straight into writing code for problems that could’ve been solved in minutes with Flows, Validation Rules, or Configurations. It feels powerful in the moment — but a year later, that same org is drowning in 𝐭𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐝𝐞𝐛𝐭. Apex is powerful, yes. But power without discipline is dangerous. Every line of code you write today is maintenance for someone tomorrow , and when you skip declarative tools, you’re not being a “𝒑𝒓𝒐-𝒄𝒐𝒅𝒆𝒓” — you’re making the system harder, slower, and more expensive to run. Here’s what I believe ⬇️ Most real-world solutions should start with declarative tools. ✅ Flows handle 80% of automation. ✅ Validation rules cover most guardrails. ✅ Sharing & config solve more than people think. Apex should be the last resort, not the first. The best developers aren’t the ones who write the most code — they’re the ones who write the least code necessary to solve the business problem. 👉 Next time a requirement lands on your desk, ask yourself: “Can this be solved without code?” #Salesforce #Apex #DeclarativeFirst #TechnicalDebt #SalesforceOhana #SalesforceAdmin #SalesforceDeveloper

It is an excellent tool when processing data in Salesforce, but it is also important to know the batch size before processing and prevent the asynchronous process from overlapping with others.