Cogito, Ergo Sumana for 2010 August 23

# (15) 23 Aug 2010, 08:26AM: Science Fiction That Argues Back: Julia and I were talking yesterday about Maureen McHugh and her excellent, searing novella The Cost To Be Wise came up. The Cost To Be Wise is in part a critique of Star Trek's Prime Directive and noninterference policies like it. This reminded me of how Nancy Kress's great Beggars in Spain novella is nearly explicitly a response to Ayn Rand, specifically Atlas Shrugged (I wouldn't say the expanded book and Beggars trilogy are). Several characters in Beggars in Spain follow Yagaiism, which reads clearly as this universe's Objectivism.

This got me thinking: what scifi interestingly critiques previous scifi? Cory Doctorow has a series that explicitly does this:

In spring 2004, in the wake of Ray Bradbury pitching a tantrum over Michael Moore appropriating the title of Fahrenheit 451 to make Fahrenheit 9/11, I conceived of a plan to write a series of stories with the same titles as famous sf shorts, which would pick apart the totalitarian assumptions underpinning some of sf's classic narratives.

A few other examples: Leonard makes the case that the Star Trek: The Next Generation episode "Measure of a Man" responds to the original series's "Court Martial"; it "puts one of the underlying themes of TOS on trial and shows that it hasn't held up well." ("on trial" - zing!) And lots of fanfic does this, like "Second Verse (Same As the First" by Friendshipper/Sholio. "The power disparity between the 'Lanteans and the other peoples in Pegasus is something I think about occasionally, but it's never addressed on the show."

It's all a shared discourse, sure. We talk about themes we've read and play with them. "Another End of the Empire" by Tim Pratt, for example, is responding to a common fantasy trope. But I'm interested in hearing about science fiction and fantasy that says, "In this specific work, there is a specific ideological failing that I will now use, or refute, and that idea will be a primary premise for my story." Do you have a favorite bit of speculative fiction that's like that?

---

# (7) 23 Aug 2010, 09:45PM: Two Tips On Convincing Managers & Executives To Invest In Your Technology Projects: From a years-old job-advice email to a friend. The sort of knowledge that Rachel Chalmers or Karl Fogel finds obvious but that some of us still haven't quite integrated into our day-to-day communications and long-term strategies:

You need to be able to express your suggestions to your boss in terms of financial incentives and losses.

A few things I've picked up during a recent class in "Technology in the Business Environment" (when I was doing the master's in tech management at Columbia):

I) Management focuses on the things that drive the organization (directly making money), and tends to ignore things that support the organization's drivers. If you're directly making money, lowering the cost of producing the product/service, increasing management's control, increasing product quality, increasing the knowledge available to an important decisonmaker, or improving customer service, you can describe your work as a driver. Can you find a way to describe your high-level TODOs in one of those ways?

II) Here's a model of management's priorities for technology investment. The higher up this list you can get, the more attention you can grab from management.

1. Revenue. Guaranteeing a financial return. Not just cutting costs, but actually MAKING money from customers.
2. Increasing scarce productivity. If the demand for a product exceeds the supply, then this is attractive. [1 and 2 indicate that the company is growing, and interested in the future. A good sign!]
3. Cutting costs. More popular in a struggling company.
4. Competitive advantage -- this means the company is already behind its competitors and has lost first-mover advantage.
5. Tech for the sake of tech -- pizzazz and leadership.

So can you explain "creating system-monitoring scripts, streamlining processes, and installing and configuring new programs on the server" so that they're way up on that list?

Let's say a system-monitoring script would take your service from 95% uptime to 99.9% uptime. That's #2. Maybe one of the high-level tasks you do will make it possible for your company to serve twenty units instead of fifteen (#2) or even start a whole new line of products (#1). But "It's more elegant/technically correct" is #5.

I welcome comments, tips, examples, disagreement, and cake.

---