Saturday, April 20, 2013

Why does the Fujitsu iX500 document scanner need a computer?

For the past decade I've used a typical corporate document scanner. These are the big brothers of the home "MFC" - laser printer, copier, scanner, fax machine. The scanner produces PDF images on an internal hard drive. You can adjust resolution and page size from a control panel, but really all we ever do is scan to 8.5x11 PDF archive resolution.

It's old tech. So why can't I buy a decent document scanner that produces 600DPI 8.5x11 PDFs without an attached computer? In particular, since Fujitsu seems to rule the home document scanning world, why does the ix500 still require an attached computer? This isn't rocket science.

Brother did something like this on a home MFC back in 2009, but I can't find anything on it today.

This is so weird. Is there a patent problem?

It's driving me daft.

See also

Blood donation false-positive HTLV I/II test interpretation. Update - a single case of later onset auto-immune disorder

After decades of blood donation I was rejected in 2010 because of a false positive HTLV I/II test.

I was annoyed, but not too concerned. I forgot about it until I came across old papers today, and a Google search showed that this has been a problem for others. So I'll explain here what I know of this topic, and why I wasn't worried.

This is a bit hard to explain -- even physicians have trouble with testing concepts. One way is by a simplified analogy made for this situation. Suppose you were looking for a killer and you knew they blue eyes and a unique DNA marker that's expensive to test for. Blue eyes would be your imperfect screening test; it has lousy accuracy but it's cheap. Next you test the blue eyed people with the expensive (and perfect) DNA test and you find your killer.

You could test everyone with the perfect "DNA Marker" test, but that would cost a lot of money. So the "blue eye" test is used first to save money.

