updatesHEADmaster

1 files changed, 216 insertions, 214 deletions

diff --git a/2025/captions/emacsconf-2025-bookclub-tapas--bookclub-tapas--maddie-sullivan--answers.vtt b/2025/captions/emacsconf-2025-bookclub-tapas--bookclub-tapas--maddie-sullivan--answers.vtt
index feeab999..53f9486e 100644
--- a/2025/captions/emacsconf-2025-bookclub-tapas--bookclub-tapas--maddie-sullivan--answers.vtt
+++ b/2025/captions/emacsconf-2025-bookclub-tapas--bookclub-tapas--maddie-sullivan--answers.vtt
@@ -1,5 +1,7 @@
 WEBVTT
 
+NOTE Introduction
+
 00:00.000 --> 00:07.879
 All right, take it away. Okay, am I, are we live?
 
@@ -21,14 +23,11 @@ Yeah, let me, let me see here. So I have.
 00:38.480 --> 00:41.559
 Yeah, I see, I see some, I see some questions coming in.
 
-00:41.560 --> 00:47.079
-Perfect. I am going to show my share my screen real quick.
-
-00:47.080 --> 00:54.399
-We have currently currently we have
+00:41.560 --> 00:00:53.416
+Perfect. I am going to share my screen real quick.
 
-00:54.400 --> 00:59.079
-a sort of a dross thing going.
+00:00:53.417 --> 00:00:59.079
+Currently, we have a sort of a ?? thing going.
 
 00:59.080 --> 01:04.519
 And so I just wanted to, while we're waiting
@@ -48,10 +47,12 @@ that might be even nicer.
 01:15.960 --> 01:38.159
 Yes, absolutely, gladly. Whoa, okay. There we go.
 
-01:38.160 --> 01:41.559
+NOTE Q: Did you show examples of files in bookclub style?
+
+01:38.160 --> 00:01:40.899
 All right, the first question
 
-01:41.560 --> 01:45.839
+00:01:40.900 --> 01:45.839
 was looking for examples of files in book club style.
 
 01:45.840 --> 01:48.799
@@ -64,7 +65,7 @@ to what I've been doing,
 but coming from different influences. Yes, yes.
 
 01:54.240 --> 02:03.559
-So I included a, included a,
+So I included a...
 
 02:03.560 --> 02:07.879
 Let me see, I'm just looking at the IRC here
@@ -73,15 +74,15 @@ Let me see, I'm just looking at the IRC here
 and smiling at all the people. So, yes, I provided a link.
 
 02:16.720 --> 02:19.039
-So I think that an excellent.
+So I think that an excellent...
 
 02:19.040 --> 02:24.159
 So I have gone ahead and provided
 
-02:24.160 --> 02:26.959
-the get the link to the repo
+02:24.160 --> 00:02:28.125
+the link to the repo
 
-02:26.960 --> 02:30.479
+00:02:28.126 --> 02:30.479
 and I'm going to go ahead and post that again.
 
 02:30.480 --> 02:34.039
@@ -91,25 +92,25 @@ So this should serve as a full example
 of what a just sort of standard book club file looks like.
 
 02:39.520 --> 02:41.559
-And if anyone has like specific questions
+And if anyone has specific questions
 
 02:41.560 --> 02:42.839
 about anything in particular,
 
 02:42.840 --> 02:47.799
-they would love to see my sort of like walkthrough
+they would love to see my walkthrough
 
 02:47.800 --> 02:52.239
-and narrate like specifically, you know, any place in this file
+and narrate specifically, you know, any place in this file
 
 02:52.240 --> 02:55.319
-that they would like to see me sort of like go over live,
+that they would like to see me go over live,
 
 02:55.320 --> 02:58.719
 I would be super happy to do that.
 
 02:58.720 --> 03:03.439
-So I have the whole, you know, more or less complete
+So I have the whole more or less complete
 
 03:03.440 --> 03:10.799
 book club file for Squint pulled up here.
@@ -121,22 +122,24 @@ Yeah, I have my vision laid out,
 which has my initial sort of goal.
 
 03:18.640 --> 03:22.879
-you know, the background and the vision sort of combined
+The background and the vision sort of combined
 
 03:22.880 --> 03:28.559
 to lay out what my general sort of goal is.
 
 03:28.560 --> 03:31.319
-I just realized, let me kill my stream there.
+I just realized... Let me kill my stream there.
 
 03:31.320 --> 03:39.079
 There we go. All right. There's another question.
 
+NOTE Q: The product of a Tapa like squint.org would be pure GOLD for an agent like Claude Code - have you experimented with providing an agent with the final output and letting it chew through todos?
+
 03:39.080 --> 03:41.439
 The product of a tapa like squint.org
 
 03:41.440 --> 03:44.359
-would be pure gold for an agent like Cloud Code.
+would be pure gold for an agent like Claude Code.
 
 03:44.360 --> 03:47.519
 Have you experimented with providing an agent with a final output
@@ -151,7 +154,7 @@ That would be a really excellent question.
 I actually just kind of recently
 
 03:54.920 --> 03:58.159
-got into Clawed in particular.
+got into Claude in particular.
 
 03:58.160 --> 04:01.679
 I played quite a bit with GPT and
@@ -178,7 +181,7 @@ or really just not having enough parameters
 in order to understand the context of what's going on.
 
 04:21.920 --> 04:25.759
-Cloud has completely changed my perception
+Claude has completely changed my perception
 
 04:25.760 --> 04:27.359
 of what an LLM can do or not.
@@ -253,19 +256,19 @@ oh, I just want to hand off
 the boring parts to Claude.
 
 05:34.160 --> 05:36.519
-But the thing is, if I'm writing an e-list,
+But the thing is, if I'm writing in Elisp,
 
 05:36.520 --> 05:39.479
 I find the whole thing to be kind of fun.
 
 05:39.480 --> 05:46.079
-be super, um, it would be super interested in, you know,
+I'd be super interested in, you know,
 
 05:46.080 --> 05:48.159
 just sort of as a point of exercise,
 
 05:48.160 --> 05:49.479
-like seeing what it's capable of.
+seeing what it's capable of.
 
 05:49.480 --> 05:51.479
 Because I think, I really do think
@@ -309,10 +312,12 @@ But yeah, I think that's definitely onto something.
 06:29.680 --> 06:31.439
 I've definitely thought about this.
 
-06:31.440 --> 06:33.759
+06:31.440 --> 00:06:37.919
 I've definitely been really curious about this.
 
-06:33.760 --> 06:40.279
+NOTE Q: Do you think every Tapa should have it's own Bookclub file as well? Or would you rather keep just one bookclub file in the top of the project?
+
+00:06:37.920 --> 06:40.279
 Next question, do you think every Tapa
 
 06:40.280 --> 06:42.479
@@ -339,16 +344,16 @@ the way that my brain kind of works
 07:00.800 --> 07:06.239
 is that out of sight, out of mind is very literal for me.
 
-07:06.240 --> 07:13.519
-I find that I find that. What am I thinking of?
+07:06.240 --> 00:07:16.207
+I find that... I find that... What am I thinking of?
 
-07:13.520 --> 07:19.959
+00:07:16.208 --> 00:07:18.750
 Sorry, I just saw that I got an email
 
-07:19.960 --> 07:22.799
+00:07:18.751 --> 00:07:22.839
 and I'm like, yeah, okay, cool.
 
-07:22.800 --> 07:27.319
+00:07:22.840 --> 07:27.319
 Case in point, right? We are at case in point, you know,
 
 07:27.320 --> 07:30.519
@@ -394,7 +399,7 @@ It really rewards the fact that you can pivot.
 So I find that to be really excellent.
 
 08:06.040 --> 08:08.359
-But to go back to the original a question,
+But to go back to the original question,
 
 08:08.360 --> 08:11.519
 I would definitely recommend,
@@ -405,10 +410,10 @@ at least in my circumstance,
 08:13.760 --> 08:15.679
 I find it to be incredibly useful
 
-08:15.680 --> 08:19.199
+08:15.680 --> 00:08:18.699
 to have each tapa be its own book club file
 
-08:19.200 --> 08:21.839
+00:08:18.700 --> 08:21.839
 rather than to have a unified file
 
 08:21.840 --> 08:26.599
@@ -516,10 +521,12 @@ separation of concept though.
 09:58.000 --> 10:00.639
 But however you do that is, you know,
 
-10:00.640 --> 10:01.919
+10:00.640 --> 00:10:08.039
 is best your judgment call.
 
-10:01.920 --> 10:11.399
+NOTE Q: How do you build habits when it comes to documentation?
+
+00:10:08.040 --> 10:11.399
 Next question, how do you build habits
 
 10:11.400 --> 10:13.119
@@ -550,7 +557,7 @@ or priorities change, it can be hard to keep discipline.
 Would love your thoughts. Thanks. Yes, absolutely.
 
 10:32.560 --> 10:35.719
-So what I tend to do is I don't
+So what I tend to do is I don't...
 
 10:35.720 --> 10:39.239
 So really, so far, what I've been doing
