E.g. Why it is ported to various platforms and always used as a test game to run in the next (fascinating) engine?
Things like preparing a topic, recording, audio editing, writing shownotes/links/chapters, marketing (social media posts), and maybe editing reels/shorts. This can quickly consume ~8h per week.
We looked into the usage of AI with the goal of reducing the time spent.
Right now we are using https://www.assemblyai.com/ to generate transcripts. This helps us a lot because we often ask ourselves, "Didn't we talk about X in some episodes already?" - DUe to transcripts, we can easily search it.
We are experimenting with https://podsqueeze.com/ to auto-generate chapters, show notes, auto-extract links etc. - In the end, this seems to be a service that generates transcripts and sends them to ChatGPT with a few custom prompts - We don't use the full service, but might end up with our own workflow doing the same. Still a good inspiration for now.
When recording is going wrong and we only end up with one audio track (vs. 1 audio track per speaker), we use https://auphonic.com/ to normalize the audio loudness, etc. This service is doing a pretty good job.
Right now, we are playing around with the automatic removal of filler words (like "ehms") in the audio file with the help of a transcript. The challenge here is that we record in German. Many AI's don't support the German language as well as the English one. Time will tell.
However, we can say the transcripts had the biggest improvement in our workflow - The speed up writing the show notes a lot!
How do you use AI to speed up / get support for your podcasting workflow?
Every now and then, I read answers from Ex-Google Engineers on questions like "How is it like to be out of Google? What do you miss in the industry?". Often they say "the quality of source code".
I am curious: What is that special to the source code inside Google? What makes them "high quality"? Is it a well-commented code base? That people with less context get a grasp of what the piece of code is doing? Is it a strict following of company-wide coding guidelines? Is it the tooling around that supports the maintenance of the quality?
I am curious to hear answers from people who have experienced the code inside Google. And maybe have concrete examples?
Thanks all.
What I am thinking about is for a home automation use-case. You have a Raspberry Pi or any server running. Your home automation is functioning without the internet. However, you might have VPN installed to be able to connect from elsewhere to check what's going. I want to be informed by a service when my home is offline. The idea would be to install a cronjob that calls every 5 min. an API. The API checks that every 5 min. There is a call. When there are two calls missed, it pushes you a message.
Implementation wise this is quite simple and straight forward. But I believe sometimes you need to focus on your domain and don't need to reinvent the wheel. Any hints here?
I don't feel that I have a Return on Investment of running those. I am not talking about money. We run it 100% non-profit. I have a huge network based on the meetup, but I don't use it. I am not looking for a new job or anything related. The challenge is missing. The excitement is gone.
Therefore i am asking myself, whats next? What can we do with this crowd (without losing the trust)? We are organizing a small community conference [2], and it was sold out in 10 days. Handing this meetup to someone is tricky. I didn't find someone who cares so much about this, and I don't want to see this thing to die.
Any idea what's next? Any tips from your side? Any thoughts or feedback? Feel free to ask questions for more context.
[1] https://www.meetup.com/Web-Engineering-Duesseldorf/ [2] https://localhost.engineering/