31 comments

[ 3.1 ms ] story [ 81.4 ms ] thread
I think we 'code writing nerds' are to some extent influenced by the machines that we interact with on a daily basis, we learn to spot the 'bugs' before they bite us by mental emulation.

Computers have the uncanny ability to do literally what you told them to do, but rarely what you meant. So when someone says something (even in poetry) we tend to temporarily suspend our humanity and we read it in this exact literal sense, out of sheer habit, and respond just like the machine would respond to us to any inconsistencies or ambiguities.

"Tea or coffee? Yes, please."

Little children sometimes go through phases of this kind of behavior too, and as a programmer I can usually have a lot of fun with them by playing the game right back and watching their responses.

I once offered a (computer scientist) friend of mine some chocolate. He said "I'll have one or two squares, please". I gave him three.
Hehe, that's funny. That's what you get for not specifying if you mean a binary or a logical or.
In binary the logical 'or' would give you three. Take'em one bit at a time from least significant to most:

  2 | 1 
  -----
  0 | 1 = 1
  1 | 0 = 2

  1 or 0 => 1
  0 or 1 => 1

  2 | 1 
  -----
  1 | 1 = 3
(comment deleted)
Recreational pedantry isn't confined to programmers. My dad was a lawyer and he would do it too, but he did it for amusement value rather than force of habit.

"Would anyone like tea or coffee?"

"I'm sure someone would."

"Would you like tea or coffee?"

"Yes please"

"Which one?"

"Coffee, please"

There is a very strong parallel between lawyers and programmers though, programmers use formal languages to communicate with machines and lawyers use a variation on human languages to remove all ambiguity from it.
Legalese is way too confusing to qualify as non-ambiguous. I doubt most lawyers really understand what they're saying.
It just looks confusing because you're not accustomed to reading it. The bizarre turns of phrase are just as transparent to lawyers as an if-then-else statement is to a programmer.

As evidence, I provide the fact that court cases rarely come down to ambiguous phrasing in the legalese portions of the law.

Programmers don't understand code all that much. They understand it at the moment they write it, and they can understand it when they focus on reading it, but other than that, they rely on the machine to execute it.
Kind sir, have a look at http://www.python.org/
I work in python all the time, kind dude.

And, are you suggesting legalese to lawyers is like python to us?

Even if it was: I can't execute a python module in my head!

I can read it several times and I might have a guess at what it does, but I can never execute it as well as a machine does. Also, I would invariable end up with bugs that I can only fix by inspecting how the machine executes the code, for example by stepping it through a debugger, or running portions of it in an interactive interpreter (aka REPL).

Ironically the true literal interpretation of "Every moment dies a man, Every moment one is born" is more correct than Babbage gives credit for.

If one and 1/16th is born, then certainly one is born!

I think that your comment actually illustrates what jgc was getting at better than he did :)
Yes, so true. It's a pity that if there was a reply from Tennyson it is lost (I have searched his letters for one). Perhaps he would have replied to Babbage that he had simply rounded the figure to the nearest integer, whereas Babbage has rounded to a rational.
So maybe, "Every sixteen moments die sixteen men, every sixteen moments seventeen are born" ?
Plays havoc with the poem's meter, though.
And actually, I'd also say that there's never a moment where 1/6 man is born.
What, you think births are instantaneous? It takes quite a while for a baby to be born, so for a reasonable finite-time definition of "moment" I can quite easily imagine one sixth (or one sixteenth) being born in that moment.

Though I am concerned about men being born, instead of babies.

Your'e wrong. My point is there's no such thing as half a person or 1/6 of a person. The birth process might be half-way through, but that doesn't mean 1/2 a man (or a baby) is born. It means a baby is half way through in the birth process.

When you say half a person is born, "born" implies the birth process has finished and we ended up with half a baby. And that doesn't make any sense.

"Your'e wrong."

Best contribution to the pedantry discussion so far.

I contend that if a given baby is eighteen inches long, then in a period of time when three inches of that baby exits the appropriate orifice we have witnessed the birth of one sixth of a baby. Put six of those together and you have a whole baby.

In that case, no people are born every moment.

Every few moments dies a man, Every few moments one is born.

But that's not the case, because born is present tense as well, not only past tense. "Babies are being born".

Every few moments one is (being) born.

Alternately, born is a variation of bearing - a woman carrying a child around is bearing it from A to B. Afterwards, it was born from A to B. In that sense as well the original wording makes sense, with a different meaning.

a woman carrying a child around is bearing it from A to B. Afterwards, it was born from A to B

Surely that would be borne, not born.

Wrong. 'born' is not in present tense. 'being born' is present because 'being' implies the present, not because born does. Same applies to 'being carried': 'carried' does not in any way imply the present.

And, moment doesn't have to correspond to an SI time unit 'second'.

And no, a poem doesn't have to be an accurate description of reality (if so it would hardly qualify as a poem).

And my point is: stop trying to make it more accurate, because your attempts are futile; you're only destroying the poetic beauty without any gain to justify that.

Precisely. Even more precisely, births and deaths are random / chaotic, not a steady state. There are moments without a death and moments without a birth, and there are moments with many deaths or births. So even Babbage is not 100% technically correct.
You mention that anyone who deals with computers "ends up training themselves to spot minute details that are incorrect or out of place". I agree, but would also come at it from the other direction; people who are inclined to spot minute details are good at dealing with computers.
If poetry is about reality, then there's no such thing as poetry.
> persons of great computational ability (which I shall refer to as nerds)

I consider myself a nerd (obsessed with computers, technology, programming), but I'm not of "great computational ability", in fact, I hate crunching numbers, and I hated highschool math. The value of PI never fascinated me, I never tried to memorize any portion of it (other than 3.14).

I'm an 'INFP'[1] so I tend to look at the big picture and ignore the details. I only dive into a detail temporarily, on an as-needed basis, to fix a bug or improve performance, or something like that.

Point is, not all computer nerds are math geeks.

The only math I loved was elementary math, first degree equations, and from university: discrete math.

[1] http://personalitytype.com/career_quiz_2

Point is, not all computer nerds are math geeks.

He didn't say they are, he merely said math geeks are nerds.