CEO: This Superfish incident has put our credibility in the toilet. Even corporate customers are looking askance at us now, and we didn't put it on their computers. Suggestions?

Executive 1: Lay low until it blows over.

Executive 2: Hire a new PR firm.

Executive 3: Start a social media campaign.

Genius executive: Maybe we should promise not to do stuff like that anymore.

It'll be one of those moments I'll remember, like coming into work and being told about the Challenger disaster, or turning on the car radio and hearing the hushed voices of the announcers on 9/11. Like so many people I feel a connection to this wonderful man.

Of course he did more than play Spock; and in the early post-TOS years he was famously ambivalent about his association with the role. But he did something special with that role. It's easy in the fog of nostalgia to forget that man TOS scripts weren't all that great (although some of them were). The character of Spock might have become just an obscure bit of pop culture trivia; instead Nimoy turned Spock into a character that I feel sure actors in our grandchildren's generation will want to play and make their mark upon.

What Nimoy brought to that role is a dignity and authenticity, possibly rooted in his "alien" experience as the child of Ukrainian Jewish immigrants. In less sensitive hands the part might have been a joke, but I think what many of us took away from Nimoy's performance was something that became deeply influential in our world views. Nimoy's Spock taught us that there was something admirable in being different even when that is hard for others to understand; that winning the respect of others is just as rewarding as popularity. The world needs its oddballs and misfits, not to conform, but to be the very best version of themselves they can be. Authenticity is integrity.

It's customary to say things in remembrances like "you will be missed", but that falls short. Leonard Nimoy, you will live on in the lives of all us you have touched.

I wonder how much direct or even second-hand knowledge of unions you have.

In my family we've been on both sides of this issue. My sister, who is an RN, just recently led a successful but bitterly contested unionization drive of her hospital. The impetus for bringing in the union was that after privatization the hospital cut staff so much the nurses feared for patient safety. Nurses don't just administer medicine and make beds; one of the most important things they do is catch mistakes. When a surgeon starts prepping the wrong limb for amputation or an internist accidentally prescribes a medication that will kill the patient. It's nurse's job to catch that. It was unequivocally fear of making mistakes that drove the nurses at that hospital to unionize.

Did she piss off the hospital's new owners? You bet she did. But would you rather go to a hospital where the nurses *lost* that fight? How would you feel about the nurse checking your medications had worked back-to-back weeks of double shifts caring for more patients than she (or he) can keep track of?

On the other hand my brother is a senior executive at a large food service company. He told me about a meeting he had with a local African-American union representative where she played the race card with the first words out of her mouth. This was pointlessly antagonistic, in part because while my brother is a conservative he's open-minded and has a good track record of working with the unions. But mostly pointless because we're not white. We can pass, but as the genealogist in the family recently figured out we have only about 1/3 European ancestry. Fortunately he could laugh that off but if he'd been white and thinner-skinned that might have driven the negotiations into a ditch.

Well, this "richest country in the world" business is somewhat misleading. It means the country with the greatest aggregate economic power, not the country where people tend to be the best off. You need to look at several measures before you can begin to understand the thing that's mystifying you.

By total GDP the US is by far the wealthiest nation in the world. It has almost twice the total GDP of the second country on the list, China. By *per capita* GDP, the US is about 10th on the list, just below Switzerland; so by global standards the typical American is wealthy, but not the wealthiest. On the other hand the US ranks about 20th in cost of living, so the typical American has it pretty good.

Where things get interesting is if you look at GINI -- a measure of economic disparity. The most equal countries are of course the Scandinavians, with Denmark, Sweden and Norway topping the list. The US is far from the *least* equal (Seychelles, South Africa, and Comoros), but it is kind of surprising when you look at countries near the US on the list. Normally in most economic measures you see the US ranked near advanced industrialized countries in Europe, but it's neighbors on the GINI list are places like Turkmenistan, Qatar, and El Salvador.

What this means is that we have significant classes on either end of the scale: the *very* wealthy and an economic underclass. Now because of the total wealth sloshing around in the US, the US underclass has it pretty well compared to the underclass in, say, India. But what this doesn't buy is clout or respect. "Poor" households in the US usually have TVs and refrigerators -- a fact that seems to anger some people, who see the poor in the US as ungrateful people who are too lazy to improve themselves. But a study by the OECD suggests that they don't have the *time* to improve themselves. In a ranking of countries by time spend on leisure and self-care the US ranks 33rd, at 14.3 hours lagging almost two hours per day behind world leader Denmark (big surprise). But remember this is an average; it doesn't represent the time available for the poor.

Most Americans seem to think that poor people spend all their time sitting around waiting for handouts. This willfully ignores the phenomenon of the working poor. After selling my company, I volunteered on a lark at a charity which refurbishes old furniture and household stuff and furnishes the homes of poor people, and I found poor people to be neither lazy nor ungrateful. Let me tell you I have never met so many people who work two or sometimes more jobs. Particularly shocking were the number of women who took their children out of abusive relationships, and then have to work a full time job, raise three or four kids, without a car and in a neighborhood that doesn't have a grocery store. You don't know what gratitude is until you've given a poor, overtaxed mother beds when her children have been sleeping on the floor for months.

When some smug, ignorant and conspicuously well-fed media head starts whining about the poor having refrigerators, it makes me want to punch them in the mouth.

A social media company data mining your communications and sharing the results with third parties shouldn't come as a shock to any social media user.

PCMCIA CF card reader, plus fat formatted CF card, plus USB CF card reader.

Or about a thousand other ways.

Find a compromise between predicting too much of the future and just managing a project by the seat of your pants; get into a rhythm where you check how good your estimations and learn to get better at them.

Of course you can't develop every project this way; I've used Agile and it's worked for me. I've used waterfall and it's worked for me too. You have to try to be sensible; you can't completely wall of other people's need to know when you'll accomplish certain things, nor can you build a solid plan based on pure speculation. You have to have an intelligent responsible way of dealing with future uncertainty, a plan to cut it down to size.

I've even had the good fortune at one point of winning a $750,000 grant to build a system for which no firm requirements had been established. It was kind of an uphill-flowing waterfall: we knew how long it would take us and how much it would cost but we had no firm idea of what we were supposed to build. If that sounds like a recipe for disaster, it was; but my team was *successful* and built a product which was still be used and supported over a decade after the grant finished.

What's missing from many programming estimates is honesty. It's a matter of ethics; you can't take people's money and say maybe someday you'll deliver something useful to them. People don't have unlimited time and money to accomplish all the things that need to be done in the world. It's an honor being entrusted with people's aspirations, and a serious responsibility. It's hard, even nerve-wracking, but you've got to care enough about the impact of your planning on other people to make the effort to do the very best job you can.

And what I've found is that if you do make the effort you can do a surprisingly good job of estimating a project if it's in an area and with technologies you're reasonably familiar with. If you look closely your specific predictions will often be way off, but if you care enough to be brutally honest the pleasant surprises tend to balance out the unpleasant ones.

The loss of time and effort to figure out whether this is going to cause a problem and then the time and effort to get rid of it.

That loss is obvious not much on a dollar per user basis, but if you add up all those users it's enough to incent Lenovo to do something so scurrilous. That's precisely the situation which class action lawsuits exist to redress, and according to the article that's the kind of lawsuit that has been filed.

The issue isn't whether EULAs are *potentially* enforceable. The question is whether *this* EULA is enforceable.

In general there is no contract unless their is some kind of exchange of "considerations". Typically the consideration is the privilege of using the copyright holder's software. But, if you can show that users don't want to use this software, and that it is installed for the benefit of a third party, there is no exchange of considerations between the end-user and the copyright holder, and therefore no valid contract.

You're absolutely correct (except perhaps about the Eemian period not being catastrophic - 13+ft of sea level rise would be nothing to scoff at today!), but none of these facts should rule out making changes to keep the climate in a state that works for our civilization.

We'll probably never have a "good stable state," we'll have to keep making intentional climate alterations constantly in the future - as the population increases, a "good" state will be more and more narrowly defined as well. We can't let the planet's temperature vary anymore, not due to man-made causes today or any natural ones in the future. We have to keep watching the thermostat from now on or it's going to get ugly.

Keep in mind that we're really really good at warming the climate, so we won't fall into another ice age easily.

You have no idea what "scientific consensus" means. It does not mean "unassailable truth"; it just indicates where the burden of proof lies.

Including computer science.

I once sat in on an introductory CS lecture in which the associate professor teaching the course was explaining the requirements for lab assignments. First explained that the students were required to write down and turn in specifications and objectives for each program they wrote. I was very pleased and impressed; I thought this was a good habit to encourage.

Next the professor went on to illustrate things that should or should not be in the specifications. "For example," he said, "you should not specify that the program must halt. That's because it's impossible to tell whether any program will halt."

I could have cried.

We haven't proven a lot of things through full-scale experiment - like gravity and most other things related to astrophysics for example. How do you feel about those? Pure speculation?

We can adjust outdoor climate with greenhouse gas levels as we've been doing, or with aerosols as discussed in TFA.

Funny, that's what I think about denying that fairness is possible.