@@ -564,10 +571,10 @@ of writing documentation at all.
 10:45.360 --> 10:48.039
 And if that sounds contradictory
 
-10:48.040 --> 10:51.759
+10:48.040 --> 00:10:50.259
 to the talk, that is correct.
 
-10:51.760 --> 10:54.999
+00:10:50.260 --> 10:54.999
 What I mean by this is that I go about
 
 10:55.000 --> 11:00.039
@@ -595,10 +602,10 @@ what my internal monologue is
 for what I'm doing for that pass working on the file.
 
 11:23.520 --> 11:25.919
-So my document takes ultimate
+So my document takes ultimate...
 
 11:25.920 --> 11:29.519
-Distance of dark is ultimately a property
+Distance of doc is ultimately a property
 
 11:29.520 --> 11:32.359
 from the fact that I am writing
@@ -624,19 +631,19 @@ yeah, so let's go ahead and take a look back at the macro.
 11:53.320 --> 11:56.359
 Yeah, really, this is kind of cheating,
 
-11:56.360 --> 12:01.119
+11:56.360 --> 00:12:07.541
 because mostly I would consider this to be self-documenting,
 
-12:01.120 --> 12:07.919
+00:12:07.542 --> 00:12:09.500
 but we all kind of know that
 
-12:07.920 --> 12:11.759
+00:12:09.501 --> 12:11.759
 that in and of itself is a slippery slope.
 
-12:11.760 --> 12:14.799
+12:11.760 --> 00:12:16.167
 That's not great. Because it's like, I could believe
 
-12:14.800 --> 12:17.719
+00:12:16.168 --> 12:17.719
 that this would be self-documenting
 
 12:17.720 --> 12:19.959
@@ -646,33 +653,33 @@ if this was a three-liner.
 It is not. which, you know, also goes to show me
 
 12:24.720 --> 12:27.759
-that this needs to be splitting into its own topos.
+that this needs to be splitting into its own Tapas
 
 12:27.760 --> 12:32.239
-I intend to, you know, write a Tapa that's a sort of,
+I intend to, you know, write a Tapa
 
 12:32.240 --> 12:37.079
-that's a sort of like macro builder
+that's a sort of macro builder
 
 12:37.080 --> 12:40.559
-that automatically, you know, does the gensims for you.
+that automatically, you know, does the gensyms for you.
 
 12:40.560 --> 12:41.959
 Something along the lines of
 
 12:41.960 --> 12:46.679
-what's the common Lisp macro for that called?
+what's the Common Lisp macro for that called?
 
 12:46.680 --> 12:51.879
-It's like, There's some common list faculty
+It's like, there's some Common Lisp faculty
 
 12:51.880 --> 12:53.919
-that does automatic Jensen binding.
+that does automatic gensym binding.
 
-12:53.920 --> 12:55.479
+12:53.920 --> 00:12:57.099
 I can't quite remember what it's called.
 
-12:55.480 --> 13:01.559
+00:12:57.100 --> 13:01.559
 A prior version of this talk had my live coding that,
 
 13:01.560 --> 13:04.319
@@ -732,28 +739,30 @@ but is going to be simple enough such that
 14:02.320 --> 14:04.679
 a doc string is sufficient for documentation.
 
-14:04.680 --> 14:06.999
+14:04.680 --> 00:14:10.599
 That is not the case currently.
 
-14:07.000 --> 14:12.279
+NOTE Q: How do you write examples and tests? I think that you mentioned that during the talk, but I couldn't find them on a very quick look at your org file in the squint repo...
+
+00:14:10.600 --> 14:12.279
 All right, next question is,
 
 14:12.280 --> 14:18.559
 how do you write examples and tests?
 
-14:18.560 --> 14:24.679
+14:18.560 --> 00:14:22.750
 I think that you mentioned that during the talk,
 
-14:24.680 --> 14:27.359
+00:14:22.751 --> 00:14:25.083
 but I couldn't find them on a very quick look
 
-14:27.360 --> 14:35.239
+00:14:25.084 --> 00:14:27.833
 at your org file in the Squint repo.
 
-14:35.240 --> 14:40.519
+00:14:27.834 --> 00:14:35.208
 My use of the word test was a little bit creative.
 
-14:40.520 --> 14:42.759
+00:14:35.209 --> 14:42.759
 It's my validation of the code that I've written.
 
 14:42.760 --> 14:45.479
@@ -802,7 +811,7 @@ of the way that the program ultimately ought to behave.
 In doing so, I created a sort of embedded domain language
 
 15:43.400 --> 15:46.359
