I'll rephrase. Learn about the basic container data structures like linked list, vector, set, map, hash, tree, queue, heap.
Study time complexity of insertion, deletion, search, etc. in these data structures. Then you will understand when to use which. Big O notation is used to express time complexity for expected runtime of the operations.
This calender-thing really seems to resonate with people!
I built something similar but more versatile, where you can either display images or feed the display with whatever information you want remotely. And it runs on a battery for a whole year:
The written sizes are correct. By default I will manufacture the two smaller displays with the same frame dimensions. The small device in the comparison image is from a custom order, which allows for a better size comparison. For custom orders I can create the frames in arbitrary sizes accurate to a millimeter. I'll add a note.
I actually have an Inkplate at home. The 8 gray shades they support are unfortunately not evenly distributed, which makes it difficult to display images in good quality.
You can't define more than 8. The API allows only 3 bit input. I also tinkered with the lookup table, and was able to create a lot of different gray shades, but I was not able to produce ~40-60% gray.
If you want to hack it and don't want to pay for consumer grade quality for neither hardware nor software, then the device you linked is a good choice.
e-Ink price tags are designed to be used and abused by store public who do not care about store property. They are built like tanks, so "consumer-grade quality" would in fact be a downgrade...
I just wanted to show off the new battery-powered E-Ink picture frame that I have been working on for the last couple of months.
It took a lot of work. I hope you like it.