When I make word clock, I make it change from "SATU LEBIH DUA" ("ONE PLUS TWO", 01:02:00) to "SATU LEBIH TIGA" ("ONE PLUS THREE", 01:03:00) at 01:02:30.
But if I make digital clock, I make it change from 01:02 to 01:03 at 01:03:00.
The problem is the fake storage can just overwrite the new data on top existing data. Then you always confirm new data is correct because it broke the old ones.
But something like 2TB micro SD when actually it only has 64GB capacity, that will be very long time waiting 2TB to fully written.
How about write some file, then verify sometimes the new sometimes the old one, repeat until full.
There's a challenge where you see words like "RED BLUE YELLOW GREEN PURPLE", but they are written in color different to their name. You are challenged to say the color of the text and not read the word out loud.
Intentionally defocusing your eyes makes that challenge trivial.
Would have expected something more sophisticated, where the shader also looks at subpixels, where it gets the best matching char for the shape and brightness.
Like rastapasta map renderer did with the braille block:
Radian don't give simple numbers for simple angles.
For example the right angle, in degrees it is 90deg,
in radian it is 1.5707963267948966...
Better using tau-radian, it is 0.25tau (right angle is 0.25 of full circle).
When I make word clock, I make it change from "SATU LEBIH DUA" ("ONE PLUS TWO", 01:02:00) to "SATU LEBIH TIGA" ("ONE PLUS THREE", 01:03:00) at 01:02:30.
But if I make digital clock, I make it change from 01:02 to 01:03 at 01:03:00.