EOF - The Last Silos Standing
For the many years I wrote Linux for Suits and the SuitWatch newsletter, I always insisted that Linux and business were joined by and logic rather than or.
I still believe that's true. But, I also believe that many businesses—especially the big ones—still don't get Linux, free software, open source or even the Internet itself. That's because they remain, in the immortal words of Walt Whitman, “demented with the mania of owning things”.
Oddly, the things they want to own most are not things at all, but customers. These companies still harbor the illusion that customers can be “acquired” like slaves and “managed” like cattle. The nicest ranches for customers are politely called “walled gardens”. I prefer an equally agricultural metaphor: silo.
The definition of silo I like best is “a tall cylindrical structure, usually beside a barn, in which fodder is stored”. (That's from the Free Dictionary.) Fodder, in the case of business, is customer data. That data includes specifics, such as name, address, purchase history and call records. It also might include customers' stated or inferred preferences, status with the company (frequent flyer grades, for example) and other variables.
The crowning irony of business silos is that they are built to maximize BI (Business Intelligence), yet they are blind to how they're not working. This form of inward-gazing ignorance is familiar to techies who have watched many silos come down in the computing and networking fields. Mainframes, closed on-line services and proprietary e-mail systems all come to mind. The Internet and its open protocols killed all those things, yet the lessons remain lost on every business that continues to believe that good “intelligence” about what customers actually want can be found inside the company's customer data silo.
For evidence I offer three examples: call centers, loyalty cards and mobile phones. All three are shining examples of a form of architecture that has been discredited, if not defeated, by the successes of Linux, FOSS and the Internet.
Look up “call center hell” in Google, and you'll get millions of results. (This morning, 8.65.) Two of the three top search results on Twitter are by people working in call centers. Most of these are “hold centers”, because putting callers on hold is what they do best. Conversation is not their forté. If you ever reach a human being at the end of a choice maze, you too often interact with a script rather than a human being. After an accident involving my rental car a couple years ago, the woman at the other end of the line reacted to my anger at her uncooperativeness by admitting that her options were limited, literally, by a script. There were only certain things she was allowed to say or hear. When the conversation stepped outside those lines—as it had to, since the accident was novel in several ways—both of us went nonlinear. The call crashed as badly as the four cars (including one cop car) involved in the pile-up.
Loyalty cards are the silliest thing since Green Stamps. By the middle of the last century, nearly every store gave away green stamps, achieving zero differentiation from every other store and adding friction to the entire economy in the process. Today, instead of collecting stamps and sticking them in books (to redeem later for a crappy grill or something), we collect cards that fatten our wallets without making us richer. Loyalty cards require retailers to maintain dual pricing for merchandise and add friction at the checkout counter, where too often the only benefit to the customer is a coupon for something they just bought. Worse, loyalty programs can't tell when or why people don't shop at a store. My family likes to shop at Trader Joe's, because that store avoids the hassles of both loyalty cards and coupons. There is nothing in other stores' loyalty programs that welcomes hearing this useful information.
Perhaps the worst business silos are the Siamese ones formed by cell-phone equipment makers and carriers. Although PCs—even closed ones with Apple and Microsoft operating systems—are open to endless varieties of third-party applications, we see nothing of the sort from the cell-phone business, with the notable exception of the iPhone, which is (as I write this) enjoying its billionth application download. That download, of course, will come from exactly one source: Apple's iTunes. One might consider this a step in the right direction—it's kind of like the one Windows 95 took by making it easy for countless developers to write applications that would run on even-more-countless PCs. The next step, however, has to come from outside the silos of both the equipment makers and the phone system carriers. More eyes make bugs shallower, as we say.
Time to debug some business silos.
Doc Searls is Senior Editor of Linux Journal. He is also a fellow with the Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at UC Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- LiveCode Ltd.'s LiveCode
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide