@hazardwarning Yep. ?
@matigo Very likely.
We are already on the GSuite boat so it would make sense to use it for the internal chat. Also, there seem to be some strong proponents for it in the company. It is very likely we will switch to it at some point.
We are testing Hangouts Chat at work as a potential replacement to our current company internal chat solution. Let me just say politely that I am not a fan.
@joanna That’s the view from our living room. The white flat area behind the yellow grass is sea (frozen, obviously). Not bad, I would say. ?
@joanna Indeed. Last night he didn’t wake up due to pain at any point, which meant that we didn’t give him pain killers. When he woke up he was in pain, though.
/@matigo
@joanna 2–4 weeks. He must wear a support thingy for 1–2 weeks, after which he can ditch it if he has no pain anymore.
/@matigo
@matigo Technically I could do the thing, but 1) I may not have access to the relevant parts of the backend system and 2) we have a dedicated person who is responsible for those parts (even though the PO aka The Douche likes to push the responsibility to me).
@matigo Now that the person who handles the app testing knows that, he most likely can tell the testers what is going on. But the root cause of the problem needs to be solved nevertheless, but that's a thing that needs knowledge of the backend services and the internals of the backend aggregation server the app is using. I have not done any of those.
There's a problem in the backend services and the app gets all the blame. Yay. Not.
Luckily I can refer to the fact that the app displays exactly the data it gets from the backend, which means that if there's a problem, it is most likely always with the backend.