dybr

 As vit_r  suggested, I maintain a spreadsheet to trace the cases I do. Got 5 more cases last week, today put them in the table.

Actually, since my head was filled, in the morning, with the problem of docs generation, I wrote to three of my ex-colleagues asking if they could remind me how t.f. we generated swagger docs from code. Chris wrote that it was in the opposite direction, have swagger files, generate code.

Oh. not what I needed. So it was not in iHeart, it was in Machinify. Ok, ok. Will ask someone there.

But actually, that would be a big job, to implement all this, and the company won't be interested. Let me generate the docs then.

Wrote a design doc for that, with options, and the final ("best") option - scan the code, extract endpoints, generate scripts for that. Parsers-combinators. Then generate docs, fill in the docs repo; not a big deal, except that this may involve some amount of manual intervention.

Shared the doc with Janet; she's going to discuss it with Jeremey, so after that, we agreed, I'll share it with the team. We will see.

The problem with me doing a contract job is that I can't stop thinking. Have to distract to something unrelated. They don't pay me for thinking on weekends. I'm not exempt.