I usually record using Skype, turning off the video to optimize the bandwidth. Manual time: 15min spread over days and emails Recording with Skype To say the lease, there is potential to reduce headaches here. Right now, it is overkill, but I will soon add „daylight-recording-slots“, so such a tool will come in handy again. These tools sync with your calendars, display the free slots you have and let the guests book YOU as they see fit. I used « book yourself » tools ( Timebridge and Vyte) for a while. But those amount to 8 hours per week only. It is easier since the time slots are clear „next Monday, Tuesday or Thursday from 21:00 GMT+2“. This makes the scheduling both easier and harder at the same time. So I have to record at night, when the kids are asleep (>21:00). My current day-job makes it hard to record during the day. Manual time: 10min (manual steps + writing down questions) Scheduling It helps them prepare beforehand and know what is coming.
Finally, it also has a psychological-safety effect on more introverted guests. Then, it might be useful (to me) if we fall short of topics or if I need to redirect the discussion during the recording. Then it will set the tone of what kind of stories I am looking for and thus orient the flow of the discussion. How better than by highlighting all the good things they can add to the discussion? First I want the guest to feel welcome. I like to add personal questions for 4 reasons: And finally how the guest can prepare for the interview. It also explains the technical details of the recording. It will help the guest understand what I am after and what they can contribute. This invitation email explains why the DevJourney project. Once I have an email address and an informal GO, I can send a formal invitation. Or with guests and contacts introducing me to potential guests. It starts with simple networking during conferences. The „guests“ acquisition process starts way ahead of the recording. There’s still a lot of possible improvements, but here‘s how it looks behind the curtains. To do so, I had to streamline my recording and publishing process a little. At the time of this writing, I published 3 episodes. I then decided to set the pace on a sustainable two-weeks basis and hold it. One month ago, I rebooted the Developer's Journey podcast after a year long hiatus.
0 kommentar(er)
