Skip to main content

The Meanings of Ender's Game


In response to an Ender's Game discussion (Goodreads), with a link from Reddit, I posted the following:

Much of the Reddit stream seems to focus on military tactics, or the lack thereof, used by the Ender, but who reads Ender and thinks it about military tactics, except the 20-year old grunt that started the thread?

For a book written in the 80's, then edited in the early 90's, it seems more prophetic, with its use of game immersion, remote military operations and portable computing. Then when you think about the use of children in military games, one can think somewhat more deeply about sociopolitical indoctrination.  The series itself becomes a broader exploration of empathy and foreign culture.  The criticism seems more like the problem of a man with a hammer, who thinks every problem is solved by hammering, but even worse, every problem is about hammering.

An additional post, regarding suspension of disbelief:

Some people commented on the suspension of disbelief, and that they could not suspend disbelief. I have at times wondered what is required for suspension to occur. With any great science fiction, suspension of disbelief is required to tolerate the seemingly impossible. For me, with Ender, it was simple, and I did not suffer from doubt about possibilities, but for me acceptance occurs in the beginning of the book, and afterwards I only question the actions of individuals, as to whether they are plausible actions given the character and setting.

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

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

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.