9

4 f*ing years since the app is published and f*ing QA team still can't read f*ing logs and find out why the f*ing backend messed up and f*ing blaming it on the frontend in a f*ing scenario that has nothing to do with the f*ing REST API. F**********CK!

Comments
  • 12
    Dude please this is not the Disney channel. For fucks sake write fuck if you mean fuck.
  • 4
    @horus K. Will do next time Mr Disney Channel
  • 2
    @mexandroide it's probably the frontend.

    Backend devs rarely make mistakes.

    They're just happy little accidents.
  • 1
    QE couldn't debug because your log files have ****s all over
  • 1
    @sariel the problem was actually the backend but who cares. QA people unable to fucking read an HTTP payload and response and blaming it on something that doesn't use the network is beyond all frustration.
  • 2
    Show "server error" notification, when you get 500 or smth :) Well I guess you can even show it, when you get 200 xD
  • 1
    sounds like your QA team isnt comprised of engineers, but rather 🤡🤡🤡s
Add Comment