Mar. 28th, 2024
So, now I have to find the API properly documented (or not) in "route" code, find a way to produce a) swagger (not necessary), and generate documentation the way "Prism" generates it from samples in shell scripts. Or first generate those samples - the path does not matter, the result does.
The code seems to be written (or copy-pasted) by a Spanish (or Catalonian) guy, and there's a recording of his talk, last July, so I'm trying to ask questions... seems like probably nobody in the company knows. But I love this kind of work.
Asked Janet, who's much more educated and competent than one would expect from a PM. She provides me with all the information she has.
Besides, we had some meetings... one was about yet another crash; and another was just a joint lunch, where we discussed movies (I recommended "Resident Alien").
So I jump from experimenting with shell scripts, written with an amazingly high quality, checked with shellfmt - in which the whole Mermaid files generation is written, so they actually first, run shell scripts to talk to a service, then generate docs and diagrams out of this experience. Really cute.
But since all this requires more mental efforts than just sitting on your ass and typing, I get distracted all the time. It's okay.