I came here to say something similar. I also have aphantasia, and I generally keep a list of concepts this function (I'm a C guy) needs to do, what assumptions

I came here to say something similar. I also have aphantasia, and I generally keep a list of concepts this function (I'm a C guy) needs to do, what assumptions it needs to make, and where it fits in the general process. It needs to be general enough to be called in other contexts. It should verify that the input pointer is not null and it can safely ignore freeing that as a resource since it's done somewhere else. It needs to return one of these errors, and needs to add one of them to the error/description list since it's new with this function. It needs to handle the case where the passed-in error code pointer is NULL. Things like that. I've tried to visualize code with diagrams and whatnot, and it only gets in my way. I suspect that like some abstract math concepts visualization will always only get in the way except for an abstract very simplified picture of what's going on. But it's certainly possible that I'm missing some visualization skills most 4-year olds have and if I could visualize I would be able to handle it just fine.