I went back and looked at the pictures without the words, and it's actually easier to just see what's going on. A couple of the ideas are simple enough that one picture can give you the idea. But others, like yak shaving and garbage collecting, would need a story line and multiple pictures/pages.
You could make an entire series out of these books! There are many great childrens' series, and you can study them to see how they present stories, what kind of themes they touch on, how the characters interact. If it were me writing them, I would parody every great children's book series with each programmer book. A bernstein bears book, a clifford book, a fraggle rock book, a Dr Seuss book, a Curious George book, etc. Each book could parody a famous series, but tell a story to explain a programming concept. You can do much simpler ones for teaching ABC's but it will best as simple concepts that can be grasped with a picture.
However, when I Googled the term I understood it.
A reader may learn a few software terms but I don't think this book would teach anyone, child or adult, a fundamental understanding of programming; which is what I would look for in a children's book. It also significantly narrows your market to only people who already know how to program.
Example: Debugging should have "to figure out just // what has gone wrong".
That said I doubt that's much of a bar to sales.
To me it's a novelty book "A Programming ABC" that people (probably non-programmers) would buy as a gift. The artwork is amazing IMO.
As a teaching resource it seems more like a pile of quirky chapter pages that would preceed in depth descriptions.
I wonder if the pages would work as merchandise, or just framed artwork.