dybr

Now, what's up?

I have two cases.

One is: "introduce an env var for a url for public key, with a default value".
Colleagues are reviewing it.

Esteban says: we have to check it on staging, because what if something happens when the env var is not defined. (Sure!)

Bill says: oh, no, we cannot provide a default value for an env var, it's a bad idea. The env var should be always defined, or else we should crash.

I answered to both, and invited Devon, who had created this jira case about half a year ago.

Mike asked me why am I doing this case, and I told him that it was his suggestion that I pick up some cases when I have time. I did not tell him I have plenty of time, it's too personal.

The second case is: "use standard-errors module' to enable localization of error message and to standardize them.

Ok, so I pushed that stuff, and then started asking around: how exactly will my updates get into generated scala code? No answers, but at the standup Mike told me: it's automatic. Oh, ok, automatic, coo. And it was automated. I pulled that automatically generated code, run a build locally, everything's fine. Started looking the build results (the jars) in artifactory. None. Started checking Jenkins' build logs. Last build was done 9 months ago. So, hey, what's up? Asked the team. Mike answers: "we had a build failure" (I did not see it in github, though), "and we are investigating".

Good! I have nothing to do. As Mike suggested during the standup: "Vlad will close the meeting tab and will go have a glass of French wine" (Actually not, with my health status I only have a glass or two of wine per week. I'm being careful. More, I'm not even enjoying my favorite local Les Queyrats.) (P.S., 2025 - I hope I will now.)

So, it's almost 8pm (that's 20h), and I'm just hanging out, nothing to do.