1 files changed, 13 insertions, 2 deletions
diff --git a/2021/talks/tech.md b/2021/talks/tech.md
index d9a3e8a1..6a26281c 100644
--- a/2021/talks/tech.md
+++ b/2021/talks/tech.md
@@ -26,8 +26,19 @@ org-treeslide to write and present technical documentation with style.
 
 # Discussion
 
-IRC nick: jan-ypma
-
+BBB:
+- Have you encountered any push-back from people requesting the documentation who are of the opinion that only a Word document will do?
+  - Jan: Not really, I tend to deliver the PDFs only. If more is needed, I expect I'd make a docker container with emacs in it, so people can export the org-file to PDF themselves.
+  - The main problem I have is that effectively they end up branching it in order to use Word's change tracking, and there is no reverse path.
+  - Jan: That sounds more like a team thing. Most people I interact with are developers, and are OK reading/interpreting change tracking as a git diff, e.g. on github or azure devops.
+  - OK, thanks. I think that is the root of my problem I just thought I would ask in-case you had encountered the same.  Thank you for the talk.
+  - Jan: I think in your case I'd either introduce them to a nice web-based git interface (org-mode looks fine usually), so they see it can do similar things as word change tracking.
+  - Jan: Thanks for your feedback :) feel free to reach out if you want to chat more.
+  - Unfortunately in this case they refuse to use anything that isn't a WYSIWYG interface. So even a Markdown editor in a split screen with a preview window is not accepted.
+  - Thanks!
+  - Jan: Hold their hands, be kind, small baby steps :)
+
+IRC: (nick: jan-ypma)
 - I use restclient everyday, but never thought about using it from code blocks, duh! Very interesting talk!
 - This is a good demo, I've found org-babel to be a really amazing glue language for stuff that's sort of annoying to automate otherwise.
 - Thanks! :) So the fonts of the current talk are: Fixed pitch (serif): New Heterodox Mono, Variable pitch (serif): ETBembo