Skip to content

You call that a name?

Nice posting, rant?, about names.  Falsehoods Programmers Believe About Names

And let me also draw your attention to this extremely interesting talk on “Face Blindness,” or the inability to recognize faces.  A more serious case, suffered by  3% of the population, lack that ability to recognize themselves in a mirror!  It was unclear how many people suffer from less serious versions of this; but even with 3% that’s approximately one in every school room.  So we all know a lot of people who have this.  I got to wondering what it must be like at the other end of this spectrum; is that another affliction?

Cost Benefit Analysis

Plucked from this poignant post about externalities (which reminds me of my realization that limited liability corporations evolved from pirates) is this bit from a Rolling Stone article.  It’s a nice clean example of cost benefit analysis in the “real world.”

BP has also cut corners at the expense of its own workers. In 2005, 15 workers were killed and 170 injured after a tower filled with gasoline exploded at a BP refinery in Texas. Investigators found that the company had flouted its own safety procedures and illegally shut off a warning system before the blast. An internal cost-benefit analysis conducted by BP – explicitly based on the children’s tale The Three Little Pigs – revealed that the oil giant had considered making buildings at the refinery blast-resistant to protect its workers (the pigs) from an explosion (the wolf). BP knew lives were on the line: “If the wolf blows down the house, the piggy is gobbled.” But the company determined it would be cheaper to simply pay off the families of dead pigs.

Billions of years ago, in a course on Biotechnology, I got a A+ for writing a long paper outlining a cost benefit analysis for some research on kidney machines.  I’d written the entire paper in a similar sardonic tongue in cheek tone and I was shocked that the instructor seemed to be oblivious to that.  It was, I thought at the time, the most interesting lesson I took from the course.

I must look for a chance to use the The Three Little Pigs as design framework!

Wii Meditation

It appears that AJ Jacobs is writing a book on self experimentation and this very lovely article on managing the many daemons in your brain is a portion.  It is a good addition to the thread about self control and attention management.

My favorite bit involves a shocking idea.  Language evolved so we could talk to ourselves.  Or, I’d say, so our various inner daemons could talk to each other.  I even find myself wondering if one of them didn’t stumble upon it and discover it now had a huge competitive advantage over it’s siblings.

The less shocking, but still fascinating, is that one way to keep your attention focused is to talk – preferable out loud – about what your doing.

So, what was the catastrophe?

I always assume there was a catastrophe.  Something happened.

A hurricane leveled the forest.   A fire leveled the city due to lack of water.  There was a riot.   An economic bubble swept over the landscape.  The troops came home and a swarm of babies appeared.

The system you are gazing at, which seems a given and maybe slightly odd, is the result.   I learned this rule from “Reading the Forested Landscape,”  if you stand in the forest and all the trees are about the same size it tells you when the catastrophe happened.  That works just as well for housing developments.  If you take the rule seriously then one of your first questions is always: what were the catastrophes?

You can turn this rule around.  Pick your favorite catastrophe and ask how it changes a range of systems.  Catastrophe: Moore’s law, modern managerial practice, the great depression and war?  System: healthcare, civil rights, work?

I was reminded of all this reading an interesting book about the work week, e.g. how long.  I read this book some time ago, so my memory maybe fuzzy.  But broadly starting with the industrial revolution and ending with the great depression there was a broad movement and consensus that the number of hours a person should work each week was and should be declining.

The rational for that trend varied and evolved.  One argument was that democracy demands a contribution from it’s citizens and if they were working all the time they could hardly make that contribution.  Civic duty competing with the employee’s duty to his employer.  Interestingly I don’t recall a religous duty argument being mentioned.   Another argument was about productivity, e.g. that 12 hours work day didn’t actually deliver much more output than an eight hour day.  I gather the data on that is compelling.  There was a economic argument that citizens needed more time off so they could consume more.  And others.

The number of hours worked stopped declining during the great depression and have slowly and steadily risen since then.   Apparently that catastrophe changed the framing.  Suddenly people were horrified that the world economy appeared structurally incapable of employing most of the labor.   One reaction to this was that work should be treated as a scarce good with tight regulations to assure it was distributed equitably.  In that framing number of hours worked have an entirely new rational.

