As software engineers, we have two nemesis, the first are bugs (more like errors or things that prevent our code from working as it should), the second are software testers. Software testers are like quality assurance officers, they're there to ensure that the products we build are up to standard and do what they're supposed to do. Software engineers are constantly in a love/hate relationships with software testers as they can deem your product unfit and send you back to the drawing board.
When you use apps in funny ways or intentionally do things that you know the computer doesn't expect from you (in a bid to see the reaction of the application) the reason why the application doesn't break is because the software testers have tested the product for edge cases, that's like contingency based testing such that they think of the funniest, weirdest and scariest things clients can do with tech solutions then they do it so software engineers can build failsafe features to handle those scenarios.
As software engineers having software testers on your team can be beneficial as they help review your code, when feedback is implemented you end up writing better, more reliable code which increases your skill and value as a software engineer in the long run. Organizations that have software testers also produce better softwares and have the assurance that products are properly vetted before being released. There's a conflict of interest that occurs when you make software engineers vet their own code, the separation of responsibility that happens when software testers are responsible for vetting tech solutions increases efficiency overall.
If your tech product or app is constantly crashing or giving errors don't blame the software engineers (please you'll break our hearts), blame the software testers because they gave a seal of approval (and because we hate them too) 😉.