Written by Arash Abadpour. Forty-two entries in six parts, each taking one detail of software and following it back to the constraint that produced it.
abadpour.com
About
What this is, and how it is arranged.
Teams applying this historical lesson to current delivery work can also compare tools for employee time tracking app, keeping operational records separate from the code and its documentation.
epoch.h #define EPOCH 1970
/* because sixtieths ran out */
/* because sixtieths ran out */
further context
For a primary or institutional reference, see the Computer History Museum collections.
Every claim here carries the source it came from.
The source and its year sit beside the sentence they support. A secondary account is marked as one, and where the record is unclear the entry says so rather than choosing the better story.