-that I have termed animal houses.
+that I have termed Animal Houses.
 
 15:46.360 --> 15:50.999
 And Animal Houses is a sort of markup language
@@ -820,19 +829,19 @@ Grammar or anything, but like, it is more or less.
 Breadth of everything that needs to be known
 
 16:08.840 --> 16:10.519
-about how animal houses works.
+about how Animal Houses works.
 
 16:10.520 --> 16:14.279
-And I've created animal houses because it is an ideal
+And I've created Animal Houses because it is an ideal
 
-16:14.280 --> 16:18.479
-and incredibly simple circumstance.
+16:14.280 --> 00:16:16.875
+and incredibly simple circumstance
 
-16:18.480 --> 16:22.679
-For how to go about as needed tests.
+00:16:20.040 --> 16:22.679
+for how to go about as-needed tests
 
 16:22.680 --> 16:28.119
-For how squint ultimately ought to work in practice.
+for how Squint ultimately ought to work in practice.
 
 16:28.120 --> 16:30.239
 So when I'm doing research,
@@ -847,46 +856,43 @@ and I will go ahead and insert it into a buffer.
 And I'll just create an analog buffer.
 
 16:46.600 --> 16:48.639
-I just called it a woo.
+I just called it awoo.
 
 16:48.640 --> 16:55.959
-And then what I'll do is in my research sections, I will write
+And then what I'll do is in my research sections, I will write...
 
-16:55.960 --> 17:01.199
+16:55.960 --> 00:17:02.919
 Like I'll write like step-by-step
 
-17:01.200 --> 17:07.919
-like instructions on how to go about with a REPL-driven detection
+00:17:02.920 --> 17:07.919
+instructions on how to go about with a REPL-driven detection
 
-17:07.920 --> 17:15.119
-using animal houses. So it does squint pass label
+17:07.920 --> 00:17:13.843
+using Animal Houses. So it does
 
-17:15.120 --> 17:16.799
-to width restriction correctly.
+00:17:13.844 --> 00:17:16.799
+squint pass label to :with-restriction: correctly.
 
 17:16.800 --> 17:20.479
 The tests conducted here indicate that it does not.
 
 17:20.480 --> 17:25.839
-And then I link to a development focus.
+And then I link to a development focus
 
 17:25.840 --> 17:29.959
-that um effectively acts as my bug report
-
-17:29.960 --> 17:33.999
-or sorry my uh you know my bug for um
+that effectively acts as my bug report,
 
-17:34.000 --> 17:37.599
-my bug listing for this particular problem
+17:29.960 --> 00:17:37.599
+or, sorry, my bug listing for this particular problem
 
 17:37.600 --> 17:38.479
-that I've identified
+that I've identified.
 
 17:38.480 --> 17:41.439
 I lay out some criteria of how to
 
 17:41.440 --> 17:44.959
-go about using the REPL to um
+go about using the REPL to...
 
 17:44.960 --> 17:47.079
 you know I identify what I believe
@@ -895,7 +901,7 @@ you know I identify what I believe
 is sort of like the quarantined area
 
 17:49.480 --> 17:50.639
-that I found for the bug
+that I found for the bug,
 
 17:50.640 --> 17:56.799
 and then test is that I will go about
@@ -921,13 +927,13 @@ Something's going on with the screen share.
 18:16.880 --> 18:18.799
 I can see your screen but
 
-18:18.800 --> 18:23.239
+18:18.800 --> 00:18:25.119
 the server cannot see your screen updating.
 
-18:23.240 --> 18:28.439
-Sorry. Oh, no. Maybe you stop switching.
+00:18:25.120 --> 00:18:30.749
+Sorry. Oh, no. Maybe you stop sharing...
 
-18:28.440 --> 18:33.399
+00:18:30.750 --> 18:33.399
 Yeah, and then we just redo it again. Thank you.
 
 18:33.400 --> 18:36.039
@@ -937,7 +943,7 @@ Yes, absolutely.
 Thanks to someone who noticed the buffer time,
 
 18:39.040 --> 18:42.919
-the time in the load line was not updating.
+the time in the mode line was not updating.
 
 18:42.920 --> 18:50.079
 Okay, let's try that again. Now it's updating. Gotcha.
@@ -967,22 +973,22 @@ that you need to write a parser for animal houses.
 Most of the tests around Squint involve
 
 19:19.360 --> 19:23.999
-writing sort of ad hoc parsers for animal houses.
+writing ad-hoc parsers for animal houses.
 
 19:24.000 --> 19:27.199
 Just when I have it in its own buffer, you know,
 
 19:27.200 --> 19:29.719
-I find more or less it's an excellent way
+I find, more or less, it's an excellent way
 
 19:29.720 --> 19:31.199
 of going about testing
 
-19:31.200 --> 19:36.359
-in an ad hoc sort of REPL driven manner.
+19:31.200 --> 00:19:35.479
+in an ad-hoc sort of REPL-driven manner
 
-19:36.360 --> 19:39.879
-that I just sort of write regular
+00:19:35.480 --> 19:39.879
+that I just sort of write regular...
 
 19:39.880 --> 19:43.799
 that pull out the pieces of the sections of buffer
@@ -1000,28 +1006,28 @@ and the houses to which they belong.
 And then when I am engaging in research,
 
 20:00.320 --> 20:03.559
-Um, you know, what, what my research section is,
+what my research section is,
 
 20:03.560 --> 20:05.079
-is I'm ultimately just sort of like
+is I'm ultimately just
 
 20:05.080 --> 20:06.399
 laying out, like, you know,
 
 20:06.400 --> 20:10.239
-I'm sort of thinking to myself, is this working right?
+I'm thinking to myself, is this working right?
 
 20:10.240 --> 20:11.319
-I feel like, like, I feel like
+I feel like
 
 20:11.320 --> 20:14.639
 there's something here, something in this area.
 
 20:14.640 --> 20:16.919
-And I'll, you know, ask myself, well,
+And I'll ask myself, well,
 
 20:16.920 --> 20:20.199
-kind of like, what is it, you know, what am I looking for?
+what is it, what am I looking for?
 
 20:20.200 --> 20:22.519
 And then nail down, how am I going
@@ -1033,16 +1039,18 @@ to go about looking for it?
 The process of working with the REPL
 
 20:30.560 --> 20:34.319
-to sort of pin down like what exactly is going on
+to pin down what exactly is going on
 
-20:34.320 --> 20:36.119
-and come to a conclusion
+20:34.320 --> 00:20:42.867
+and come to a conclusion on...
 
-20:36.120 --> 20:44.519
-on completely jumping out of order.
+00:20:42.868 --> 00:20:44.519
+Completely jumping out of order.
+
+NOTE Q: Have you experimented with something like whisper.el for doing speech-to-text as you think out loud into your Bookclub?
 
 20:44.520 --> 20:47.799
-Have you experimented in like whisper.el
+Have you experimented with whisper.el
 
 20:47.800 --> 20:49.759
 for doing speech to text
@@ -1057,7 +1065,7 @@ Now I am. I love that idea. That is awesome.
 Yeah, no, I love that.
 
 21:00.040 --> 21:04.839
-Even with, I only have a CPU, no GPU on mine,
+[Sacha]: Even with... I only have a CPU, no GPU on mine,
 
 21:04.840 --> 21:08.039
 it does capture things a lot faster.
@@ -1090,7 +1098,7 @@ so that even when I'm looking at something else,
 I can dictate into my equivalent of the book club file.
 
 21:37.920 --> 21:41.759
-Yes, yes, yes, absolutely.
+[Maddie]: Yes, yes, yes, absolutely.
 
 21:41.760 --> 21:44.719
 So you can be scrolling through documentation on, like,
@@ -1132,7 +1140,7 @@ You're not even writing into the buffer
 that you're working with. That's actually so cool.
 
 22:14.120 --> 22:17.279
-Or you can type into the org capture process
+[Sacha]: Or you can tie it into the org capture process
 
 22:17.280 --> 22:21.039
 so that it can pick up an annotation automatically.
@@ -1144,48 +1152,50 @@ Sorry, annotation is the link to the thing,
 whatever you're looking at.
 
 22:26.160 --> 22:32.999
-Oh, that's super cool. Yes. No, I actually really love it.
+[Maddie]: Oh, that's super cool. Yes. No, I actually really love it.
 
 22:33.000 --> 22:36.119
 I haven't, you know, hooking this all up to Org Capture at all.
 
-22:36.120 --> 22:58.639
-I actually really love that idea in of itself. Yeah.
+22:36.120 --> 00:22:58.199
+I actually really love that idea in and of itself. Yeah.
 
-22:58.640 --> 23:01.119
-Or a capture will give you a lot of capture options.
+00:22:58.200 --> 23:01.119
+[Sacha]: Org capture will give you a lot of capture options.
 
 23:01.120 --> 23:03.159
-Like you can capture to your currently
+You can capture to your currently
 
 23:03.160 --> 23:11.039
-clocked in, uh, heading. So then it just files your note
+clocked in heading. So then it just files your note
 
-23:11.040 --> 23:12.919
+23:11.040 --> 00:23:15.059
 in the right place automatically.
 
-23:12.920 --> 23:19.199
-Absolutely. I love that. Let me see.
+00:23:15.060 --> 23:19.199
+[Maddie]: Absolutely. I love that. Let me see.
 
-23:19.200 --> 23:22.279
+23:19.200 --> 00:23:21.099
 I'm actually like writing a note to try that out.
 
-23:22.280 --> 23:25.159
+00:23:21.100 --> 00:23:23.125
 I'm definitely going to have to do that.
 
-23:25.160 --> 23:36.039
+00:23:23.126 --> 23:36.039
 Like the flexibility of that in particular sounds just perfect.
 
 23:36.040 --> 23:38.239
-I'd like to finish typing noises
+[Sacha]: I'll let you finish typing noises
 
 23:38.240 --> 23:39.679
 and then we can ask the next question
 
-23:39.680 --> 23:41.239
+23:39.680 --> 00:23:42.291
 for which there is one.
 
-23:41.240 --> 23:45.839
+NOTE Q: What is the largest project in terms of team size you had the chance to consult and introduce the Bookclub Tapas concept and what have been your experiences with these setups (implying larger applications / solutions a company is working on)?
+
+00:23:42.292 --> 23:45.839
 The question is, what is the largest project
 
 23:45.840 --> 23:48.479
@@ -1392,22 +1402,24 @@ Sort of get a solid idea of scope and function,
 26:51.240 --> 26:57.199
 do pre-planning as we're going into more specifics
 
-26:57.200 --> 27:01.359
+26:57.200 --> 00:27:03.375
 on what the overall look for the project
 
-27:01.360 --> 27:03.479
+00:27:03.376 --> 00:27:04.250
 and how it ought to look
 
-27:03.480 --> 27:05.679
+00:27:04.251 --> 27:05.679
 and how it all ought to be laid out.
 
 27:05.680 --> 27:11.519
 So there's a lot of really exciting flexibility there
 
-27:11.520 --> 27:13.199
+27:11.520 --> 00:27:21.999
 that I think is really cool.
 
-27:13.200 --> 27:23.679
+NOTE Q: People will also be curious about the mechanics of collaboration: other person uses Emacs and Org? Shipping things back and forth via git / version control? CRDT?
+
+00:27:22.000 --> 27:23.679
 People will, of course, be curious
 
 27:23.680 --> 27:25.919
@@ -1438,7 +1450,7 @@ where I could get you know, clients and partners,
 like, you know, really excited
 
 27:53.360 --> 27:54.799
-about using Emacs on org.
+about using Emacs and Org.
 
 27:54.800 --> 27:58.559
 But, you know, it's, it can be a little bit to ask,
@@ -1450,67 +1462,64 @@ I would love to see if I can, like,
 put together some sort of a config that,
 
 28:01.880 --> 28:04.519
-like, sands off all of this and, you know,
+like, sands off all of this and
 
 28:04.520 --> 28:08.079
-makes this this really, you know, you know,
+makes this this really
 
 28:08.080 --> 28:13.759
-like safety-proof sort of intuitive environment
+safety-proof sort of intuitive environment
 
 28:13.760 --> 28:16.599
 just for CRDT in particular.
 
 28:16.600 --> 28:18.879
-I love the idea of like, you know,
+I love the idea of
 
 28:18.880 --> 28:21.479
-sort of like spawning CRDT
+spawning CRDT
 
 28:21.480 --> 28:24.159
-so that like, you know, the two of us can,
+so that the two of us can
 
 28:24.160 --> 28:27.559
-you know, type SPAC and ideas
+type-spec an ideas
 
 28:27.560 --> 28:31.239
-and sort of like draft together on, you know,
+and draft together on, you know,
 
 28:31.240 --> 28:33.559
-especially like the glue code tapa
+especially like the glue code Tapa
 
 28:33.560 --> 28:35.639
 for a larger software stack.
 
 28:35.640 --> 28:38.399
-like collaborating on that over CRDT
+Like, collaborating on that over CRDT,
 
 28:38.400 --> 28:43.399
-or having folks step through Tapas and,
-
-28:43.400 --> 28:45.599
-you know, unfold them and like, you know,
+or having folks step through Tapas and
 
-28:45.600 --> 28:46.719
-point to a particular thing.
+28:43.400 --> 00:28:46.719
+unfold them and point to a particular thing...
 
 28:46.720 --> 28:49.159
