Evolution Of A Roach

-
Growing up in New York City gave me plenty of opportunities to observe roaches.  I remember the first ones I saw run away from me in a straight line.  Despite their speed, they were easy to chase down and step on.

A later generation of roaches learned to zig-zag as they tried to escape.  Those were much harder to catch.

Then there were the roaches I spotted on the wall.  They were fairly easy pickings, but a later generation startled me.  As I closed in for the kill, they let themselves fall to the floor and then scurried away.  Their ability to learn and evolve was little bit frightening.

I was a child then, and now, as an adult living in the suburbs, haven’t seen a roach in quite a while… until recently at Grand Central Station.  That day, like all the days before, morning commuters slowly, quietly, somberly, shuffled off the train toward their places of work.  But the woman in front of me suddenly broke stride and jumped and twitched.  Then zigged.  Then zagged.

Then I saw why.  Great Kafka!  In front of her was the largest roach I had ever seen.  No, it wasn’t carrying a briefcase, but that doesn’t mean it didn’t work on Wall Street.  Frightening indeed.

Comments

Post a Comment

Popular posts from this blog

Bookshelf: UNIX A History and a Memoir

-
Image
  A man page will give you, in black and white, specific information about UNIX. Brian Kernighan's new book adds color and depth about UNIX you won't find anywhere else. I'm not a gray beard (yet), but I imagine they would plow through the book knowingly, but at the same time, learn a few things. Those new to UNIX -- recent college grads or those experimenting with Raspberry Pi -- would be better off starting with Chapter 8 which describes more relatable events and the descendants of UNIX, including Minux and Linux. It's when they start to ask questions like "Where does UNIX come from?" and "Why is Gamora grep?" that they should start from the beginning: Bell Labs, 1969. Kernighan opens with a birds-eye-view of Murray Hill New Jersey, zooms in on the buildings, the offices, the significance of Center 1127, and offers a brief look at some of the key players there. As I progressed through the book, the two factors that made UNIX not just possible, bu
Read more

Bookshelf Classic: The C Programming Language

-
Image
My first job had me programming in Microsoft BASIC for the IBM PC (DOS).  BASIC worked well enough, but its limitations were clear.  The language was interpreted and therefore slow.  More importantly, it wasn't a modern structured language, and instead, relied on line numbers and the GOTO statement.  Anyone who has read Dijkstra knew  GOTO was a bad thing . Having learned a structured language in college ( PL/I ), using BASIC felt unnatural.  When a C compiler became available for the PC, I saw a chance to improve and modernize our software.  The problem was selling the idea -- a problem made harder because I wasn't fluent in C. "It would be a staffing problem.  Not many people know C, but we can find a lot of programmers who know BASIC," noted one manager. The argument was strong as my knowledge of C was weak.  But I knew that C, by design, was a small language and thus easy to learn.  "It has about 30 keywords," I proffered to another manager. U
Read more

Connections

-
Image
Opening a drawer in my hotel room in Toronto, I found this.  I worship at the altar of tech, but I imagine the reaction between two priests might go like this: Mormon Priest:  "At least we're wireless!" Catholic Priest: "And from the very beginning too!"
Read more