I don’t know when this change was added, but the dark mode switch in @tonsky’s site now glows in the dark! Seeing it for the first time, I laughed. I love this website’s design so much. It’s irritating but in the most entertaining ways imaginable. 😄

I notice that @andfadeev288 Andrey Fadeev

https://youtu.be/ji-D5PhPZoE

I'm designing a new API for a deal booking service. Main task right now is to explore existing request schema. There were three APIs before - all of which accepted xml requests. A request can be of different trade types and based on that the XMLs vary. There are some common stuff like ids, users, etc. But meat is about legs, instruments, and economic details. I have collected one sample trade per each distinct trade type per API and dumped these into fs as json, edn and original xml. Now I have to go through these and look for common structural parts that can be extracted and think. I was wondering in addition to simply eyeballing, are there any tools techniques I can use here? I remember malli had some functions where I can input some sample data and it'd infer the schema. I will try this out but my feeling is that this is a little too coarse. I am interested about the structural level. I think LLMs might be useful and I'll check that out too. Any suggestions, ideas?