I'm a Support Engineer at GitLab, and based on my own experience that statement is definitely correct. There's entire classes of problems you simply don't have to deal with at all for SaaS customers.
I get into this argument inside my company, but as alternative point of view is that "hardening" the software for those 'I have seen some shit!' circumstances can be actually good for the overall health of the codebase and user experience. "It works on my machine" is all well and good until something goes off the rails (heh, so to speak), and if the software always assumes the happy path, debugging that is painful for an internal audience just as it is for external ones
Come to think of it, I would have though GitLab's fully-distributed workforce would make this true for you, too, since "I dunno what this error means, lemme just walk over to Jane's desk and ask" becomes expensive in that setup
Come to think of it, I would have though GitLab's fully-distributed workforce would make this true for you, too, since "I dunno what this error means, lemme just walk over to Jane's desk and ask" becomes expensive in that setup