There was a pretty major issue in the app. Turned out that the name of a required parameter was wrong on our end. Then again, the documentation of the feature had that wrong too. ?♂
@matigo Well, in this case we were writing to each other, but you get my point. Also, we were discussing in English that is not the first language to either of us. However, I think I was able to express myself clearly enough. But what do I know, maybe I was everything else but clear. ?♂
Today is one of those days when I wonder does the other person I am communicating with understand a single word I say to them even though we are supposedly speaking the same language. Sigh…
@matigo Yeah. That could explain it if it would happen every time on their devices. But it’s inconsistent on their tests too. ?
Yep. The library returns wrong value when opening the connection. The behavior is inconsistent, sometimes it returns the right value (always for me), sometimes it’s wrong (never for me). Not cool. Not cool at all.
// @matigo
@matigo Probably. But the actual root cause for the issue might be in the library that we use. For some reason its open method returns wrong value sometimes.
Grr… The other developers are still facing issues with the reworked architecture. I have had zero issues with it. That makes me wonder what the fuck they are doing there.
@streakmachine I must admit that I didn’t. There were Solaris machines at the university and at Ericsson, but I never had to do any work on those.
Let’s see if the major refactoring I started working on today will fix a major issue or not. At least I would hope it would fix it, as the changes are handled a lot better than in the old system.