In my case I tested positive on the cheap ("blue eye) screening test but negative on the good (but expensive) test.

So you'd think I could still donate blood -- but one problem is I may continue to test positive on the inaccurate screening test. That means each time I give blood the expensive test would have to be repeated. That's too much money to spend since we have enough blood donors. (We use far less blood that we used to.)

There are other procedural workarounds, but they all introduce cost and complexity. On the other hand, I'm still a listed bone marrow donor; in that case the economics justify the expensive test.

There's a reasonable discussion in Transfusion 2011 - Human T-lymphotropic virus antibody screening of... [Transfusion. 2011] - PubMed - NCBI. There were 130,000 false positive US donors between 1995 and 2008.

There's a better screening test on the market now so this problem should become less common. Blood centers may eventually decide to reinstate people previously rejected for HTLV positivity and rescreen, but that's probably more trouble than its worth.

If you think about this a bit, there are some other issues to consider. I wasn't much bothered by my false positive test because I'm a physician who works with these topics -- but I bet most of those 130,000 people were quite anxious. Money was spent on follow-up visits with expensive specialists and unnecessary retesting. Some may have had insurance problems. Arguably blood donors should be warned about the risks of false positive testing prior to donation -- so they have informed consent prior to the procedure.

Update 11/26/2015: It helps to have some long term followup on these strange happenings. In retrospect this might have been an early indicator of an auto-immune disorder. Two years later, in 2012, I developed acute inflammation of a distal (near nail) joint of one hand. Five years later (2015) it involved 3 joints and I have sub-patellar arthritis on both knees. In addition to an inflammatory arthritis along the psoriatic-osteoarthritic spectrum I've features of metabolic syndrome despite a low BMI -- including slowly elevating glucose.

My (newly acquired) rheumatologist and I suspect this was a sign I was pumping out lots of antibodies, part of a dysfunctional immune system activation. Though there has also been a relationship between HLTL-1 infection and polyarthritis that doesn't seem to resemble mine, and of course the follow-up testing showed I didn't have the infection.

If someone has a false-positive HTLV-1/II test when donating blood it obviously doesn't mean they are in the early stages of an auto-immune disorder. This is just one odd case. Still, it might be worth a retrospective study.

Thursday, April 18, 2013

The Net is a forest. It has fires.

Whatever RSS (Atom, etc) was intended to be, it became the standard plumbing for subscription and notification. When In Our Time has a new podcast available, Google Reader's use of RSS tells me to get it. When Emily adds a new event to her calendar, RSS lets me know about it.

These are useful tools, but most of all RSS is the plumbing that enables Google Reader to track the hundreds of publishing sources I follow. Some of them publish dozens of stories a day, some publish 2-5 times, a day, and some publish every few weeks. RSS and Google Reader means I can follow them all. Without it the NYT would still be interesting -- I'd just visit it less often. I would give up on those infrequent publishers though, even the ones I love.

Many of those infrequent publishers are "amateur" writers who use blogs. RSS is the democratizing force that put them and the New York Times on an equal footing -- much to the NYT's chagrin. RSS is one of the things that makes blogs work -- esp. the blogs I love.

Since RSS has been pretty important to blogs, and since Google Reader has been the dominant RSS client for years, it's worth seeing what the major blog platforms are saying about the end of Reader

We'll start with Blogger. That's a huge platform, they must have had a lot to say ...

<crickets>

Ok. That's weird. Let's take a look at another biggie - Tumblr, home of 100 million blogs.

<single cricket>

Wow. Spooky. Ok, let's go to the real core. The home of WordPress, the world's dominant professional blogging platform...

<intergalactic space>

As Bond says "Once is happenstance. Twice is coincidence. The third time it's enemy action."

Something is happening. It feels like a fire is coming to the Net. Again.

The first fire I remember was the end of Usenet. Yeah, I know it's technically still running, but it's a faint shadow of the days when I posted about Mosaic for Windows in WinOS2. The Usenet archive nearly vanished when DejaNews failed, but Google rescued it. That was a different Google that the one we know now.

The next fire took out GeoCities. GeoCities was once the third most valuable property on the Net; thirty-eight million web pages died when Yahoo closed it. (Did you know Lycos.com is still around and that it still hosts Tripod? I was shocked.)

Yes, maybe 90% of those pages were junk, but that leaves about 4 million pages of people writing about things they were passionate about. Apple's termination of MobileMe .mac web sharing destroyed a much smaller amount of content, but even now I come across reference to great .Mac content that's gone. Not just moved somewhere else, gone.

The end of GeoCities and .Mac was matched by the end of applications like FrontPage and iWeb. Those apps let geeky amateur's publish to their (web) "hosting" services. Most of that content is lost now -- millions of pages.

No wonder it's hard to find things I read on the net in the 90s. The fires took it all.

Today its feels like the fire is coming again, and once again amateur content will be purged.

I wonder if it will return again.

Sunday, April 14, 2013

I closed my PayPal account. You probably should too.

In the old days I did casual hookups -- of new net accounts and services.

Now, of course, every net identity and related service is a security risk; the hookup era is history. A recent WordPress attack, for example, meant I had to review the security on current and unused WordPress accounts.

The rising cost of account security, including multiple systems for doing two factor authentication, means we all want as few net identities and services as possible, and we want to limit them to companies with good security policies. (Until recently, that didn't include Apple. They're showing signs of improvement.)

So, on general principles alone, it would have been a good idea to get rid of my unused PayPal account. I set it up in 2005 and by November of that year PayPal had earned my lasting distrust. It's weird that I kept it around, even though I did give it an extremely robust and unique password. My only defense is that 2005 was a long time ago.

Truth is, I didn't get around to deleting my old account until I read a Cringely post on how PayPal mismanaged a hacked account of his. It's a litany of fail.

That's when I discovered that my PayPal password, which was something like "I8qRb7yw93OSD4iUHt2b", no longer worked. Evidently my (robust) PayPal password had been quietly reset sometime in the past few years -- either that or my account had been hacked.

PayPal let me do a password reset today based on the original email; the new password came with the usual security-reducing 'secret questions'. Then I had to agree to an electronic notification policy that's probably years old. Finally I was able to close my PayPal account.

If you don't use PayPal routinely, you should close yours too.

Next up: My Amazon commerce account ...

[1] OAUTH is not a cure; it brings different vulnerabilities. Even I'm not very good at reviewing OAUTH access against my various net identities.

Friday, April 12, 2013

Is this AT&T rate change minute expiration a new dirty trick?

We use about 1,000 minutes a month on our AT&T mobile family plan. So our use is halfway between their 700 ($48) and 1,400 minute plans ($64).

To avoid overage fees we do the 1,400 min plan, and we now have 1,200 rollover minutes. So I thought I could drop back to the 700 min plan for a while and use them up.

Not so fast ...

Screen Shot 2013 04 12 at 9 21 59 PM

On the one hand, I hate AT&T. On the other, I kind of respect the purity of their evil. The rollover minutes are pretty useless, but they were probably a competitive advantage once.

So is this minute expiration policy a new dirty trick, or is it one of their old ones?

Wednesday, April 10, 2013

Buying a used road bike (Mineapolis St Paul example).

When I published my 'touring bike' page in 1997 I'd just bought a new 1996 Cannondale touring bike for $600. I've made many upgrades over the past 16 years, but it's been a very decent bike.

These days similar bikes seem to start at $1000. I can find good value mountain bikes or cross-bikes for my relatively short #1 son, but road bikes of any kinds are an elite product these days. So I'm looking at used bikes, which aren't cheap either. (Not surprising, given the cost of a new bike.)

Finding a used bike is a bit tricky. There are too many stolen bikes on Craigslist for me to be happy there, and searching Craigslist for a small frame bike is a pain anyway [1]. Fortunately a friend of mine is a passionate lover of old bikes, and she was happy to pass on on some advice. It's Minneapolis - St Paul specific of course: 

  • The Bike Hub Coop has a wide range of used bikes, but many are high priced consignment or high class refurbs, so the average price is $300+. In June they have a "used bike extravaganza" -- a good time to hunt for a small frame bike.
  • One on one bicycle studio (Minneapolis warehouse district) - they'll watch for a small frame if asked
  • Cycles for Change is near my St Paul home. They had a slightly big bike for the right price, but it had been refurbed with a wide cartridge modern wheel and the chain rubbed on the frame.
  • Mr Micheals Reycles Bicycles: web site isn't worth much but I think as of 2022 they are still around.

I think prices will be around $250-$400. In some shops the bikes are assembled by trainees -- which is part of the mission. They aren't necessarily bike experts though, so you need to inspect mechanicals.

For now #1 is riding my wife's 1984 Nishiki -- a fine and tough old steel bike. She's fond of it but happy to let him try it out, gives me time to test him out and find a used one. (Emily is loathe to part with old gear, so she's not interested in replacing the Nishiki with a $$$ carbon frame thingie.

[1] An app.net comrade suggested pawn shops, but that seemed a bit hit or miss. I think in these parts bike shops that specialize in used bikes are the best bet.

PS. A post with a picture of my 1976 Raleigh International; I think it was $450 then. In those days that was a high end bike, the equivalent of a $2,000 bike today. (Since that picture I did make one concession - I put Shimano mountain bike clips on it.)

Thursday, April 04, 2013

Roger Ebert and Iain (M) Banks

Two days ago I learned that Iain (M) Banks, one of my favorite writers, had months to live. He should have had decades. He announced he was marrying his partner.

The same day I read a blog post by Roger Ebert. He announced that a recent fracture was "pathologic" -- meaning related to a cancer recurrence and his new plans...
A Leave of Presence - Roger Ebert's Journal 
... I am re-launching the new and improved Rogerebert.com and taking ownership of the site under a separate entity, Ebert Digital, run by me, my beloved wife, Chaz, and our brilliant friend, Josh Golden of Table XI. Stepping away from the day-to-day grind will enable me to continue as a film critic for the Chicago Sun-Times, and roll out other projects under the Ebert brand in the coming year...
I assumed, reading it, that he was preparing, as quickly as possible, for the end. That came today. I will miss his wisdom and compassion.

Monday, April 01, 2013

Google Field Trip -- Scooba Mississippi

My gypsy wife sent us on a 12 state 9 day road trip from the frozen north to Florida's "Emerald Coast" and back to the still frozen North.

This was less painful than you might think; we kind of like road trips. iPhones help, but so does a cheap old two panel auto DVD player and our patented movie selection method -- parent chooses four, each child removes one until one DVD remains.

This time we tried out Google Field Trip for iOS. I won't trust my data to Google products like the comically named "Keep", but I'm relatively good with this kind of ad-supported product [1]. Leonard has a good review up on Salon, with his take on the coverage problem we also ran into ...

App of the Week - Salon.com

... it’s not clear how in-depth Field Trip’s coverage is across the entire U.S. I used the integrated Google Maps feature to peer into some other regions I know pretty well and received widely varying results. I took a look at downtown Gainesville, Fla., and found a wealth of interesting historical information, but very little in the way of restaurant or bar recommendations. I zoomed in on Peterborough, N.H., and found zero recommendations of any kind. I checked out my father’s old neighborhood in the Upper East Side of Manhattan, and discovered much less than one would expect of one of the most densely packed regions of the world...

We had pretty good coverage of local history in parts of Illinois, but then less in Indiana and almost nothing in Kentucky. Most of the interesting alerts came from Google's use of the volunteer led Historical Marker Database; its coverage may depend on where volunteers live. I'm hoping Google will support some expansion as part of their routine Street View maintenance.

We're a long way from getting road trip history on a place like Scooba Mississippi. From the name and look of the old main street, called Railroad St, Scooba was a railroad town that died with passenger rail:

Screen Shot 2013 04 01 at 8 56 12 PM
(image from Google Street View)

Now it's the home of East Mississippi Community College - which was likewise empty on our Good Friday drive by. Empty except for two police cars with closed gates on every entrance road but one. (The web pages appear to have been last revised in early 2012, but the campus is still in business. I think.)

Google Field trip was silent on Scooba. I'd like to know what it was like when times were good, and I'd like to know why students go to EMCC and what happens to them after they leave.

[1] Relatively good, there's still the Google predatory pricing problem. "Free" (ad supported) aps like this push better alternatives out of the market.

Saturday, March 23, 2013

Schneier: Security, technology, and why global warming isn't a real problem

In the Fever Days after September 2011, I wrote a bit about "the cost of havoc". The premise was that technology was consistently reducing the cost of havoc, but the cost of prevention was falling less quickly.

I still have my writing, but most of it is offline - esp. prior to 2004. As I said, those were the times of fever; back then we saw few alternatives to a surveillance society. Imagine that.

Ok, so that part did happen. On the other hand, we don't have Chinese home bioweapon labs yet. Other than ubiquitous surveillance, 2013 is more like 2004 than I'd expected.

The falling cost of offense/cost of defense ratio remains though. Today it's Schneier's turn to write about it… (emphases mine)

Schneier on Security: When Technology Overtakes Security

A core, not side, effect of technology is its ability to magnify power and multiply force -- for both attackers and defenders….

.. The problem is that it's not balanced: Attackers generally benefit from new security technologies before defenders do. They have a first-mover advantage. They're more nimble and adaptable than defensive institutions like police forces. They're not limited by bureaucracy, laws, or ethics. They can evolve faster. And entropy is on their side -- it's easier to destroy something than it is to prevent, defend against, or recover from that destruction.

For the most part, though, society still wins. The bad guys simply can't do enough damage to destroy the underlying social system. The question for us is: can society still maintain security as technology becomes more advanced?

I don't think it can.

Because the damage attackers can cause becomes greater as technology becomes more powerful. Guns become more harmful, explosions become bigger, malware becomes more pernicious...and so on. A single attacker, or small group of attackers, can cause more destruction than ever before...

.. Traditional security largely works "after the fact"… When that isn't enough, we resort to "before-the-fact" security measures. These come in two basic varieties: general surveillance of people in an effort to stop them before they do damage, and specific interdictions in an effort to stop people from using those technologies to do damage.

Lots of technologies are already restricted: entire classes of drugs, entire classes of munitions, explosive materials, biological agents. There are age restrictions on vehicles and training restrictions on complex systems like aircraft. We're already almost entirely living in a surveillance state, though we don't realize it or won't admit it to ourselves. This will only get worse as technology advances… today's Ph.D. theses are tomorrow's high-school science-fair projects.

Increasingly, broad prohibitions on technologies, constant ubiquitous surveillance, and Minority Report-like preemptive security will become the norm..

… sooner or later, the technology will exist for a hobbyist to explode a nuclear weapon, print a lethal virus from a bio-printer, or turn our electronic infrastructure into a vehicle for large-scale murder...

… If security won't work in the end, what is the solution?

Resilience -- building systems able to survive unexpected and devastating attacks -- is the best answer we have right now. We need to recognize that large-scale attacks will happen, that society can survive more than we give it credit for, and that we can design systems to survive these sorts of attacks. Calling terrorism an existential threat is ridiculous in a country where more people die each month in car crashes than died in the 9/11 terrorist attacks.

If the U.S. can survive the destruction of an entire city -- witness New Orleans after Hurricane Katrina or even New York after Sandy -- we need to start acting like it, and planning for it. Still, it's hard to see how resilience buys us anything but additional time. Technology will continue to advance, and right now we don't know how to adapt any defenses -- including resilience -- fast enough.

We need a more flexible and rationally reactive approach to these problems and new regimes of trust for our information-interconnected world. We're going to have to figure this out if we want to survive, and I'm not sure how many decades we have left.

Here's shorter Schneier, which is an awful lot like what I wrote in 2001 (and many others wrote in classified reports):

  • Stage 1: Universal surveillance, polite police state, restricted technologies. We've done this.
  • Stage 2: Resilience -- grow accustomed to losing cities. We're  not (cough) quite there yet.
  • Stage 3: Resilience fails, we go to plan C. (Caves?)

Or even shorter Schneier

  • Don't worry about global warming.

Grim stuff, but I'll try for a bit of hope. Many of the people who put together nuclear weapons assumed we'd have had a history ending nuclear war by now. We've had several extremely close calls (not secret, but not widely known), but we're still around. I don't understand how we've made it this far, but maybe whatever got us from 1945 to 2013 will get us to 2081.

Another bright side -- we don't need to worry about sentient AIs. We're going to destroy ourselves anyway, so they probably won't do much worse.

Thursday, March 21, 2013

Fermi Paradox: The solution set is stable


Any discussion of the Fermi Paradox has to be presented with a wink and a chuckle. Even if, behind the wink, there's a haunted look in the eyes.

Today's io9 version is no exception, but it contains two of my personal faves (wink, chuckle, give me a drink) ....
11 of the Weirdest Solutions to the Fermi Paradox 
...5. The Simulation Hypothesis 
...We haven’t been visited by anyone because we’re living inside a computer simulation — and the simulation isn’t generating any extraterrestrial companions for us.
If true, this could imply one of three things. First, the bastards — I mean Gods — running the simulation have rigged it such that we’re the only civilization in the entire Galaxy (or even the Universe)...
... the simulation is being run by a posthuman civilization in search of an answer to the Fermi Paradox, or some other scientific question. Maybe, in an attempt to entertain various hypotheses (perhaps even preemptively in consideration of some proposed action), they’re running a billion different ancestor simulations to determine how many of them produce spacefaring civilizations, or even post-Singularity stage civilizations like themselves... 
... 7. All Aliens Are Homebodies 
... An advanced ETI, upon graduating to a Kardashev II scale civilization, could lose all galactic-scale ambitions. Once a Dyson sphere or Matrioshka Brain is set up, an alien civilization would have more action and adventure in its local area than it knows what to do with. Massive supercomputers would be able to simulate universes within universes, and lifetimes within lifetimes — and at speeds and variations far removed from what’s exhibited in the tired old analog world. By comparison, the rest of the galaxy would seem like a boring and desolate place. Space could very much be in the rear view mirror...
The list omits the Theist Hypothesis -- that God(s) created Man to be Alone. This is, of course, simply a variant of the Simulation Hyopthesis.

I reinvented the Homebody Theory around 2000, but I later learned it goes back decades. The basic idea is that every civilization either dies or goes 'singular', and post-singular they are invariable disinterested in childish pursuits like interstellar travel.

The 'Phase Transition Hypothesis' doesn't really belong on the list; it's really just a term in the Drake Equation (technological life has been rare, etc).

The io9 post is a nice reference even if there's nothing new in the list; the set has been stable for at least seven years.

See also:

Sunday, March 17, 2013

Device size: clothing makes the choice

An App.net thread reminded me of some analysis I did in the 90s on what device sizes we should build our Cloud ASP service against. That analysis focused on pockets and purses; it came in an era when men still had shirt pockets and Jeff Hawkins carried around wooden models of the Pilot until he settled on one that fit his.

Since that time our devices have evolved a bit -- thought not as much as many think. We had slates in the 90s too -- they were just heavy and ran Windows variants or Windows thin client OS. Our clothing may have changed more [3]. Shirt pockets are gone, suit jackets are less common, and pants pockets are larger. Pocket location may also have shifted as men have gotten fatter around the world. (I don't know what's popular in China).

This produces some interesting size options based on clothing. Here's my own personal list of exemplar devices for each transport option with a gender assignment based on typical American practice.

GenderClothingDevice
b None [1] watch
m Traditional pants front pocket iPhone 5S
m Expansive pant front pocket Samsung Galaxy [2]
f Purse Samsung Galaxy
f Purse iPad Mini
b Backpack / shoulder bag iPad Mini
b Backpack / shoulder bag MacBook Air 11"
b Briefcase iPad (full) + Logitech Kb/Case
b Briefcase MacBook Air 13"

Running through the list, and disregarding whether one wants a phone or not, device options are probably best determined by one's clothing habits. The list also suggests the women should disproportionately prefer the Samsung Galaxy to the iPhone but that men should split 50/50 -- so the Samsung Galaxy should outsell the iPhone 5 about 1.5:1.

If the iPad Mini provided voice services the list predicts the combination of iPhone 5 and iPad Mini(v) would equal or exceed Samsung Galaxy sales.

This analysis suggests a narrow niche for the 11" Air. I have one and I like it, but if I were buying an Air today I'd get the 13". If I'm carrying a briefcase I might as well get the 13" Air or an iPad with Logitech Kb/Case. The 13" Air vs. iPad tradeoff is an interesting one -- for many travel cases I think the iPad wins on power and bandwidth consumption -- but see the comments -- Charlie Sross and Martin Steiger disagree. I can imagine a future version of OS X and OS X hardware with iPad like power and bandwidth use -- in which case I'd go Air.

[1] Swimsuit, running gear, nudist colony.
[2] I haven't seen mention of this, but my understanding is that Android handles variant screen geometry more easily than iOS. 
[3] Our devices must be influencing our clothing styles by now.

Saturday, March 16, 2013

Project Ducky - why I've stopped using new Cloud services.

Dilbert 04/14/1994:

Screen Shot 2013 03 16 at 3 39 53 PM

Yeah, Google Reader is on many geek minds today, but it's not the only cloud death to disrupt my routine.  Today, working in Aperture, I tried searching on a AppleScript workaround for Aperture's single-window mangled Project problems. I found a couple of good references -- to Apple .Mac pages that died with MobileMe. The page owners never recreated their lost resources.

Later I wanted to upload some photos from our special hockey team. I remembered then that Google discontinued Mac/Picasa integration and the iPhoto Plug-in.

Within a year I expect Google is going to discontinue Blogger, which currently hosts this blog.

Enough.

I'm on strike. You want my business? Give me standards. Give me products I pay for that have low exit costs and that have competitors. 

Oh, yeah, Google - go away.

See also:

Thursday, March 14, 2013

Google's war on standards: RSS, ActiveSync, now CalDAV

I remember when Google seemed to be somewhat friendly to standards and to the idea of open interchange.

That was, of course, Google 1.0. Now we live with Google 2.0.

With the neglect of Blogger, the end of Google Reader, and the RSS-free launch of G+, Google has put a stake in the RSS/Atom subscription standard. (Google played a big role in the development of Atom, when most of us write of "RSS" we mean "RSS/Atom".)

Recently Google limited support for ActiveSync, a de facto standard based on Microsoft Exchange technologies.

Now Clark reminds me that they've also ended CalDAV support, which I use to view my Google Calendars on my 11" Air:

Official Blog: A second spring of cleaning

... CalDAV API will become available for whitelisted developers, and will be shut down for other developers on September 16, 2013. Most developers’ use cases are handled well by Google Calendar API, which we recommend using instead. If you’re a developer and the Calendar API won’t work for you, please fill out this form to tell us about your use case and request access to whitelisted-only CalDAV API...

I'm glad I never committed to Android. I'm deeply enmeshed in the Google ecosystem, but it is time I started digging out.

Quick thoughts on the end of Google Reader

Of all the things Google has killed, I used Reader most of all.

I'm sad to see it go, but, unlike the end of Reader Social, I'm not angry. I'm just surprised Reader lasted as long as it did.

Reader feels now like something from a mythical Golden Age. Free, but with minimal and non-intrusive advertising -- particularly when used with Reeder.app and Readability. Standards based (OPML, RSS/Atom), and so open in a way that few things are in our locked-in locked-down era.

So Reader's end was expected -- and this time Google did things well. Unlike when they killed the 'sharebro' community, Google telegraphed this one. Even now we've got three months to switch -- much longer than I expected. 

It will be interesting to see what our options will be; the end of Reader will open up a new ecosystem. An ecosystem that will, I hope, include services we buy. There is at least one upside -- I'm losing one of my big Google dependencies. It's getting easier for me to swich away from Google.

Incidentally, I bet Blogger will die in 2014.

Saturday, March 09, 2013

Strange loops - five years of wondering why our corporate units couldn't cooperate.

Five years ago I tried to figure out why we couldn't share work across our corporate units.

This turned out to be one of those rabbit hole questions. The more I looked, the stranger it got. I knew there was prior work on the question -- but I didn't know the magic words Google needed. Eventually I reinvented enough economic theory to connect my simple question to Coase's 1937 (!) theorem1970s work on 'the theory of the firm', Brad DeLong's 1997 writings on The Corporation as a Command Economy [1], and Akerloff's 'information assymetry'. [2]

Among other things I realized that modern corporations are best thought of as feudal command economies whose strength comes more from their combat capacity and ability to purchase legislators and shape their ecosystems than from goods made or services delivered.

Think of the Soviet Union in 1975.

All of which is, I hope, an interesting review -- but why did I title this 'Strange loop'?

Because I used that term in a 2008 post on how Google search, and especially their (then novel) customized search results, was changing how I thought and wrote. This five year recursive dialog is itself a product of that cognitive extension function.

But that's not the only strange loop aspect.

I started this blog post because today I rediscovered DeLong's 2007 paper [1] as a scanned document. I decided to write about it, so I searched on a key phrase looking for a text version. That search, probably customized to my Gordon-identity [3], returned a post I wrote in 2008. [4]

That's just weird.

 - fn -

[1] Oddly the full text paper is no longer available from Brad's site, but a decent scan is still around.

[2] There are at least two Nobel prizes in Economics in that list, so it's nice to know I was pursuing a fertile topic, albeit decades late.

[3] John Gordon is a pseudonym; Gordon is my middle name.

[4] On the one hand it would be nice if I'd remembered I wrote it. On the other hand I've written well over 10,000 blog posts. 

See also: