We built a tool that sets up screen recording links that, once the screen recording is complete, transcribes, AI processes and writes a page into our wiki with the video embedded into it.
The tool is pre-configured with standard meeting or documentation configurations so that the tool knows how to process each meeting or screen recording and transcript.
For instance, we'll have a documentation type called 'Infra/Terraform Notes' which once the screen recording is stopped generates a video, transcription, AI summary, keywords and writes it into the correct part of the wiki.
Further, we've introduced workflows so that you can chain multiple instances of this so that the AI can get smarter. For example; we've got a workflow for Requirements Docs where;
* we record the discussion with the client where they explain what they want
* that is transcribed and the tool knows to generate a Requirements Doc
* the developer adds a recording where he/she records screen recording explaining their approach to the problem
* that generates the developer design doc (using all the transcripts/ai output so far)
* the developer finishes the feature and records a screen recording explaining the outcome
* that generates a test plan for the QA person (using all the transcripts/ai output so far)
* QA person records a video showing all the testing that was done
* that generates release notes (using all the transcripts/ai output so far)
All this is compiled into automatically into a 'chapter' in our Features book in our wiki. The video and transcripts are added as attachments to the chapters.
It's nice to be able to go back through the whole history of a feature.
I stopped drinking 20 months ago. Australia has a big drinking culture so not drinking is confusing to friends and family. I've found that it's had a huge positive impact on my life - much improved mental function, motivation and stress/emotion management. I'll likely never drink again.
We built a tool that sets up screen recording links that, once the screen recording is complete, transcribes, AI processes and writes a page into our wiki with the video embedded into it.
The tool is pre-configured with standard meeting or documentation configurations so that the tool knows how to process each meeting or screen recording and transcript.
For instance, we'll have a documentation type called 'Infra/Terraform Notes' which once the screen recording is stopped generates a video, transcription, AI summary, keywords and writes it into the correct part of the wiki.
Further, we've introduced workflows so that you can chain multiple instances of this so that the AI can get smarter. For example; we've got a workflow for Requirements Docs where;
* we record the discussion with the client where they explain what they want
* that is transcribed and the tool knows to generate a Requirements Doc
* the developer adds a recording where he/she records screen recording explaining their approach to the problem
* that generates the developer design doc (using all the transcripts/ai output so far)
* the developer finishes the feature and records a screen recording explaining the outcome
* that generates a test plan for the QA person (using all the transcripts/ai output so far)
* QA person records a video showing all the testing that was done
* that generates release notes (using all the transcripts/ai output so far)
All this is compiled into automatically into a 'chapter' in our Features book in our wiki. The video and transcripts are added as attachments to the chapters.
It's nice to be able to go back through the whole history of a feature.