dybr
Feb. 10th, 2025 06:42 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
juan_gandhi Today is a silent day, "standup is by slack".
Added the table schema for the keys in the doc I wrote. Sent it again to Karen and to Kerry, let them review. Kerry seems to be pretty satisfied. Will have to schedule a team presentation for the next week, I guess.
Since all my cases except one are closed, started investigating the last one. It's about updating elastic search index by the data we get from "editors". Ok then, looked around in the codebase. Cloned a huge huge project, with Java beans inside. Horrible. 2014 is not that far away, but the technology looks like it was 2004. Horrible. Thank God it turned out it only mentions elastic search, but does not do anything there. So asked the people around, where do we update it? They pointed me to a rather new project (2022), which looks ok. Wrong design though; but I'll fix it, no problem. Not much to fix, and it's independent from everything else. Will just write another design doc, big deal. But first have to study the code, to make sure I know exactly how it works.
Then Jacob wrote about SNYK, do we use it? Jorge writes - "will it really find anything bad"? I wrote - "hardly, our code is professional Scala". Anyway, installed the plugin. But shit, the tool is undocumented. Of course we can document it, but what are we paying for? Posted the question, and decided, ok, let's discuss it next week maybe. Jacob has a similar opinion.
In spite of the fact that we are in hiring freeze, Samantha asked me to share the list of technical questions. It's in github, so I sent her the link, asking if she's able to access it. I guess she's afraid she can lose her job. She's really nice, good to work with. Ok, New York, New York. Cutthroat assholes left in the Bay Area.
Added the table schema for the keys in the doc I wrote. Sent it again to Karen and to Kerry, let them review. Kerry seems to be pretty satisfied. Will have to schedule a team presentation for the next week, I guess.
Since all my cases except one are closed, started investigating the last one. It's about updating elastic search index by the data we get from "editors". Ok then, looked around in the codebase. Cloned a huge huge project, with Java beans inside. Horrible. 2014 is not that far away, but the technology looks like it was 2004. Horrible. Thank God it turned out it only mentions elastic search, but does not do anything there. So asked the people around, where do we update it? They pointed me to a rather new project (2022), which looks ok. Wrong design though; but I'll fix it, no problem. Not much to fix, and it's independent from everything else. Will just write another design doc, big deal. But first have to study the code, to make sure I know exactly how it works.
Then Jacob wrote about SNYK, do we use it? Jorge writes - "will it really find anything bad"? I wrote - "hardly, our code is professional Scala". Anyway, installed the plugin. But shit, the tool is undocumented. Of course we can document it, but what are we paying for? Posted the question, and decided, ok, let's discuss it next week maybe. Jacob has a similar opinion.
In spite of the fact that we are in hiring freeze, Samantha asked me to share the list of technical questions. It's in github, so I sent her the link, asking if she's able to access it. I guess she's afraid she can lose her job. She's really nice, good to work with. Ok, New York, New York. Cutthroat assholes left in the Bay Area.
