Skip to main content

So I tried live streaming last night...

What fun!

The interesting twist is that I wasn't gaming! I did it for software development!

It's probably not a new concept, but I came about the idea of streaming my coding sessions while talking with my wife about my presentations and community involvement. A really good friend of mine streams his League of Legends sessions and seems to have a lot of fun doing it.  The sensation I got was similar to back in my early internet-faring days as I became aware of the breadth of people online.

My project of choice for this is kind of nice because it plays back into the streaming audience interest. Obviously to stream, you have to run some kind of source on your machine and the biggest game in town is something called OBS Studio. One neat feature of OBS Studio is that it allows you to configure a web-browser based overlay for your stream that simply inlines a web page into your stream.
This has caused a proliferation of web-based stream widget providers all vying for streamers to use them simply by copying and pasting a secret URI that renders a widget to their screen.

The Appeal

I think there are many different dynamics to the draw of watching someone code online.  I also suspect most people take a combination of the benefits and never just one. Either for practical reasons to see someone coding to share in comprehension, for the social elements and oddly - for the sound.

Really in the end it's all about community and live streaming is one I totally underestimated.

Things to Improve

So yeah, I think I'm going to be doing this more often - time permitting.  If it takes off in any magnitude, I'll probably have to cave and at least start streaming my voice.
Another issue is that internet connections where I live are horribly overpriced with upstream rates being a cruel fraction of downstream. So I'm going to have to figure something out on that front as the stream quality for coding has to be good enough for text to be legible.
The last thing would be that I have to make sure I only go as far as I've been able to plan out in my head. Otherwise things slow down a fair bit as I start humming and hawing over architecture. Usually thoughts I have while not at a computer.

Anyway, if after reading this, you're interested in watching me do some live coding, feel free to tune in!

Popular posts from this blog

Amazon in Winnipeg?

Late last week, Amazon put word out that they're starting to look for a city to locate a second headquarters.  The fuel this announcement provides has the hype train in Winnipeg going so fast, it's missing stops.

I'm curious though.  As you've been digesting this exciting news, who have you spoken or listened to?
Was it this guy and his party's historic theft of public infrastructure (pdf) and incompetence with digital strategy? Or how about this guy, who maintains that Winnipeg doesn't need a proper rapid transit option?  You know, the kind that might actually catch the eye of handsome Amazon who now has Winnipeg trying to be the belle of the ball.

Runner up articles are Winnipeg's inability to join the 21st centry on active transport and the compounding of the aforementioned digital strategy mistakes.
Stop Listening to These Guys They are not technology experts. At worst, they're unabashed self promoters. At best they're conduits for very bad pol…

Making TypeScript npm Packages

If you've landed here, I can only assume you're like me and see packages as the highest form of sophistication in software development.  In that same vein, I bet at some point in the past you've wished you could start applying DRY principles to your client-side efforts.  I know for myself, I don't enjoy writing the same application bootstrap code constantly and so recently, I was motivated to codify it.

This body of understanding has taken me quite some while to figure out, hopefully what I share here is helpful enough to get you up to speed.  No post is complete without some kind of example, so throughout I'm going to reference a package I've just finished putting together called protoculture.

Briefly described, protoculture encapsulates all the common bootstrap and conventions I've been using while developing TypeScript apps that use React and Redux.  Honestly, I've already gotten a lot of benefit out of putting this package together, but nothing about…

Building .NET Core Nuget Packages

My last blog post was on building and publishing npm packages, specifically for typescript projects. In my opinion, packages are an important fundamental unit in software development. They sit at the confluence of technical competence and collaboration, and represent something the software community should be proud of.
Most of the time, you're going to be creating software packages once you're comfortable with some essential pillars: CodingProject structureSoftware architectureBuildingDeliveryCommunityLicensing
After I got my npm package up and running, my next task was to do the same thing with my C# libraries. Similar to protoculture, I have made a library called praxis.  This is done by leveraging the services and tooling known in the .NET ecosystem as nuget.

In this case, praxis abstracts many of the concepts and functionality I require when producing server projects. It builds on top of ASP.NET Core, so in that sense you can almost think of it as a framework-framework. The…