OBS for remote meets

We’ve recently had to pivot to fully remote church service at my church, for reasons that are hopefully quite apparent.

We had a few constraints

  • Accessible by the technically illiterate - need to see the stream in a single click
  • We wanted several people presenting - to keep a discussion and community feel
  • As little contact as possible - ideally none. All the presenters meeting in 1 place means that one infection can take down the lot, not to mention the public health concerns of doing such.
  • Usable by technically illiterate - the presenters are not necessarily literate either

Is this your situation? The good news is, we did this in a relatively straight forward way - using OBS Studio, Zoom and YouTube Live.

Read on to see how

How does the Hololens 2 matter?

So that happened, the Hololens 2 has been released. A few people have asked me what I think, so it’s about time I got my thoughts down on paper the interwebs. I’ve had a day or 2 to mull over it now - so here it is for you.

The main features touted are improved FOV, fully articulated hand tracking and increased engagement and collaboration - partnerships and technology enablements.

But how will this play out? How much is smoke and mirrors? What are the effects here? Read on for my thoughts.

Seedy Fake Data

With fake user authenication done, we had everything we needed to generate fake data.

The seed data was generated on every deployment to our dev and demo environments - which gave us nice, clean, predictable demos, and our dev server was never a terrible mess of temporary data (yeah, you know what I’m talking about).

Seedy Fake Users

Ever been on a project where a dev comes on board, and has to clone databases in order to get test data? What about when you just want to nuke all your test data and start afresh - is starting afresh pretty painful?

We went whole-hog on seed data and test user generation recently, found it to be incredibly useful, and will be doing it on future projects.

This post covers the fake user creation aspect.

Put your operations on your client

In the last post, I showed how we put our server DTOs into our client code, to ensure changes in our data structures didn’t silently fail. In this post, I’ll show you how we protected ourselves against changing API endpoints.