Skip to main content

It's You, Your Books

A response to Literary Dealbreakers, itself a response to a NY Times article, It’s Not You, It’s Your Books:

From a distance, not reading is a deal breaker, and for the most part it is valid. Like many others, I’ve known wonderful people, in my case women that were engaging and sexy, but didn’t read. In the long run, the lack of intellect is killing. My wife has always read a great deal, but I tend toward the abstract and difficult, Pynchon, Borges, and Beckett - I guess I’m the pretentious one - while she enjoys classics, memoirs, mysteries, and authors like Kundera. To me, it matters that one reads and has an engaging mind.

There were many times in my life that I’ve felt love for books, for language, and for words. Who among us hasn’t? It’s absurd not to look for, to find, someone that shares something so basic to one’s self. The freedom that I feel to speak with my wife, our joy in wordplay, her ability to make the funniest old songs new by changing the lyrics, those ‘yes’ instances when we find a word particularly engaging, are part of what make life special.

Books speak volumes about one’s self, it would be absurd to ignore them.

Comments

Popular posts from this blog

Behave: The Biology of Humans at Our Best and Worst by Robert M. Sapolsky My rating: 5 of 5 stars I finished reading this crying. It is a work of neurobiology, social science, anthropology, and history, but ultimately it is a work of great humanity, suggesting ways that humans, our groups, our systems, and our societies can be made better. View all my reviews

Don't learn to code. Learn to think.

A response to  Don't learn to code. Learn to think. : Below is is my usual response when I see an article stating that everyone should learn to code:  Rather than programming, it is more important to impart the thinking of computer science (CS) than a specific implementation. Programming can be an end point for some students, but it is likely that programming itself will be increasingly automated, so that one needs more the general concepts common in CS. Even then, programming itself is to some degree a grunt task that one progresses beyond:  The following are typical components of a CS degree: algorithms & flowcharting systems thinking logical systems and set theory object-orientation & patterns probability, statistics, mathematics All of the above can be useful in an increasingly automated and data-driven world.

A Journey — if You Dare — Into the Minds of Silicon Valley Programmers

My responses in a NY Times comment section for the book, Coders: The Making of a New Tribe and the Remaking of the World by Clive Thompson : #1 - Link Although I've been a software developer for 15 years, and for longer alternating between a project manager, team lead, or analyst, mostly in finance, and now with a cancer center, I found it funny that you blame the people doing the coding for not seeing the harm it could cause. First, most scientific advancement has dark elements, and it is usually not the science but how it is used and sold by business people that is the problem. This leads to the second problem, in that it is not coding that is in itself problematic, but specifically how technology is harnessed to sell. It is normal and desirable to track users, to log actions, to collect telemetry, so as to monitor systems, respond to errors, and to develop new features, but that normal engineering practice has been used to surveil users for the purpose of selling. Blaming