[bwaine]

At my fully remote startup we operate a variation of this that I think can feel less onerous than a culture of verbose written communication.

- We create living documents / whiteboards on Miro (formally Realtime Board) that relate to the features we're working on. Things like pictures, architecture diagrams, draft db schemas. All at WIP stage.

- When we need to create communications (like requests for comment, demos etc) we record a short video using Loom. The video usually centres round some area of the whiteboard or in the IDE.

- We post this both on a notion page and in slack (using a public channel as to article suggests), tagging those that need to know or would find interesting. Keeping a long list of previous videos in notion helps find useful data later.

I think the low barrier to entry for recording video over the top of documentation thats "just good enough" to get the idea across has lead to universal uptake across our team. It's also easy to slot in reviewing these videos and responding during natural breaks in flow.

For more critical areas of the code / operations we document more formally towards the end of a feature development cycle.

[tomatohs]

I'm building a product that combines screencasting with git, so you can talk about code as you work and discover it in your git history. I like how you describe it as "over the top," I think the biggest advantage is that video can be created while you code rather than writing which typically occurs after I'm done. The product is in beta and you can sign up here:

https://paircast.io

[beckingz]

That looks cool!

How does this compare to livecoding on a streaming platform?

[tomatohs]

It integrates with code. The transcript on the right side is a combination of git diffs and audio transcription which is generated from your cast. Each git diff automatically commits to your git repository so you can reference the video from your git history.