dybr

 So my fix for the weird import job was eventually approved, and I merged it. But then I had to deploy it (and run), which is done by updating a groovy file, generating configs for Jenkins, and, well, merging it all. So spent some time (actually working on build.sh which would kind of automate this shit.

Also we had a sprint closing meeting, and when asked about whether import will be deployed today, I was saying "I don't know, it depends on the speed of reviews", and when asked whether I'm going to add endpoints for updating markets I said "I don't know, it depends on what we agree upon with Mike, maybe there's nothing to do at all". So we agreed to postpone it to the next coming sprint - and everyone was doing the same.

Karen was sick, so we did not have a 1-1, where I wanted to discuss with her, maybe we should not have a cache, if the data are requested once a day (which I don't 100% believe). But she's sick.

What else. Oh, id length. Amazon, during the long weekend, increased the default length of user id for Alexa. We store it (wrapped in some stupid stuff) in Postgres, and the column width is not enough to fit it all.

Ok, you can tell me what we should do. I know what we should do. I also know what we should not do: trim the id. Had it in Orkut, when users started mixing their accounts with other users, because "encrypted" ids started overlapping.

Here my question about whether it's 1 to 1, a mono, etc, was not answered, because, well... you know programmers. They never learned the basics.

As a result, the sprint postmortem was replaced with a rush "war room", when they tried to find a solution that they would understand. So I had one more hour free for work.

Also, I was exhausted fighting with our jfrog, and asked on slack whether anybody knows who is jfrog's admin, and I hope it's not me. Guess what. Jacob was, and he now delegated it to me. I was volunteered.

That's it for today.