by ramses0 | 2025-10-31 17:27:04+00:00
Not at all! So for example at ~20-25m, you're explaining "the revset engine"

Just basically flip the first two bullet points:

Situation: "Our repo shape can assume: ..."

Consequences: "Non-mainline graphs fit in memory ..."

Actions: "Tada! Revset engine!"

Result: "Monotonic commit numbers"

Impact: "b/c we can sort ranges => unlocks filtering, client-side processing, etc"

(please excuse my poor understanding of the DETAILS of `jj-at-goog` internals, so I'm butchering some of the details of impact, etc).

...another comment mentioned "death by powerpoint". You can still do/make your slides as you're currently doing it, but when you're "done", just move all the text down into the "speakers notes", and focus on providing some illustrations or comparisons for the visual portion.

Example here: https://share.google/images/tWSmujLgnX2gDvtgL

On the revset, a bunch of it could be helped by "illustrating the impact" or "compare and contrast"

| RevSet | Git-on-ext3 | +----------------+----------------+ | Indexed | FS-Traversal | | Working Memory | Disk Cache | | Strong Server | Local Limits | | 456 > 123 | $RAND != $RAND | ...etc...

...and in your speakers notes, you can record some of the technical details you want to talk through.

You're so deep in the weeds it's like asking a fish what they think about water (and to clarify: I'm absolutely not meaning this in any sort of insulting way)... it's just that when you're communicating to others, you may have to end up moving "back and forth" or "up and down" ... illustrated: https://www.youtube.com/watch?v=3amL4O8BSAg ... stretching things out so you can see the individual threads then putting them back, or giving them a twist and blending in a new topic.

Because of your intimate familiarity with the inner workings, sometimes in your talk you're describing an inner working (ie: there's 206 bones in the human body!) but there's no context about what makes that better, or worse, or how they're conceptually connected with each other.

On the grand scale, what is the IMPACT you want your talk to have? To put words into your mouth: "We're about to go GA at google, which is a big deal."

How do you get there? Where did you start from? To put words into your mouth: "JJ is solving google-scale problems, and there's _demand_ and _support_ for bringing it about." [that's your situation]

Consequences? Actions? => now you have set the scene for your very same technical deep dives on JJ.

1) Google has big problems, JJ is solving lots of them!

2) The consequences of (jj-solving-them) or (suffering-further-with-git) are: ...

3a) The actions that have helped jj forge ahead (better than git) are: ...

3b) The actions that jj reduces suffering compared to git are: ...

4) ...as a result, we're about to go GA

5) The impact is increased community trust, improved internal development capabilities, etc...

...again: it's _mostly_ about rearranging things, and providing a little bit more context so that what you _are_ presenting hits your audience better. (3a and 3b are kindof what your current presentation was all about... just set it up a little more on how those interact with the larger picture)

Situation: You've done a great technical thing, and are being asked to present more and be an advocate for it (and yourself)

Consequences: ...if people don't understand JJ, there will be less adoption, or people that would be well-served by it won't use it, or won't contribute

Action: ...you're taking feedback on presentation skills, will continue your systematic learning and iterative improvement approach to this tech-adjacent skill

Result: Butterflies! Rainbows! 150% increase in JJ contributors and 5000% increase in JJ adoption... world peace imminent! :-P

<3 ... best of luck, and free free to reach out if you'd like to continue the conversation!