dybr

 On one hand, we had too many meetings; on the other hand, it was not too exhausting.

One meeting was about the jira tasks, which we have a lot, and I'm getting a feeling now that they are not for completion, but for occupying the workforce. I don't mind. I agreed to take care of a case that looks interesting to me, and probably boring to others: organize handling errors in the servers.

Oh, also, pinged Mike regarding approval of my production deployment. He wrote that he already did - but somehow it was not visible on my side. Ok, will deploy tomorrow.

Esteban sent yesterday a huge pull request; I wrote a couple of suggestions; today he implemented that stuff (adding tests), but he did not get the suggestion of handling Options the same way he handles IO: loop style. So, yes, he does not get it. FIIC, right?

Then there was a meeting regarding "what went well, what went bad during the sprint" - "post mortem". I did not have access to that doc, so this fact was added to the list of bad things. Otherwise it's fine.

Then a guy from support or qa, no clue, pinged me on Slack, and we huddled, he showed me how he reproduces the bug I was supposed to work on. Ok, really easy. I took several snapshots. Will work on it tomorrow.

Today I was working on parsing those routes in Scala, and generating proper shell scripts. Well, it works, but I have to make sure I provide the right environment, on demand. Environment values for "workflow scripts". A bit challenging, because how do you know, right? A variable can have whatever name a developer uses; I need to guess which env var matches it. My code should be AI-ish.

So, lots of fun.