The Congress passed 30 hour work week laws twice during the depression.  Both times the President was convinced by industry to veto the new law.  Both times industry assured him that the depression as almost over, so not to worry.  Both times they were too optomistic.

So that’s an interesting example of how a catastrophe helps to explains a system.

But he tells a story my thoughts keep returning to.

Apparently, to hear him tell it, the depression caused a huge shift in the way that Science perceived and explained it’s role in society.  Before getting into that it might be fun to pause and think: “what is Science’s role in society?”  When I was a kid I recall two common answers: to explain how the world works (often v.s. religion), and the arms race.  But then, pretty much everything’s purpose was the arms race.

Before the depression scientists would appear at the government’s door and explain why they should receive funding.  The argument was largely that they were making the world a better place by relieving man of his labors and improving the efficiency of industry.  But then, 60% of the planet’s labor was out of work and the scientists woke up to discover that they were getting a share of the blame.  So they were like “Oh!  No!  … ah …  That’s not we meant!  (Could you put down that pitch fork please?)   Science?  Why Science’s social purpose is … ah … ah … new frontiers!  Yeah, that’s it!  We discover new frontiers; and each of these creates jobs!  Why just look at radio and air conditioning!  Lots of job, right?”

Of course Science is not the only institution who’s entire purpose was remade by the Great Depression and it’s spouse the Great War.   Government’s was too.

Water in Boston

The big (10 foot) pipe that brings Boston it’s water has suffered a break and we have all been instructed to boil our water.  I see on the MWRA web site that they deliver 167 million gallons of water to 2.5 million residents a day.  That comes out to 66.8 gallons per person per day.  Of course they also deliver water to industry … and more typical leaks.

The paper says that the leak was dumping 8 million gallons an hour into the river.  167 gallons/day is equivalent to about 7 million gallons an hour.

This water is drawn from some resevours in the middle of the state.  The largest of which holds 417 billion gallons, or 6.7 years to draw down at 167 million a day.

Problem: Immovable installed base -> Solution: closed system?

The ongoing puzzle, debate even, about the choice points between a closed and open system appears to have picked up a new aspect.  At least I had not noted this one before.  What differentiates a closed model from an open one is the extent that the business hordes the options created by it’s product offerings.  For the firm the open v.s. closed debate comes down to questions about short and long term advantages for the firm and it’s managers.   A closed approach hold out the hope of better price discrimination.  While an open approach offers a change at wider adoption, more innovation, stronger network effects, and better protection against competitors.

So, the new argument I’d not previously seen goes as follows.  It is on the closed side.  A firm can adopt a closed architecture to deal with the rapid technology change.  Closed addresses the immovable installed base problem.  By making closing things down the firm captures the ability to migrate the installed base more quickly.  Or, so this story goes.

When dealing with the risk of technology driven displacement a large installed base is both a blessing and a curse.   It’s a curse, of course, because it is slow to move.  But it is a blessing since there is safety in numbers, e.g. an assurance that when technology changes you’ll not be left out in the cold.   The suppliers and users will have plenty of common cause to help solve to manage the switching costs.   In a closed system the vendor coordinates that.   You could argue that in a closed system the coordination problem is easier to solve.  I suspect that’s not so clear in practice.  The installed base ties it’s fate to the competence of the vendor.  The vendor is a single point of failure.

Open makes firms nervous.  Management is all about juggling risks.  Closed offers the impression your in control.  This impression is often wrong.  Closed systems lead to the systemic blindness; provincialism.  And yet I find the argument that a closed system is better able to handle rapid technology change sounding pretty good.  Possibly that’s because it’s about supply side risks.  I wonder why I think the closed system blindness issue is less serious on the supply side v.s. the demand side.

Having engaged with this debate for twenty years, and now finding it kind of dull, it’s a delight to see a new aspect to it.

Problem/Solution

I’ve not read Stephen Prothero’s recent book “God is Not One.”   But, listening to him interviewed last night I was much attracted to his list. What each of the eight major world religions treat as their big problem, and what their solution is.

