1 files changed, 48 insertions, 5 deletions

diff --git a/2023/talks/parallel.md b/2023/talks/parallel.md
index ea966383..8806e7c2 100644
--- a/2023/talks/parallel.md
+++ b/2023/talks/parallel.md
@@ -1,13 +1,13 @@
-[[!meta title="Parallel Text Replacement: Does P = NP?"]]
-[[!meta copyright="Copyright © 2023 Lovro"]]
+[[!meta title="Parallel Text Replacement"]]
+[[!meta copyright="Copyright © 2023 Lovro, Valentino Picotti"]]
 [[!inline pages="internal(2023/info/parallel-nav)" raw="yes"]]
 
 <!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
 <!-- You can manually edit this file to update the abstract, add links, etc. --->
 
 
-# Parallel Text Replacement: Does P = NP?
-Lovro - IRC: hokomo, <mailto:hokomo@airmail.cc>
+# Parallel Text Replacement
+Lovro, Valentino Picotti - IRC: hokomo, <mailto:hokomo@disroot.org>
 
 [[!inline pages="internal(2023/info/parallel-before)" raw="yes"]]
 
@@ -18,7 +18,7 @@ replacement.
 efficiency through parallelism, but to the concept of performing 
 more than one text replacement without them interfering with 
 each other. This is in line with the usage of the term in the 
-Lisp community when contrasting the behaviors of LET and LET\*, 
+Lisp community when contrasting the behaviors of LET and LET*, 
 SETQ and PSETQ, etc. (e.g. 
 <http://www.lispworks.com/documentation/lw60/CLHS/Body/s_let_l.htm>).
 
@@ -37,6 +37,49 @@ alternatives. Our current best candidate is "replace-parallel"
 welcome.
 
 
+# Discussion
+
+## Questions and answers
+
+-   Q: This looks great, and was very well-presented.  Do you have plans
+    to upstream this functionality into Emacs?
+    -   A: Would require some refactoring upstream, so not suitable for
+        upstreaming as-is.
+-   Q: Did you use pair-programming while developing it, or did you work
+    independently, alternating and reviewing?
+    -   A: Yes, we did! I was at the keyboard, Valentino was at the
+        whiteboard, and we kept bouncing ideas back and forth, trying
+        out prototypes, coming up with various tests, checking the edge
+        cases, etc.
+-   Q: What is your background in programming? Was it difficult to
+    implement following the same API and architecture as what is already
+    in Emacs?
+    -   A: Both Valentino and I are PhD students in computer science,
+        but a PhD or similar is definitely not a requirement. It wasn't
+        too difficult because we could reuse the interactive
+        functionality from query-replace's internals. Figuring out what
+        and how to reuse is what took a bit of creativity, but a lot of
+        the necessary knowledge for that came from just reading and
+        poking around Emacs' replace.el. Don't be afraid to go and
+        read the source!
+-   Q: What did you learn about Emacs programming or programming in
+    general while working on this project?
+    -   A: That Emacs is so flexible that you can even advise its
+        `message` function. Similarly, being able to prototype
+        functionality so quickly and immediately integrate it into the
+        rest of Emacs is so fun and so satisfying!
+
+## Notes
+
+-   One usecase could be character names in a novel manuscript, if one
+    has named a character and want to now rename it to some other
+    character names or swap it with another one.
+- Nice, I was wondering if it utilized `rx`
+- package installed, ready to use!
+- excellent talk, and also such a cool package
+- great talk, very clever concept
+- that SRE "paper" you linked to is interesting
+- just saw the "Parallel Text Replacement" talk - 👏 great talk!
 
 [[!inline pages="internal(2023/info/parallel-after)" raw="yes"]]