Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @dan@d.sb

  • 4 Posts
  • 1.26K Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle

  • You could archive a description of the file format alongside the files. Maybe a pseudocode implementation too, or actual code (although who knows which programming languages will exist 300 years from now).

    Or the dreaded .doc and .xls that even Microsoft has problems with today.

    The US Library of Congress recommends archiving data in SQLite databases, since it’s a simple, well-documented format, SQLite is public domain, and SQLite devs have promised to support it for a long time and retain backwards compatibility indefinitely.

    CSV and TSV are okay too of course, but it’s often much easier to deal with large datasets if they’re in an actual database format.



  • I used to work for an Australian company that produced HR software - recruitment, 360 reviews, etc. Our job application form had a fairly standard list of titles (Mr, Mrs, Miss, Mr, Dr, and maybe one or two others) that nearly all clients were happy with. However, a university asked us to add maybe 60 more, much like the list in this screenshot. Some understandable for a university (things like “Prof” or a suffix of “Ph.D.”) and some… less understandable (Colonel, Lieutenant, General, Father, Capitan, Sir, The Honourable, …)

    The customer is always right… We had to add a “huge list of titles” feature flag to the system, that was only enabled for this one client. All other clients were fine with the standard list.