-And it's like, you know, like, what's, what's this?
+And it's like, you know, what's this?
 
 28:49.160 --> 28:50.119
 What's the clock here?
 
 28:50.120 --> 28:52.239
-It looks like we're spending a lot of time
+It looks like we're spending a lot of time,
 
 28:52.240 --> 28:54.519
 and I would like to get a little bit clearer
 
 28:54.520 --> 28:56.319
-of an idea of like what exactly we're doing here.
+of an idea of what exactly we're doing here.
 
 28:56.320 --> 29:01.319
-back up a little bit because the stream just disconnected
+Back up a little bit because the stream just disconnected
 
 29:01.320 --> 29:02.759
 and reconnected from the audio.
@@ -1519,16 +1528,16 @@ and reconnected from the audio.
 So, please repeat just the last sentence.
 
 29:06.600 --> 29:11.959
-Yeah, yeah, for sure. Yeah, so I would like, you know,
+Yeah, yeah, for sure. Yeah, so I would like...
 
 29:11.960 --> 29:18.239
-I love the idea of, yeah, like, you know, collaborating on,
+I love the idea of collaborating on,
 
 29:18.240 --> 29:20.519
-especially like on the glue code.
+especially on the glue code.
 
 29:20.520 --> 29:23.839
-tapa for a particular software stack, you know,
+Tapa for a particular software stack, you know,
 
 29:23.840 --> 29:26.159
 having the both of us use CRDT
@@ -1540,31 +1549,31 @@ to type into it simultaneously,
 I think that would be super cool.
 
 29:30.160 --> 29:33.679
-I also really love the idea of, you know,
+I also really love the idea of
 
-29:33.680 --> 29:38.159
-having a client or partner, you know,
+29:33.680 --> 00:29:37.139
+having a client or partner
 
-29:38.160 --> 29:41.479
-thumb through individual tapas in the stack.
+00:29:37.140 --> 29:41.479
+thumb through individual tapas in the stack
 
 29:41.480 --> 29:45.639
-And then like, you know, like, look at and be like,
+and then look at and be like,
 
 29:45.640 --> 29:47.879
 well, we seem to have time on this recently,
 
 29:47.880 --> 29:51.759
-can you give me like, some clarification on like,
+can you give me some clarification on
 
 29:51.760 --> 29:55.519
-you know, what, what this part is and how it's, you know,
+what this part is and
 
 29:55.520 --> 29:57.559
 what it means for the whole
 
 29:57.560 --> 30:00.799
-and sort of like what, you know, what it represents
+and what it represents
 
 30:00.800 --> 30:02.599
 in terms of how all of this is going to come together.
@@ -1573,16 +1582,16 @@ in terms of how all of this is going to come together.
 I think that would be super cool. I love the idea of that.
 
 30:06.440 --> 30:11.679
-I would even consider like, you know, if not Emacs proper,
+I would even consider, if not Emacs proper,
 
 30:11.680 --> 30:17.119
-I would love like, you know, maybe a, a web-based org parser.
+I would love maybe a web-based Org parser
 
 30:17.120 --> 30:21.399
-for, you know, even on just a read-only version
+or even just a read-only version
 
 30:21.400 --> 30:25.399
-of the document where, you know, clients and partners, yeah,
+of the document where clients and partners
 
 30:25.400 --> 30:26.879
 just sort of thumb through with it
@@ -1591,19 +1600,19 @@ just sort of thumb through with it
 and then chat with questions.
 
 30:28.200 --> 30:34.159
-Make the, you know, screen sharing for, you know,
+Make the screen sharing for
 
 30:34.160 --> 30:36.519
 peer programming process
 
 30:36.520 --> 30:41.599
-just a little bit cleaner, you know, more intuitive on their end.
+just a little bit cleaner, more intuitive on their end.
 
 30:41.600 --> 30:50.399
 I think that'd be super cool. I love these ideas.
 
 30:50.400 --> 30:55.002
-All right, theoretically, the big blue button is open.
+[Sacha]: All right, theoretically, the Big Blue Button is open.
 
 30:55.003 --> 30:57.002
 I think we've gotten to the end
@@ -1615,7 +1624,7 @@ of the questions on the etherpad.
 If anyone else would like to join or ask,
 
 31:03.086 --> 31:04.840
-I'm gonna need a couple of minutes
+I'm going to need a couple of minutes
 
 31:04.841 --> 31:06.359
 and then I can do closing remarks
@@ -1623,11 +1632,11 @@ and then I can do closing remarks
 31:06.360 --> 31:07.999
 whenever people are ready.
 
-31:08.000 --> 31:14.479
+31:08.000 --> 00:31:19.559
 So I will meet now when people figure things out.
 
-31:14.480 --> 31:22.039
-I would also be super down if, you know,
+00:31:19.560 --> 31:22.039
+[Maddie]: I would also be super down if, you know,
 
 31:22.040 --> 31:25.319
 anyone was curious about hearing more
@@ -1642,25 +1651,22 @@ that I was kind of rambling
 at the close of the talk,
 
 31:34.680 --> 31:36.479
-if people wanted to, you know,
+if people wanted to
 
 31:36.480 --> 31:39.359
-hear more about, um, some of my ideas
+hear more about some of my ideas
 
 31:39.360 --> 31:42.799
-in regards to, um, uh,
+in regards to
 
 31:42.800 --> 31:45.719
-what am I thinking at home with the, uh,
+what am I thinking at home with the...
 
 31:45.720 --> 31:49.759
 What's it called?
 
-31:49.760 --> 31:53.479
-Yeah, yeah, just sort of the, you know,
-
-31:53.480 --> 31:55.439
-some of the funding for passion projects,
+31:49.760 --> 00:31:55.439
+Just some of the funding for passion projects,
 
 31:55.440 --> 31:58.319
 I would be interested in laying out some of the ideas
@@ -1675,10 +1681,10 @@ And I think that that would be, you know,
 really cool for the whole ecosystem,
 
 32:04.720 --> 32:06.719
-because I think that there are definitely,
+because I think that there are definitely
 
 32:06.720 --> 32:09.639
-you know, things that we could bang out, you know,
+things that we could bang out, you know,
 
 32:09.640 --> 32:12.919
 for getting kind of all sorts of people on that model.
@@ -1687,25 +1693,22 @@ for getting kind of all sorts of people on that model.
 I think that it would be really cool
 
 32:14.520 --> 32:18.399
-to to having a, you know, funding model
+to to having a funding model
 
 32:18.400 --> 32:20.239
 for things that are really worth using.
 
-32:20.240 --> 32:26.519
-um and developing um the other thing is like
-
-32:26.520 --> 32:28.199
-you know just sort of um yeah
+32:20.240 --> 00:32:29.259
+And developing the other thing is
 
-32:28.200 --> 32:31.559
+00:32:29.260 --> 00:32:31.199
 just rattling off specifics on things
 
-32:31.560 --> 32:34.960
-that people could potentially vote for uh on that
+00:32:31.200 --> 32:34.960
+that people could potentially vote for on that,
 
 32:34.961 --> 32:53.759
-and in terms of specific might want to work on
+and in terms of specific "might want to work on"...
 
 32:53.760 --> 32:56.877
 All right, there's a question from IRC.
@@ -1720,7 +1723,7 @@ Let's see. Where is it?
 I will copy it from IRC. Thank you.
 
 33:12.360 --> 33:14.319
-Gotcha. Into the past.
+Gotcha. Into the pad.
 
 33:14.320 --> 33:27.759
 Perfect, perfect, perfect.
@@ -1728,6 +1731,8 @@ Perfect, perfect, perfect.
 33:27.760 --> 33:30.679
 Let me read the question out loud so it's in the recording.
 
+NOTE Q: I guess a major pro is it has less friction as people can do (a lot, maybe not everything) in BookClub Tapas file vs. having to log into gazillions of different systems, each one of them keeping a portion of the information. Did I get that viewing point right from your elaboration of the collaboration between you and your team mate(s)?
+
 33:30.680 --> 33:33.719
 I guess a major pro is it has less friction
 
@@ -1735,7 +1740,7 @@ I guess a major pro is it has less friction
 as people can do a lot,
 
 33:35.760 --> 33:39.039
-maybe not everything in book lab tapas files
+maybe not everything in Bookclub Tapas files
 
 33:39.040 --> 33:42.639
 versus having to log into gazillions of different systems,
@@ -1755,17 +1760,14 @@ between you and your teammates?
 33:52.160 --> 33:55.439
 Yes. No, that's absolutely right.
 
-33:55.440 --> 33:57.999
-um because yeah like really
-
-33:58.000 --> 34:00.519
-my hope is that we can you know
+33:55.440 --> 00:34:00.519
+Because my hope is that we can you know
 
 34:00.520 --> 34:03.239
-there's there's a lot of conflict into that
+there's a lot of conflict into that...
 
 34:03.240 --> 34:13.359
-we assume that a lot of um pieces of tooling
+We assume that a lot of um pieces of tooling
 
 34:13.360 --> 34:14.559
 and the separation between them