Update: my original answer was short because, well, I'm a sailor. But for more, see: https://en.wikipedia.org/wiki/Knot_(unit)
But how did they count "a certain time"? (Before stopwatches).
The British crown established an award for whoever could come up with a precise clock of this reason, it's a fascinating story, I recommend the book "Longitude: The True Story of a Lone Genius Who Solved the Greatest Scientific Problem of His Time" by Dava Sobel.
As done on an ASR-33
When I worked at a company which used a lot of Fortran, I kept a punch card at my desk. Among other things this made it easier to explain to new people why there was a column limit for code.
Eventually an HR person came around and told me to remove the card because the top management was coming to visit soon. Among other things this made it easier to understand the role of HR in a large company.
What on earth?
Leave these glib platitudes at Reddit.
It seems trivial to find a counter example to your claim...
It seems difficult to support even the weaker claim, that there exists an HR department at a large company that defends your interests against that company.
I wonder why you seem so convinced of your position?
One employee had to take down a little American flag (this was two years after 9/11) and another, a trophy the company had given him.
This may be the most obscure reference to a thing that clearly exists that I've ever seen. Well done.
But here's the story: In 2003, jzwinck and I were desk neighbors at a company everyone here has heard of whose original technology was written in the 1980s on computers made by Perkin-Elmer, a big government contractor most famous for screwing up the Hubble telescope's mirror.
Instead of pids, processes had names. You could send a command to them like this: "SEND MYPROG EXIT" and then, if you wrote your program to accept an EXIT command, it would run your subroutine. This was also used for interprocess communication.
Then PE stopped making computers, and the company switched to Unix, but didn't want to rewrite all its IPC code. So it wrote a Fortran function called PEKLUDGE that took a string parameter representing the program name and stored it somewhere so that it could be used to receive IPCs later. The first thing every program did from that point on was call this function with the first arg from the command line, which was supposed to be the program name plus maybe a number if the machine needed to have multiple copies running.
Then they switched from Fortran to C for all new programs, and the way to call old Fortran functions in C was to lowercase the name and add an underscore.
And that's the story of why every program at this company starts with a call to pekludge_(argv)
Larry Wall using the term "patch" prior to that: https://groups.google.com/d/msg/net.news.b/HhK847iU7ZA/7Wox7...
(It was already a well-established term.)
In 1946, when Hopper was released from active duty,
she joined the Harvard Faculty at the Computation
Laboratory where she continued her work on the Mark II
and Mark III. Operators traced an error in the Mark II
to a moth trapped in a relay, coining the term bug.
This bug was carefully removed and taped to the log
book. Stemming from the first bug, today we call
errors or glitches in a program a bug.
Reference (which wikipedia cites) http://ei.cs.vt.edu/~history/Hopper.Danis.html
As for the "correctness" of "bug" - appears you agree this is the first historically documented reference to an insect being the source of a computing error and the "quotes" infer this means insect, though agree this might not be obvious to some.