It used to be that integrating similar apis was so easy, the usual way to do so seemed to be, unless you were closely involved with the designers of one of the projects, to actually start an entirely new one that superseded both. The issue with me doing that is that I would be likely to have a psychotic break when people wanted me to fix bugs they reported. So there's more return for me if I can get the existing projects to integrate or generalise. But the option is open, since it's all pie-in-the-sky.

One big challenge for me has been graphics libraries. Displaying anything visual for me has gotten difficult in great depth. Graphics libraries are a great way to open api challenges for me, there's always pressure. It's so hard to think of software integration. One of the big daunting parts is the number of api functions that can be involved. It just _feels_ so hard, to have more than three or so api functions at once -- and real libraries may have hundreds of these. With dissociation, I can describe relatively easily some coping strategies that could work for these. For example, noting down similarities, properties, or patterns in specs while reviewing them. Porting an API doesn't need to require a huge short term memory, although it's certainly most intuitive to do it with use of one. Maybe when comparing two apis I might scroll down both lists, either in parallel or in sequence, and implement every function in both. So, each time I encounter an api function, I could for example look through the ones I've written, and make sure it's included. This can in theory only require remembering one function at once, although in reality some conceptualisation needs to be sustained around norms and patterns of the whole or of larger groups of functions. It used to be a simple, relaxing, and satisfying task, like knitting a scarf. A rote thing that makes something organised and quality at the end. Maybe some of that relaxation can get inhibited if one has to handle memory problems, or is triggered in some way by executive organisation tasks. Maybe that's my biggest issue, even, engaging these difficulties I have without disrupting work. Sometimes, rarely, I'm in a state of mind where I can just do it, and powerhouse through. This is pretty rare and random-seeming.

The task of judging a library to start with has similarities to the task of integrating or composing two libraries. Regarding integrating or composing, an interesting example is machine learning backends like tensorflow or pytorch. These all have to integrate multiple vector math backends, in an organised way, with developers likely on a time budget. It's an example of people successfully doing this in recent years. Regarding judging libraries, the similarity relates to their being lengthy lists of api functions, featuresets, or similar, and the need to summarise or hold in some way, what is important or possibly relevent about these, in order to consider them as a whole with other sets of stuff. The biggest issue for me with retaining such useful considerations is that I lose the parts. Amnesia, disorganization, incineration ... Retaining basic small information. Similar to "awesome" lists on gits. And using parts of this information to relate with other information, make decisions, and do work.

Another thing to think about, is that there are a lot of things in my life that have really really suffered as I engage difficulty organising, generalising, integrating information. My possessions and schedules are an infinite mess that needs addressing. The job can seem too large to tackle. That bears similarity with the task of integrating large libraries or codebases.

0608 I'm a little confused around my goals with my mediatek phone. I'm aware of these specific parts: - flash an open source operating system - be able to dump firmware images for security We could call the goals "OS" and "IMG". IMG can appear partly compromised if access to the phone's firmware is not reliable. If there is a way for code to be installed that fakes the firmware download. In the end, a possible and likely solution to that would be to wire directly to the arm chip on the board. I don't need to do that here. I'm happy just making progress; improving my habits. But the imperfection of the IMG goal if the flasher I'm using uses an exploit that I don't understand, can seem strongly to make it hard to hold and relate with other things.

0612 I'm leaving this system and doing something else, but I brought the phone back near the system with existing work, at least. I'm planning to return but haven't prepared the memory parts to make that likely, quite yet.

0929 Windows booted up, and I remembered I have a working linux flasher. I'll flash from windows for now I finish the task with more likelihood.

0931 I have the phone connected. It's set up for a factory partition map. I remember the way I got it to work was either modifying the factory map .... or just using fastboot. I also remember that I unlocked the bootloader using the factory rom, so I'll flash that, reboot to linux, and try to remember: "just use fastboot to flash a system image" .

0946 my system says it is very out of date. I thought I recently upgraded all the packages. 0946 oh, it isn't completing because there are pgp key mismatches.

1026 I wanted to set the phone up to resume buggily logging brainwaves using my comfortable Muse S. It is not working for this at this time. I have not diagnosed it. I did not expect this.