A recent post on vowe.net pointing to Lotus Notes and the dangers of starting from scratch sent me down the memory lane into the 1990ties.

Collaboration training

Companies would send regular employees in groups of 10 -20 to a full day training to learn about that new thing "collaboration" (which gave the word collaborator a less perilous meaning). This is how it would go down in four modules:

In the first module the Notes discussion database gets introduced. Participants would learn about topics, responses and response-to-responses. Without seeding lively discussions would emerge.

The second module would focus on eMail, inbox, signature, encryption, richtext and - everybody's favorite - permanent pen.

Followed by the lunch break

The trainer would have prepared individual emails to all participants. Most of them with harmless request like "What's your favorite color" or "Ask your colleague about the last holiday". Two emails however had loaded requests: "Stand up and put your one hand on your head" and "stand up and sing or hum the national anthem (considered unproblematic in Switzerland)"

Unsurprisingly hardly any of the recipients of such a message complied. The trainer would then ask a random participant to join in front to face the class, followed by the explanation: "You can't expect email to transport requests that a better issued in person (paraphrasing here)".

Time for a coffee break with gipfeli.

The trainer then introduced module four "Imagine you are all distributed in regional offices, so you can't show paper documents to each other, solve the problem I'll hand out". I then would hand out sheets of paper with the sentence "Every capital letter is part of the solution". The sheets were all different with different letters capitalized, so the task was to collect the capital letters and form the solution LOTUS NOTES. This wasn't explained to the participants though.

Typically a barrage of emails would follow with different levels of speculation, curiosity, acceptance or ridicule. After 20-30 minutes the task would have been figured out at the "cost" of 100+ emails. The winning team (we informally tracked completion time) however took less that three minutes: One participant created a discussion entry "Please share all capital letters on your sheets" and sent a doc link (hyper link in today's lingo) to the rest. 10 response documents later they were done.

Participant reported a better understanding of "Zusammenarbeit (collaboration)" and "Benachrichtigung (notification)" which made them appreciate the shiny new tool.

I loved this sessions since the showed not only how to use the tools, but why and when and when not.

I'm a big fan of Apache CouchDB, so I was very pleased when I got the permission to opensource (is that even a verb) a R&D project we were working on for a while, meet CouchCompanion

Fauxton as role model

We were asking us, how would CouchDB's admin ui Fauxton look like when you rebuild today, what would be the tech stack and new or enhanced features. This is what we can up with:

• build with webcomponents, namely Webawesome and Lit, no big framework like react or angular
• Native fetch()
• All JSON and JS Code editable with the Monaco editor (the one used in VSCode)
• Support to build Mango queries and indici
• Sync with version control (Github for the moment, fighting with CORS and CSP)
• dark/lght mode
• UI to configure OIDC IdP

... and more. There is a capability walkthrough available. But to really get a feel, just run the container:

docker run -d --name couch-companion -p 5984:5984 \
  -e COUCHDB_USER=admin -e COUCHDB_PASSWORD=<choose one> \
  -v couchdb_data:/opt/couchdb/data \
  ghcr.io/hcl-tech-software/couch-companion:latest

The container is based on the official CouchDB image with Fauxton swapped out for CouchCompanion. Give it a spin!