So, what's going on. A "long weekend" is coming, so not so many people are online. People are busy taking a break.
I spammed with "reminders" all those reviewers of my four pull requests that have been hanging around for almost a week. One of the PR is "introduce a constant", with a comment that points to my discussion with Nick. Nick approved it, but Sam (Samanta, a nice-looking bitch) says that she does not know the context. The other PR, somebody else also wrote that they don't know the context. Does it mean that my PR description is not good enough? They don't say it. I can write bigger descriptions. I think I'll be asking them to ask questions as comments to the PR. I'll be happy to answer. But this time I just reassigned one to Esteban, and another forgot to whom.
Then I figured how to deal with this weird logging "bug". I just wrote another app, placed it into tests folder, and this app checks that the log (intercepting it via `System.out = myPrintStreamBackedByString`. It's not a test, but frankly, I don't think I know how to write tests for that typelevel shit.
"Style checker" in Jenkins did not accept my code. It did not accept import statements and package statement. Oh, and you can't have println in the code, it's not allowed. But `print` is ok. So I wrote `print("Log verified and it's ok.\n")`. Imports, I had shuffled them around (it's Scala), and package, I just removed it, who cares. We will need to repair this "style checker", but it's Sam, and Sam is a bitch. Problems with common sense and logic. Reminds me Sonia Rikhtverchik, if you know that bitch, the bitchest one I ever encountered.
But later, at Scrum meeting, Bill told me that actually the problem was not with logging per se, but specifically with errors happening somewhere deep in typelevel, and reported improperly. So it's not about logging per se. Will investigate.
Also, in the huge pile of bugs assigned to me one is about a user who changed her mail, but continued getting mails to the old address, and these mails are sent from our team's code. Will have to investigate, of course. First, will have to figure out how I can reach that information in a bunch of services. All I know is the user id and org id. Anyway, I'm definitely not in the context, and switching them fast is too much, especially for Friday afternoon. So I had closed my work computer, until the scrum meeting.
There were four of us in the meeting. Esteban told me what is it about the dashboard for datadog that I'm actually also supposed to work on. I'm still curious... and I like datadog anyway. The most reasonable logging platform, in my view.
And Bill told me about that other logging trouble (which was not reported properly).
Oh, and I have another jira case, that only has a title, nothing else. The title is the name of an endpoint. Okay, do I mind? I'm just a contractor, I don't have a skin in all that. My only duty is to make sure I never overwork. Especially since I hear every day how good it is what I do. Which is strange. They are paying me more than probably 99% of their permanent employees.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ypq , запоминать сны. Так чтоб не забыть.
