This is the last article on the “Recording and Streaming your event”.
In this post, I conclude the series with a rant and two suggested setups.
This is the sixth article on the “Recording and Streaming your event”.
In this post, I cover some other areas I couldn’t quite put elsewhere.
This is the fifth article on the “Recording and Streaming your event”.
In this post, I cover details of the recording and streaming software.
This is the fourth article on the “Recording and Streaming your event”.
In this post, I cover details of filming the Talent.
This is the third article on the “Recording and Streaming your event”.
In this post, I cover details of the screen capture.
This is the second article on the “Recording and Streaming your event”.
In this post, I cover details of the Audio recording.
As you may know if you’re following me on twitter, I’ve tried to help when possible with the recording or streaming of PowerShell & DevOps events. From a couple of hours recording for a user group, to several days of PowerShell conference recording and streaming, I’ve went through a fair share of experiments (a.k.a. failures). I am by no mean an expert in the subject, and not a professional in this field either. I’m an amateur, who’s spent a bit of money and time trying to help, mainly because I’ve been on the event organiser side, and I know the effort required to deliver recordings, in terms of budget, time and effort.
If you’re attending events, or not, and wondering why it is so hard or expensive to get decent recordings published, I hope this detailed explanation will help you understand why. The investment needed, even for amateur recordings or streaming, is substantial and it may feel unfair for attendees to bear the cost and share the benefits. This, however would be worth another post, so it’s out of scope.
If you just want to know what I recommend, jump to the conclusion. Otherwise, I’ll take a tour of my experience and what I learnt.
From my experience in IT, mainly in what we call IT operations or more specifically platform Engineering, there’s an emphasis on some noble design principles such as reliability, resiliency, high availability, monitoring, MTTR, MTBF and so on, but something is missing.
None of them should be ignored, obviously, but the capacity for change is often overlooked. I’m convinced it should be a core design principle, re-evaluated for each change, especially for automation architecture.
As I was (and still am) working on a post to explain What’s happening to DSC, I found it was necessary to explain the context around it, or at least my interpretation of it.
This is from a traditional IT Infrastructure point of view, so only looking at what would a traditional IT Pro see within Microsoft’s offerings, communication and especially in the PowerShell ecosystem.
It’s meant to help understanding the changes in products (especially DSC), and the impact it may have on your day to day job, by looking back at what happened in recent years.
Ah! I always struggle to explain these concepts and the superiority of Policy-Driven, but I think I’ve found a good example! My Air Conditioning systems…
@gaelcolas 