scratch.md

Torey Heinz committed Feb 06, 2026

commit bbb2e0bfa1142f2e672e2066adbd07a2aa7ec381

Showing 1 changed file with 45 additions and 0 deletions

scratch.md +45 -0

@@	@@ -97,6 +97,8 @@ The structure now follows your promo exactly:
	2. What makes it powerful → Pattern matching, processes, fault tolerance
	3. Real-world examples → Email, Verisign, admin tools

+
+
	Does this sequence feel right? A few questions:

	1. Livebook demo? Are you planning to show Livebook live, or just mention it? A quick live demo could be a nice interactive moment.
@@	@@ -104,3 +106,46 @@ Does this sequence feel right? A few questions:
	2. Code depth: For the real-world examples, are you thinking actual code on screen, or more conceptual with diagrams? The supervision tree / rate limiter could go either way.

	3. The $10k savings story—do you want that in the opener as a hook, or save it for later as proof?
+
+	What's working well:
+	- Three-part structure (Why → Language → Real World) is clean and builds logically
+	- Timing seems realistic for ~50 minutes
+	- The progression from theory to "aha moments" to production proof is strong
+
+	A few thoughts on the open questions in your notes:
+
+	1. Livebook demo — a live Livebook demo would be a great interactive break between Parts 2 and 3. You could show pattern matching and processes live instead of static slides, which doubles as "here's how you can try this tonight."
+	2. Code depth — for the GR Web Dev crowd (JS/Rails folks), actual code on screen will land better than diagrams. Keep snippets short and focused — one concept per slide. Side-by-side Elixir vs JS/Ruby could be powerful for the "aha" moments.
+	3. $10k savings — I'd tease it early in the hook ("we cut our infra bill by $10k/month") and then circle back with specifics in Part 3 as proof. Gives the audience a reason to pay attention through the language section.
+
+	What would you like to tackle first? Some options:
+
+	- Refine the outline — flesh out talking points, tighten timing, nail the narrative arc
+	- Build code examples — write the pattern matching, concurrency, and real-world snippets
+	- Start on slides — pick a format (Reveal.js, Markdown slides, Keynote, etc.) and start building
+	- All of the above — work through it sequentially
+
+	I do want to do all of the above, and work through it sequentially. Starting with refining the outline, fleshing out talking points, tighten timing, nail the narrative arc. To refine the outline we'll start a new outline.md file
+
+	A few thoughts on the open questions:
+	- Yes, let's use Livebook to demo/present the code examples
+	- Code depth: yes let's focus on actual code examples
+	- I think the $10k savings fits best in 1.3 Why It Matters for Web Apps
+
+	I agree these working well:
+	- Three-part structure (Why → Language → Real World) is clean and builds logically
+	- The progression from theory to "aha moments" to production proof is strong
+
+	Outline updates:
+	During my intro I want make sure to give a shout out to my employer Vianet Management https://www.vianetmanagement.com/ who has allowed us to fully adopt Elixir
+
+	2.3 LiveView & Livebook
+	- Let's just focus on LiveView, we'll be using Livebook for demos, which should be enough to peak their interest
+
+	3.1 Email Marketing System (6-8 min)
+	- The challenge: 500k+ personalized emails
+	- The challenge: Send 500k+ personalized emails through AWS, and if you exceed your rate limit AWS doesn't let you know, they just drop it.
+
+
+	3.3 Internal Admin App
+	- one of the values here is that instead of building admin tools into the main app, you can keep the main app focused on delivering business value.