Religion Problem Solution
Buddhism suffering awakening
Christianity sin salvation
Confucianism chaos social order
Daoism conformity naturalness, simplicity
Hinduism endless cycle of reincarnation release
Islam pride submission
Judaism exile return to God
Yoruba disconnection follow our destiny as revealed by diviners

It is likely I’ve made mistakes in the above, it’s based on some web browsing and what I recall from the interview I listened to. More rows and columns would be fun. For example principle rituals would make a great additional column.

I am a sucker for frameworks like this.   That is a variation on one of my favorites.  This one about sketching out the differences between Puritans and Quakers - a dialectic that has much to says much about American culture.

It would be fun to have a table like that for programming languages.

Facebook PAIN

In the best scenario all Facebook is doing with their new service that allows 3rd party sites access to your Facebook identity along with a bit of what they know about your is a slightly more transparent version of what, say, Google’s Doubleclick can does. They are selling a service to their partners that identifies the visitor. It removing their anonymity. These tracking networks are troubling from a privacy point of view since they enable trafficking in a surprisingly detailed user profile. For example it enables knowing that your currently working, or shopping, or away from home. Browsing Yelp for a resturant? Working on your a Microsoft document.

We need a name for these networks that enable the trafficking in personal data. How about persona-attribute-info-network or PAIN. There are other PAINs. The credit reporting in the financial industry for example. There are ones in health insurance. There is usually one for every kind of license, i.e. drivers licenses. In the long run, i.e. after fortunes are made and I’m dead, these tend to get a complementary “privacy protection act” that serve to limit the liability of the network owners, raise barriers to entry, and add a modicum of consumer protection.

A key term or art here is “globally unique identifier,” GUI. The social security number is the poster child of a GUI. Leaking a social security number bad for two very discrete reasons. The first is it’s role as a password, but ignore that. The more serious concern is how it is a dependable key that vendors can use to unique identify you. Once a GUI tags your account data the vendor can then trade the data in that account with each other. You licensed them to trade when you assented to their “privacy policy.” I like to joke that they do not lie when they say “your privacy is important to us.” Well yeah, it’s an asset that it is important that they leverage.

GUI come in variations of quality – Social security numbers, email addresses, open ids are all pretty high quality. Cookies are actually pretty good. Google’s Doubleclick cookies can be very high quality. What your are licensing when you leave the Facebook toggle on is tagging you with a high quality GUI owned by Facebook.

A PAIN will have rules that govern the exchange of data between members. And all the usual questions arise. What are the costs, benefits, and risks of membership. Who sets the rules? I think we can assume that Facebook has not bound the members to limit data exchange laterally, i.e. Yelp and Microsoft can traffic in info about you using the facebook GUI as a key. At that point do we care what info Facebook shares with them?

Now, mind you that was all written wearing a care-about-privacy hat. There are other hats!

How about the were-things-are-going hat. It’s obvious that reach, accuracy, and tracking skill of the PAINs is only going to continue to grow. Scenarios long imagined, like enabling the car rental agency to prefill the forms based on your recent airline ticket purchase – a behavior that it pretty trivial to enable, but spooks the user if he hasn’t been carefully preped to comprehend how it happened – are inevitable.

Put on the business-strategy hat; the puzzle is who owns the PAIN that enables the scenarios like, will they make a good landlord, how many such networks will exist, should you try to establish one. The business-tactics hat depend on the answers to those questions. But moving fast maybe necessary or it could be fatal.

Having written that, I think I have a brilliant solution … but putting it here on the end … well it really doesn’t fit.

White light sighted

Many many years ago I read in some high end Optics Society journal about what I came to think of as “the white light.” The article argued that if one extrapolated the patterns in communication there would come a time when the cost of routing information around the network vs. the cost of broadcasting everything everywere would cross and at that point the end points on the net would see everything and just pluck out just the bits intended for them.

Well today I see an early example of just this idea. Here being used to provide optical interconnect for a multiprocessor.

Back in the 70s, when I last worked on multiprocessor interconnects, I sketched out something like this; but the response times on the optical receivers were too slow and the complexity of the rest of the supporting junk was way high.  I wonder if you could hack a modern digital camera’s control electronics along these lines in some fun way.  This kind of thing would be a good project for some MIT 6.111 students.

Oh Canada