so

if github had an outage

and was offline for 48 hours

what would catch fire?

@Viss

nothing i care about? :)

@paul_ipv6 sure but does like, any automated shit in your house care? what about your phone carrier? what about your isp? your power company?

@Viss

home, none. phone carrier, not much if my basic internet is working. ISP? possible though so far they seem to be doing their revision control mostly in house still. my power company only recently started offering electronic statements, so i'm probably safe there for the moment. ;)

work/customer related shit? probably a much uglier picture.

@Viss

i've had similar discussions more times than i'd care to about server OS maintenance. the number of under 40 yr olds who don't understand why trying to repro a system related issue when you just spin new virtual servers from the screaming newest externally maintained updated multiple times daily repos might not be a good way to see if it's your code or the OS that is screwing things up.

i have sometimes won the argument of at least doing everything from local repos and not updating the repo without regression testing but not nearly as often as i'd like or turned out to be the correct answer.

automation that depends on someone else's stuff working, not being unreachable, and not being impossible to revert to earlier versions is bound to be a problem at some point.

@Viss

hell, the idea of regression testing at all and not just wiping and leaping forward on new versions seems to be a dying concept.