1 min lesson
Switching registers is the skill
Use "Switching registers is the skill" to tell the cases apart, then choose a response for each one.
Step 1 of 2
Switching registers is the skillthe move that separates strong SAs
The same fact gets framed three ways - the claim stays true, but the register changes with the room.
Speed, flow, code quality.
"Less keystroke tax, more time on the interesting problem."
Control, safety, fit.
"Standardized config, scoped permissions, clean audit, contained blast radiusHow much breaks if a change goes wrong; the scope of potential damage. Press Enter for the full definition.."
impact, risk, return.
"Measurable cycle-time gain, managed IP risk, a defensible AI-native strategy."
Pitching ROIReturn on Investment. The value gained versus what it cost, the language an economic buyer funds deals in. Press Enter for the full definition. to developers makes you sound like a salesperson they'll tune out. Pitching keystrokes-saved to a CTO makes you sound like you can't see the business. Match the message to the room every time or you forfeit the room.
In the demo / presentation round you'll often be told to tailor to a developer vs. an exec audience. Name your audience out loud before you start: "I'm presenting to your VP of Eng, so I'll lead with cycle time and risk, then drop into the editor for ninety seconds of proof." Explicit audience-targeting is exactly the signal that round tests.