SQLite, sure, but I don’t want a coworker who chooses the hand-crafted full-scan on artisanal csv libraries or w/e
Exercise for the reader: avoid re-reading the PRNG state file on retries.
How about instead we just generate a uuid4, insert it into a sqlite file or Postgres database, and then the postzegelcode value is threefry(SECRET,uuid)?
I don't quite understand why programmers love minimalism more than reusing widely trusted and very easy solutions that are known to perform well.