5 ms·
> Still, I want to avoid hosting a service where I have to be on-call. For sure it sucks being on call but usually because you're dealing with someone else's c
by abraae 5y ago
> Still, I want to avoid hosting a service where I have to be on-call.
For sure it sucks being on call but usually because you're dealing with someone else's crap. But as the big Kahuna, aren't you in a position to make things reliable enough that on call is not a burden?
To me, needing someone on call is a good sign - means you've got a vital product.
- mtlynch 5y agoThanks for reading! >For sure it sucks being on call but usually because you're dealing with someone else's crap. But as the big Kahuna, aren't you in a position to make things reliable enough that on call is not a burden? Yeah, I just don't even want to think about it. I want to be able to disconnect on the weekends safe in knowing that there's nothing I'm missing that's causing a big outage for a bunch of my customers.
- sneak 5y agoYou're selling an enterprise product. The service component of it is going to be key to revenue growth. You should probably be working to get to the point where you can hire professional sysadmins to think about it so that you can disconnect on the weekends. Either that or get over the "I don't work weekends" thing and recognize that if bootstrapping an enterprise vendor were easy, then everyone would do it.
- geerlingguy 5y agoAs someone who has run two services for over a decade, even though it's only down to maybe 2-3 nights a year where there's an off-hours outage, it's annoying enough to make me question keeping the things running. It always seems to happen with the worst possible timing!