Author: erich

For the first time, the Park Avenue Tunnel was open to pedestrians this weekend. Artist Rafael Lozano-Hemmer transformed the Park Avenue Tunnel into an interactive light and sound installation.

I accept the topics I post about can be rather eclectic.  However, I did not see this coming.  Presented without further ado, the top four searches leading readers to the site, according to WordPress:

• transnational corporation network structure
• tiny tiny rss reader api
• number of brand conversation
• 18-24 year old men demographics

I think doulingo is messing with me again.

Kevin Spencer recreated the classic chair at 1:20 scale with a 3D printer.

h/t fubiz

“[T]he most important thing about language is its capacity for generating imagined communities, building in effect particular solidarities.” Benedict Anderson

I’m at Red Hat Summit this week talking about cloud with customers and partners, and it occurs to me one of the common metaphors isn’t quite right. The problem with the “Assembly Line” metaphor is everyone thinks of 1907 Ford (“any color you want, as long as it’s black”). And that’s actually a lousy example.  There was zero flexibility in product output and the only automation beyond individual parts was the well-defined hand-off during assembly. Don’t underestimate the power of those elements, but that’s nothing compared to what we can do today.

The right model is Chevrolet’s model: build knowing the products you need tomorrow are different from the ones you need today.  Build knowing you will change your process while it’s still running. It’s no wonder that once implemented, Chevy beat industry-leader Ford to market by a full year while continuing to serve their current customers and took the lion’s share of the entire car market .

If your cloud isn’t open and changeable, your competitors will out innovate you and take your market.

{ photo from excellent slide show on 100 years of assembly lines at Chevrolet and GM: http://www.assemblymag.com/articles/89625-100-years-of-chevrolet-assembly-lines }

[ update: corrected link to Red Hat Summit keynote streaming ]

I would like to programmatically generate a report using R.  The contents are mostly graphs and tables.  I have a working system, but it’s too many pieces.  When I hand this off to someone else, it become immediately fragile.

Isn’t there a better way? Here are my elements:

• R script: collection of functions to manipulate the data interactively, and with the report
• R script: wrapper to the above functions, and calls knit (from the knitr package) function to generate the report
• R/LaTeX: report template
• bash: script to tie it all together, and clean up leftovers

That’s four languages. Ugly.