What's up today? Wednesday. The day of meetings, meetings. Pretty tired. Especially when Ashok
posted a complaint that his attempt to update station returned HTTP 503. It turned out later that he used HTTP GET to post the json, and that the json was not json, but a piece of javascript (keys without quotes). I only returned to this shit when the meetings ended. And me and Karen

spent some efforts trying to explain to him that the documentation says that he has to use PUT, not GET.
Anyway, and also, since we are on Newrelic, I went ahead to check if my logging fix is ok, and could not. So Karen sent me a neat sample url for Newrelic, and everything went smooth.
Also, since the "epic" was about MVP, I kicked out two paranoid cases from that epic, it's definitely not MVP, it's 100% quality proof, which I love, but it's not MVP ("minimum viable product"). The MVP has been around for almost a month now, and even Ashok tried it (not very successfully, so far).
Oh, what else: I've cleaned up as much as I can, and now I'm ready to do the scala version transition in the projects. Really, the geniuses from the past made it hard. 1) Nix that knows better what is where (and does not let anybody make any changes) 2) our local tool that handles a uniform solution, e.g. for "style" - that's how my "build.sbt" does not follow the "style" (even the 6-year-old version of that build.sbt, from github, does not).

spent some efforts trying to explain to him that the documentation says that he has to use PUT, not GET.
Anyway, and also, since we are on Newrelic, I went ahead to check if my logging fix is ok, and could not. So Karen sent me a neat sample url for Newrelic, and everything went smooth.
Also, since the "epic" was about MVP, I kicked out two paranoid cases from that epic, it's definitely not MVP, it's 100% quality proof, which I love, but it's not MVP ("minimum viable product"). The MVP has been around for almost a month now, and even Ashok tried it (not very successfully, so far).
Oh, what else: I've cleaned up as much as I can, and now I'm ready to do the scala version transition in the projects. Really, the geniuses from the past made it hard. 1) Nix that knows better what is where (and does not let anybody make any changes) 2) our local tool that handles a uniform solution, e.g. for "style" - that's how my "build.sbt" does not follow the "style" (even the 6-year-old version of that build.sbt, from github, does not).
no subject
Date: 2023-06-22 01:42 am (UTC)no subject
Date: 2023-06-22 10:44 am (UTC)"Wally, I need you to head up our AI project. You'll have no budget and no hope of success. I just like saying we're working on AI. And you're completely useless, so it's a good match."
"I won't let you down."
Да, и чтоб дважды не вставать. Совёнок в жж написала, по-моему, настоящий шедевр. Видно, что выстрадано. Не знаю, в вашем ли это духе:
https://docs.google.com/document/d/196ai-RnXZDOg2-IZ67g3jnP20-3VLCpM/edit?usp=drive_link&ouid=108242853484719706323&rtpof=true&sd=true
no subject
Date: 2023-06-22 11:50 am (UTC)Печально.
no subject
Date: 2023-06-22 11:39 am (UTC)no subject
Date: 2023-06-22 11:50 am (UTC)Probably not. It does not look like it.