GPT-5.6: Which Model and Effort Should You Actually Use?
GPT-5.6 is a meaningful step beyond GPT-5.5, but choosing well means using Terra by default, Sol deliberately, and Luna only for bounded work.
darwin / arm64 · tty0 · online
Code, Systems, and Side Quests
Personal notes on software, experiments, and everyday life from me.
~/blog/latest · page 1/2
Latest Posts
Trigger Architecture Without a 40-Class Framework
Most Apex trigger logic needs one entry point, thin routing, bulk-safe services, and change-aware guards. It does not automatically need a metadata-driven framework.
Partial-Success Apex: Database Methods Done Properly
Database methods can let valid records succeed while invalid records fail, but partial DML is only useful when every input receives an explicit, inspectable outcome.
Screen Flow Component Validation Without Surprises
Flow screen validation is a three-method contract. Keep internal and external errors separate, render them at the right time, and never make navigation depend on accidental component state.
Apex User Mode Is Not Your Whole Security Model
User mode closes important CRUD, field-security, and record-access gaps, but secure Apex still needs authorised operations, untrusted-input handling, safe errors, and reviewed privilege boundaries.
Props, Events, LMS, or State Manager?
LWC communication gets easier when the mechanism matches the relationship: properties down, events up, LMS across page boundaries, and state managers across a complex component subtree.
Testing LWC Behaviour, Not Implementation Details
Useful LWC tests exercise public properties, user interactions, rendered outcomes, events, and data states. Brittle tests merely describe today's private markup.
Queueable Apex That Survives Retries
Queueable Apex becomes reliable when jobs are treated as at-least-once work: use idempotency keys, durable checkpoints, bounded retries, and outcomes you can inspect.
An Error Contract for LWC, Apex, and Flow
Errors become much easier to handle when LWC, Apex, and Flow agree on a small contract: stable codes for automation, safe messages for people, and correlation details for support.
Bulk-Safe Invocable Apex
An invocable method receives a list for a reason. Treat every request as independent, query and write in collections, and return one useful outcome for every input.
Where Flow Should End and Apex Should Begin
Flow and Apex overlap, but they are not interchangeable. I use Flow for visible orchestration and Apex when data structures, transaction control, scale, or reuse become the real problem.
LDS vs GraphQL vs Apex: How I Choose an LWC Data Layer
LDS, GraphQL, and Apex can all put Salesforce data into an LWC. The useful question is not which one is best, but which is the smallest honest fit for the operation.
Seven Summer '26 Flow Updates That Add Up
Summer '26 has a cluster of small Flow improvements that make automation safer, faster, and easier to configure: unanimous approvals, scheduled-flow batching, date operators, better data tables, styling overrides, and cleaner Apex-defined inputs.
Two Small Summer '26 Reporting Changes That Will Save Admins Time
Summer '26 adds brand colour palettes for report and dashboard charts, and lets Salesforce reports use up to two row-level formulas. Neither change is flashy, but both remove annoying reporting compromises.
Flow-Friendly Apex Is Becoming Its Own Design Discipline
Summer '26 makes Apex actions easier to configure in Flow Builder. The opportunity is bigger than nicer inputs: build actions admins can use safely without reading the source.
Normal Salesforce Dashboards Are Getting Custom LWC Widgets
Summer '26 adds custom Lightning Web Components to normal Lightning dashboards, creating a focused escape hatch when standard report widgets are not enough.
Apex Multiline Strings and Interpolation in Summer '26
Summer '26 gives Apex readable multiline strings and String.template() interpolation. They improve payloads, emails and tests, but do not make dynamic SOQL safe.
State Managers for LWC: Be Excited, Keep Your Components Raw
Summer '26 gives LWC a native state layer. Use it to coordinate complex pages without coupling every reusable component to one state shape.
How to Use Release Manager's Dev Channel Without Blowing Your Foot Off
Summer '26 puts preview features behind Release Manager's Dev channel. Use it to learn early without making preview code a hidden production dependency.
Live Preview and the New LWC Dev Loop in Summer '26
Summer '26 makes Single Component Live Preview and the VS Code extension generally available for LWC, shortening the edit, preview and fix loop.
Virtualized LWC Lists for 100,000 Alarms
Summer '26 dynamic lists point to the right pattern for huge LWC datasets: render the viewport, page the data and keep 100,000 rows out of the DOM.
Elastic Async Limits for Queueable and Future Jobs
Summer '26 adds elastic async limits for Queueable and future jobs. The real opportunity is to shed low-priority work before the extra headroom runs out.
Blob.toPdf() Rendering Changes in Summer '26
Blob.toPdf() keeps the same Apex API, but Summer '26 moves rendering to the Visualforce PDF service, which can change fonts, wrapping and page breaks.
Migrating WITH SECURITY_ENFORCED to WITH USER_MODE
A focused migration guide for replacing WITH SECURITY_ENFORCED with WITH USER_MODE before moving Apex classes to API 67.0.