Day 19/90: File I/O
Today's note was about making file i/o explicit about data shape, encoding, and failure points. I kept coming back to the same checks: name the file, network, or serialization boundary before writing the code that crosses it, keep data shape and encoding format visible so corrupt input is easier to spot, and make cleanup, partial writes, and decode failures part of the design instead of lucky edge cases.…
