Sysop

time.

And so we had another character called Sysop who was just like a computer that we would cut to when we needed a break.

Yeah.

like

And yeah, he's very quickly pummeled by narration in his head.

The SysOp quickly catches up to him and he's legitimately like, this is terrible.

This is awful.

How do I make it stop?

And he gets told that most of the theaters that you can enter do have their own interface, their own options.

And so he just needs to open up his thing and he can adjust the volume and he quickly turns down the narrator so he can have a conversation with the SysOp.

He can't hear himself think.

Yeah.

yes

and He's quickly approached by like the SysOp, like the moderator for this area.

Yeah.

I went back and checked as I was writing my notes.

The SysOp never gives a name.

Nope.

So I'm wondering if maybe the SysOp also isn't a person.

Is also like a virtual intelligence.

And those kinds of things, you don't have to worry about the people as much.

I mean, you still have to worry about the developers and the SysOps team and making sure that it works.

But when you go and fix something or make something stronger or like some of the stuff that we've done, found out where we're spending money that we don't need to on different services.

Those kinds of things are just educating the sysops and dev teams.

I have little tools all over the place that I wouldn't have otherwise.

Like, that was... that's one of the kind of key things about DevOps and Sysops is if you do something more than a few times, you're supposed to write a script to au- [laughs] to automate it, right? But that's time-consuming.

It's a lot of work.

Now it's easy.

He took IT classes.

He became our head of SysOps.

And Aaron was the guy who, at 4 a.m., if something went down, he'd get a pager message, would wake up and go fix it.

And We were running a business that was like advertising infrastructure for a million different websites out there.