The Site is Down

I woke up early this morning, energized and ready to tackle the events of the coming day with zest, gusto, and a great sense of enthusiasm for life (and fit in more hyperbolic words and phrases here…).

Why? Because today I planned to start my vacation…

… I say “planned” because the very first thing that hit me was a ton of notifications from Twitter, Discord, YEN, Patreon… text messages… that one of our bigger sites was down:

why….?!

I couldn’t have planned a better start to my vacation than having to spend the morning deep in DevOps / Security to figure out what exactly the issue is… which, apparently, is a phishing / botnet attack as far as I’ve figured.

This happens every fucking time that it’s not even funny; and it’s not so bad when it’s an experimental project but when you have real users and customers, it’s a goddamn nightmare.

So, you have to not only fix the issue but also spend just as much time making sure you can communicate effectively to your users about the situation and that you’re working on it to resolve the issues, sending fresh, early-morning notifications like this:

Communication during a crisis is key.

But, seriously… I just wanted to start my vacation by really, truly vacating, but, when you run an early-stage company / startup… it’s really hard to do that when you’re responsible for a ton of operational elements to the business.

And these are the types of things that are very easy to communicate to others but impossible for folks who aren’t in this type of environment and context to really understand.

The emotional burden (and cost) is extremely high and your company is on your mind twenty-four hours a day, seven days a week, three-hundred and sixty-five days a year as something is always on the verge of collapsing.

That vacation is coming… it’s coming… I believe… it’s coming… … … if I can just get through this small hiccup… I’m sure that’ll be it… I’m sure…


I captured a few thoughts on my vlog:

%d bloggers like this: