That point in being a professional software engineer where I have to start asking friends who are professional sysadmins how the fuck they make my own software work because I don’t understand how it doesn’t create an obnoxious disaster in every business environment ever and I need to learn how people mitigate the problems my widely-used software creates
@Kistaro Yes please ohgod as an Ops person please..
I presently want to murder some of our engineers over one of our products if service is consuming 2TB of ram and unstable throwing more ram at it will not fix it.. and no I'm not monitoring your special dashboards every hour when the tool offers notifications and pagerduty integration. My team will take on this when you get proper monitor solutions.. and some semblance of run books for it. this is no the only product we are responsible for.
@wobblewuffess yeah, over here the ops team would block the launch or refuse to provide services and require the SWE team to stew in their own mess if it came to that.
I’m currently writing an updater for desktop software, though, and whatever our own software deployment team does is going to be pretty local and special-case, so I have to look outside my own company for war stories related to my own product!
@Kistaro It sucks but some teams will just push stuff out regardless, especially if there is a bunch of C-level visibility on a product.
I'm going through that right now with a core product of ours that is huge and constantly growing and doesn't scale well to be but Execs said it had to launch and now Ops gets to deal with teething problems and Eng doesn't understand throwing more hardware as a stop-gap isn't a solution since it will take millions of dollars and weeks to build/deploy.