>On the writing side, the main issue is that literate programming tends to tie your writing into the tools that support your literate programming. This can make collaboration on a document difficult if the people you’re collaborating with are not as sold on the tools as you are. The moment you need to work with a business person who prefers to use Google Docs to share a document, or a university department that insists on receiving drafts as Microsoft Word documents, you start to face the pain of exporting to those proprietary formats. Like many issues in software development, this is really a social issue: for literate programming to work, all of the writers need to agree on the tools being used.

I've used org-mode at work and this was actually the strongest selling point. Using pandoc and massaging the org-mode reader to map better onto the pandoc markdown ast I could export to pdf, html and docx (!!!). I had production code + prose sent to the CTO as a word attachment in an email and she loved it.

The tangle comments also meant I have a workflow to share the code as regular code with the rest of the team and use git to see which code sections they changed. There wasn't enough traffic to justify writing an un-tangler that put their code back into the original document but it seems like a very interesting problem.