![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Had a bunch of meetings and talks. Kind of agreed on the APIs that I should specify; I'd have written the doc, but there's an urgent failure which I was investigating. Yes, with the code I've been working with.
It turned out that there are two processes, one is the service, another is the job; both do the same thing, but the data structure they use, which is supposed to be the same, is declared independently, and is different. And yet another, under the same name, is declared in another service, but that one is different, so I just renamed it.
So, instead of writing specs, I'm bugging our partners (from a different dept) regarding what exactly are they sending us (or we are sucking from them) - that structure is supposed to be the source of truth, but we don't even know where it is documented.
That's how I ended this day.
Also, thanks to Karen, I now know that what that team calls "playlists" is called "collections" in our codebase. Fucking weird. Why not have a glossary? Or a thesaurus. Will have to talk with Jacob about it. Microsoft had, a while ago, a book of terminology. So should we. Just a page.
It turned out that there are two processes, one is the service, another is the job; both do the same thing, but the data structure they use, which is supposed to be the same, is declared independently, and is different. And yet another, under the same name, is declared in another service, but that one is different, so I just renamed it.
So, instead of writing specs, I'm bugging our partners (from a different dept) regarding what exactly are they sending us (or we are sucking from them) - that structure is supposed to be the source of truth, but we don't even know where it is documented.
That's how I ended this day.
Also, thanks to Karen, I now know that what that team calls "playlists" is called "collections" in our codebase. Fucking weird. Why not have a glossary? Or a thesaurus. Will have to talk with Jacob about it. Microsoft had, a while ago, a book of terminology. So should we. Just a page.
