• ERP, HRP at Collabera and Sutherland

    Modern ERP systems have brought the automation and efficiency of turning raw materials into finished products to a high art. When will the equivalent systems for finding, selecting and deploying human resources become widespread? When will we have "HRP" (Human Resource Planning) systems that are up to the level of modern ERP? The Oak company Collabera has such a system which is more advanced, automated and efficient than anything I have seen or even heard about. When I learned about it, I was glad, but also wondered why they had to create their own, why everyone doesn't demand such a system?

    Is There an HRP Problem?

    Yes. All you have to do is think about people as though they were raw materials to be sourced for a factory, and ask basic questions like: what are our basic systems for sourcing the raw material (people) we need? How do we distinguish good sources from poor ones? When we encounter a batch of new material (a candidate), what are our systems to assure the material meets our standards and will perform? What steps do we take to turn the raw material we acquire into finished goods (an effective, trained, reliable employee)?

    Putting metaphors aside, I have personally been involved in the chaotic process of identifying, selecting  and hiring people with programming and software management skills for years, and the process has remained catch-as-catch-can for decades!

    In most places, the HR people somehow identify candidates essentially using keyword match methods that focus on the most incidental aspects of programming, like what language you've used most recently. If you were burned even more than usual with your most recent hire, you may bump up the experience and/or degree requirements, but that's about it. Then you may do phone interviews and in-person interviews, but those often amount to little more than verbal resume recitations and get-to-know-you chats. Some big companies like Google think they're being smart by giving people trick puzzles to solve, but those tend to be jokes.

    I remember on my very first job out of college, I quickly ended up interviewing all programming candidates because somehow my boss had decided I was a good interviewer. I have no idea why — I was just winging it — but then so was he, and at least I wrote up notes!

    So I would say, yes, there is a major HRP "opportunity."

    Why Isn't HRP Ubiquitous?

    I've often wondered about this. I think the answer is related to other long-standing mysteries like why does the software in certain industries (like health care) severely lag behind software in other industries? I think (pure speculation here) that the answer has to do with the degree of technical focus (i.e. nerdiness) of the management, and how "hard" (quantitative) the success measures are. For example, medicine is all about people and there are loads of tough-to-quantify aspects of their health, while manufacturing is all about making things, and nearly everything about it is easily measured. So software and automation has a hard time making headway in medicine, while it's table stakes in manufacturing.

    Who is ultimately in charge of hiring people? Mostly, it's highly people-oriented HR types, and their business is even harder to quantify than medicine. You might think that when hiring programmers, getting interviewed by other programmers would be a great selection method, but particularly in large companies, it tends to be terrible! What else would you expect when non-people-oriented programmers are asked to perform this highly inter-personal task for which they have little talent and no training??

    Everyone knows that interviewing programmers is tough, that only programmers are qualified to do it, and they're simply terrible at it.

    Job-interview-cartoon

    What can be done about HRP?

    I first realized that there were ways to make the hiring process better when I saw it actually done at a couple of Indian outsourcing companies. I noticed something was different when I attended a meeting and they would trot out the most important, prestigious person on their executive team: the head of HR! It didn't take long for the reality to sink in. As an outsourcing company, your main job is hiring and managing people better than the company you're outsourcing for. The whole reason outsourcing exists is that the client company does a terrible job finding, selecting, training and managing their people, particularly in IT and customer service. The outsourcing company has to do a better job, or the client company might as well in-source! Being real good at HR is life or death at an outsourcing company, so they tend to focus on it and apply systematic methods and automation.

    Another Oak company, Sutherland Global Services, provides a great example of how an outsourcer can be better than its client at performing essential business functions (in their case customer service and various forms of BPO) through superior methods, HRP and automation. Among other things, these methods enable them to be truly "global" as their name says, for example shifting the mix of work among various locations including the US, Canada, the Philippines and India without wrenching dislocations.

    Conclusion

    In field after field, everyone is convinced that a certain job can only be done by a highly skilled human, a craftsman, an artist, a professional. There is outrage when automation is introduced. There are riots, and machines are destroyed. Eventually, however, the automation is so successful that is replaces or greatly aids the human.

    Why shouldn't the process of selecting, training, placing and managing humans in those positions that (at least for now) require humans be subject to the same transformation? Not only can it be done — it is being done. The startling growth and success of Sutherland illustrates the practical impact of applying system and automation to human resources, and demonstrates that it can be done all over the globe.  Collabera uses its innovative and effective HRP methods to hire people who often work alongside and intermingle with "regular" employees of Fortune 500 companies; their methods make such a difference that their clients keep coming back for more, as shown by their admirable growth rate.

    Everyone involved in hiring knows it can be done better. It's only a matter of time before human resource automation becomes a widespread practice.

  • The Xiotech ISE and Technology Fashion

    We all know what fashion is. Think of Vogue Magazine, or impossibly tall, thin women walking in that special way down the elevated runway, wearing something no normal person would be able to wear, or would want to wear if they could.

    SAIC_Fashion_Show_2008 But fashion extends way beyond women's clothing. Let's start with men's clothing: how many guys wear suits and ties to the office today? Then cars — how many modern cars have those giant fins that were popular in the '60's?  The kind of popular music you like dates you at least as much as wrinkles on your skin. The more you think about it, the more you realize how pervasive fashion is.

    Fins_close_up

    "Technology is a counter-example," perhaps you say. "It's bits and bytes and silicon, no fashion there!" Well, that's true, except that it's people who buy the technology, and people are fashion-driven creatures. Let's face it: the cool kids who once drove sporty cars now pull out their iPhones at the slightest excuse. Waiting on line to see the Beatles; waiting on line to get the latest iPhone — what's the difference? They're both fashion-driven fads.

    Iphone3g_line_2

    "I concede that consumer technology is fashion-driven," perhaps you admit. "But hard-core computing technology, where nerds are building things for nerds; how can that possibly be driven by fashion?" I fully concur that no nerd techie would ever admit that his choices, selections and designs are driven by fashion, not even to himself. But all too often, that's exactly what's happening. The techie nerd who comes up with a design approach for solving a problem almost always prides himself on originality and foresight, without any awareness of how fashion-determined his most important decisions are. These decisions are often not made consciously; they are assumptions. "It's not worth discussing, of course we'll take approach X," the techie would respond in the unlikely event that the assumption is questioned — by some "ignorant" (which is tech-talk for "unfashionable") person. Just to be clear: we're not talking about how nerds dress; we're talking about how nerds think.

    Gisele_nerd

    There are examples in every field of computing technology. The Java/J2EE fad during and after the internet bubble is an obvious example, and before it client/server computing was a huge fad.

    There is a clear example in storage technology today. The fashion is as clear and obvious as short skirts, and moreover is explicitly stated by its adherents: the fashion is that storage functionality should be provided as a body of software, independent of any hardware embodiment, and without regard to any particular storage hardware. Companies that previously sold storage hardware no longer have real hardware design functions — all they do is bundle their software with hardware provided by others and sell the combination. The most popular form of this approach is to buy drive bays from an OEM and connect them to controllers consisting of off-the-shelf specially configured processors; 3Par and many others do this, for example. IBM's xiv implements a variation on this theme, using all IBM commodity server hardware. While there are still loads of dollars being spent on old-style, hardware-centric storage systems (think EMC), engineers building new storage systems are uniformly following the software-centric fashion.

    In this sense, the Xiotech ISE is decided unfashionable. The ISE was invented at Seagate, in response to the CEO, Steve Luczo, wanting to create a storage product that was higher value than spinning magnetic disk drives. The idea was simple: build a fixed-format super-disk, with many Seagate drives, intelligence, etc. It would be bigger than a disk, but smaller than a SAN. It would emphasize basic storage functions (write, protect, read) and leave the "high level" storage functions to the SAN vendors.

    What is interesting is that Steve Sicola and a group of other storage industry veterans ended up working side-by-side with Seagate engineers, something they never would have done at a SAN vendor. Sicola and his team knew the evolving fashions in storage quite well: ignore the details of the drives, that's "just storage." Build fancy high-level functions.

    But since they were stuck with the drive engineers, they did something unusual: they actually listened to them! They learned about the amazing functions the engineers embedded in the drives that all the SAN vendors ignore. They learned how annoyed the Seagate engineers were at all the drives marked "bad" by SAN's, the vast majority of which are actually good; they learned about error codes and performance details that all the other storage engineers in the industry were studiously ignoring.

    Before long, they got absorbed in what you could really do once you really knew the hardware. And, being good nerds, they invented a bunch of stuff, like how to virtualize over a fixed number of heads so that top performance was maintained even when the disks are filled up. They also invented a bunch of stuff that provides major, persisting advantages as new drives with higher capacities come out.

    Since I know a fair amount about Xiotech's ISE, I want to go on and on about it. But I won't, because the point of this post is technology fashion. The purpose of bringing up the ISE is that it's a great illustration of the power of fads and fashion in technology. Any normal group of self-respecting storage nerds would have built a completely hardware-independent storage system. As such, it may have had nice features, but it would be pretty much like all the others in terms of its basic functions of reading and writing disks. But because these storage engineers were sequestered with hardware types and had a unique mission imposed from above, they did something very rare: they built a leading-edge storage system that is decidedly unfashionable. Because the engineers actually paid attention to the hardware, the ISE does things (performance, reliability, density, scalability, energy use, etc.) that no other storage system on the market today does, even though it uses the same disks available to others.

    Fashion is, of course, a relative term. Fashion is one thing at diplomatic receptions, and quite another hiking in the wilderness or in a war zone. What is appropriate for one doesn't work for the other. Shoes that are appropriate for a salon can cripple you in the woods.

    Well, it turns out that the modern storage fashion of ignoring the storage hardware may be acceptable in salon-type environments (where appearance and style is important but there's no heavy lifting to be done), but is as crippling as high heels in the I/O-intensive environments that are increasingly found in virtualized, cloud data centers. The ISE is like storage fashion for war zones of data, for data-intensive applications like virtualized servers, where the applications are concentrated in a small number of servers, all fighting to get their data. Most storage systems know how to hold their tea cups and conduct refined discussions and other things that matter when getting your data sometime today would be nice, thanks.

    A-Tea-Party

    But when you've got a crowd of rowdy, tense applications all of whom are demanding their data NOW, perhaps more of a war-time style is appropriate; that's what the "unfashionable" nerds at Xiotech created in the ISE.

    An-Angry-Crowd-Giclee-Print-C12371290.jpeg

  • E-Commerce and E-Media

    When are e-media companies going to start honoring the "e" in "e-media?" When are they going to start acting like e-commerce companies?

    E-commerce and e-media

    Everyone knows what e-commerce is. You can look it up on Wikipedia, where there's a major series of articles on the subject. Simply put, it's the electronic version of retailing, a.k.a. e-tail (which redirects to e-commerce on Wikipedia).

    You might think that the same thing would happen to media. But we know it's not so! They are so different that "e-media" doesn't mean much — e-media doesn't even have an entry in Wikipedia! How pathetic is that?!

    So what is E-media?

    If "e-media" means anything at all, it's got to mean the electronic, on-line version of media. So if plain old media includes, for example, the New York Times, then e-media has got to be the electronic, on-line version of a newspaper. Right?

    Yes, of course that's right. There are lots of on-line news sites, and they're mostly the on-line editions of print or broadcast media. If you know what to expect from the paper or the broadcast, you can get something similar at a website, with a few enhancements such as frequent updating. And that's exactly what's wrong with e-media!

    Putting the "E" in E-commerce

    You would have thought (as many did at the beginning) that being a big, resourceful, successful retail company would give you a huge advantage on the web compared to a bunch of nerdy computer types who, when you glance at them, don't make you think "good at customer service." You would have thought that e-commerce would be dominated by names like K-Mart, Sears and Walmart. Of course, it didn't happen. All the fancy executives at the brick-and-mortar giants were certain they would crush the nerdy wanna-be's. All the fancy executives at the brick-and-mortar giants were wrong. Dead wrong.

    Let's look at some of the most obvious things that distinguish e-commerce from its bricks-and-mortar forebears:

    • Web-centric leadership. This might be the most important factor. Jeff Bezos of Amazon is the poster child for this point.
    • Web-centric approach. This is a tough one. When you look at the web from the perspective of long experience in retail, you can't help but seeing the commonalities; after all, in both cases you've got real people coming to a "place," viewing goods and deciding whether to buy them. In their essentials, they're mostly the same, aren't they? This is exactly backwards. Succeeding on the web depends on seeing what's unique about the web and how to exploit it to advantage. Think for example about how Amazon knows it's you and presents you with things you might like, and tells you in real time how other people decided among the alternatives you're considering, lets you read what other people think, etc. Going "native" works.
    • Technology embracing. Sure, retail companies use technology. Walmart is famous for their data warehouse, for example. But Walmart didn't invent anything — they amazed the world and flustered their competitors simply by using state-of-the-art data warehouse technology. By contrast, the leading e-commerce companies not only use the latest technology, they advance it and invent new technology. Sometimes they do such a good job, they even sell their technology to other companies (again, Amazon is a case in point here). Retail companies may use technology, but e-commerce companies are immersed in it and create their own.
    • Driven by Data. Again, Walmart is well-known for collecting and using data to retail advantage. They do it by product and by aisle. But the consumer has already made their most important decision simply by driving to the store. On the web, "driving" to another store is a matter of a couple clicks. The level of competition this results in is unheard-of in the world of bricks-and-mortar. In the e-commerce world, you can track everything, second by second and click by click, and the successful people do exactly that. They test, track, measure, modify and repeat.

    Putting the "E" in E-media

    It's pretty clear that today, we're just at the beginning of creating a true e-media. The way these things usually work, they will follow much (not all) of the path taken by the e-commerce folks. Here are a couple of the key points:

    • Web-centric leadership. This is a tough point for most successful old-media executives to accept. But the burden of proof is on them: why is it exactly that they will succeed when all their brick-and-mortar fellows failed miserably?
    • Web-centric approach. When you look at the web from the perspective of long experience in print (for example), you can't help but seeing the commonalities, and focusing on characteristics shared by print and web. After all, aren't you in both cases presenting a visual lay-out of words, graphics and pictures? Aren't headlines important? In both cases, it's real people consuming the product, and their reactions are the same, aren't they? This is exactly backwards. Succeeding on the web depends on seeing what's unique about the web and how to exploit it to advantage. I'm not going to spell out exactly how this can be done, because it's at the heart of e-media winning on the web. But the principle is clear: Going "native" works.
    • Technology embracing. In the print world, printing presses are somewhere "else," and no one important invents anything technological. When editing and typesetting went digital, the media industry certainly went along. But they didn't invent it — they just bought and used it. By contrast, the leading e-media companies not only use the latest technology, they advance it and invent new technology. The programmers aren't just functionaries beneath the notice of the "important" people in the company — they are essential engines of innovation, and a good part of the success of the enterprise depends on their work. Media companies may use technology, but e-media companies are immersed in it and create their own.
    • Driven by Data. You've got some data in the print world, but it's kind of pathetic in web terms. You put out a paper that has international, national and local news; sports; arts and entertainment; ads of all kinds, including classifieds; and other things — and you have no idea who is spending how much time reading which part of the paper or how they're responding! It's like running a department store and being able to see how many people come and go, but not which sections of the store they visit or what they buy! Talk about flying blind… In the e-media world, you can track everything, and the successful organizations will do exactly that. They will test, track, measure, modify and repeat. 

    No one knows how e-media will evolve. But the best companies (some of them Oak investments such as Demand Media, Federated Media and Huffington Post) are already marching down the road I've just described. While it's clear there's a ways to go, the leading companies following these principles are increasing their leads from the pack.

     

  • Healthcare: Higher Quality, Lower Costs: Candescent Health

    There has been a lot of talk about how to pay for health care. At the same time, everyone wants the best quality care they can get. We all know that in practically every area of life, in order to get higher quality, you have to pay more. A better house? More money. A better car? More money. Better food? More money. How will we ever get out of the spiral of ever-increasing, ever-more-unaffordable health care costs? Everyone knows (empty promises from politicians notwithstanding) that we are marching down the road towards higher costs for lower quality health care.

    Several companies in which Oak Investment Partners has invested in are pulling off the impossible, that is, lowering costs and raising quality. None of them involve magic. All of them make common sense. But they're new! The overall common theme is simple: understand the process, give consumers real, informed choice, and above all: use technology to automate the process. Here's one of them.

    Candescent Health

    Candescent Health is taking a well-understood, necessary, highly-valued medical service (medical imaging), and applying methods that have been used with great success for years in call centers and back office automation. The methods are proven and widely deployed. They lower costs while improving quality, often dramatically. The only surprising thing is that it has taken so long to apply the methods in medical imaging; but that's a potential subject for another time!

    The core method is usually called workflow. It is widely applied in factories, document processing, and nearly any setting in which there are repetitive units of work. The key elements include:

    • Digital unit of work. The foundation of modern workflow is a digital unit of work. This means the unit of work is like an e-mail, only with structure and controls. It contains the image, everything about it and everything that's been done to it.
    • Central work distribution. There is a central location that "sees" (like an e-mail server) every piece of work coming in, every doctor who is working or ready for work, and the deadlines.
    • Intelligent routing. It's important that the central work distribution makes intelligent decisions about which piece of work to give to whom. In a call center, this means you talk to someone who is qualified to handle your issue. For medical imaging, it means that the right specialist (for example, someone who only does shoulders!) handles your case.
    • Specialized processors. A Swiss Army Knife is great, but for any given task, a real screwdriver, etc. is better. In the same way, someone who specializes in a kind of work produces superior results more quickly than a generalist. This is the key to better quality.
    • Process automation. Once the right person gets the right piece of work, making that person as efficient as possible makes the person happier and more efficient. Every keystroke and mouse click that can possibly be eliminated is eliminated.
    • Standardized output. Of course there are standard reports. But there should also be standard lexicons, and the same information should always be provided, regardless of who does the work. It's called "interchangeable parts." When this concept was introduced to manufacturing in the early 1800's, it led to an explosion of economic benefits. Now, in the early 2000's, we're applying it to medical imaging!
    • Continuous improvement. Anyone who has worked seriously with workflow knows that the system can always be improved. Building in a process of continuous improvement helps maintain quality and make things better.

    These are the elements of success for Candescent Health. I've just described their innermost secrets! But the key is that Candescent Health is actually delivering what I've described, and everyone involved (patient, referring doctor, specialist and hospital) is better off as a result. Everyone wins. Makes me smile.

  • From Start-up to Real Success

    Start-ups are exciting. There are passionate people in hot pursuit of a new, under-appreciated opportunity. There is the uncertainty of success and long odds, along with a compelling vision and the thought that this could really happen!

    Start-ups find themselves snaking their way through dense thickets and up narrow paths, perilously clinging to the edge of steep hills. There are obstacles and dangers in every direction, many of them only avoided by quick reactions and decisive actions.

    The pioneers of a start-up are, well, pioneering. They're discovering new territory every day. They learn to be creative, because if they fail to embrace the new, their venture fails.

    Daniel-boone-and-mingo

    It's all about going where people haven't gone before. Your theme song had better feature words like quick, new and creative. Slow, careful and conservative had better be attributes of other groups.

    Most start-ups never really get started-up. Or they take off and fizzle quickly. Or something happens; in any case, it doesn't really work out.

    Things aren't even all in the clear for the few start-ups that manage to get real traction in the market. All too often, the people who discover a wonderful new field of gold…

    Gold
    …find in retrospect that all their efforts amounted to building big neon signs with blinking arrows, signs that say: "Attention established companies: There is gold right over here!" Having discovered gold and brought everyone's attention to it, the start-up is unceremoniously elbowed aside as the established companies, with their organizations and big machines, move in and actually mine the gold.

    And then there are the real winners. Part of the outside world starts to give them respect and another part (the part that feels threatened) says nasty things about them. They have real revenues and real customers. The market recognizes that they have something new and different, and a substantial and growing part of the market wants that new and different thing.

    You might think that at this stage, everyone can breathe a sign of relief. We're on easy street now! It's true that the odds of ultimate success are way higher than they were before. But there are some HUGE mistakes that are made all too often at this point. In particular, there are important behavior and focus changes that need to happen in order to continue on the path to success.

    Here are a couple of the most frequent things that go wrong:

    Innovation Scope and Focus

    When your venture has built up a head of steam, when it's really barreling down the tracks, the worse thing that can happen is to go off the tracks! But this can happen really easily if you haven't changed your innovation focus from "we're in the woods; there are lots of scary animals and danger on all sides; let's look everywhere and innovate about everything" to "we're on a roll; we've got customers and momentum; let's focus on the track ahead and confine our innovation to rolling down this track more effectively."

    TrainWreck01
    If you're not focused on the track ahead and concentrating your innovation on it, chances are you'll go off track.

    Innovation Process

    When you're small and don't have much to lose, your team communicates closely and changes focus quickly. If you've got an opportunity, it makes sense at this stage for everyone to drop what they're doing and jump on the new thing that could put you on the map.

    But now that you've built up a real herd of cattle and more people are involved, things are tougher.

    403px-Chile_cowboys_cattle_1890
    You've got to set up a system that allows you encourage pioneers, but assures that their efforts are mostly productive. You've got to encourage fresh thinking, but somehow assure that an unfortunate innovation doesn't blow up on you and cause the cattle to stampede. You can't (and don't want to) control everything, but you've got to introduce a form of light-weight process that enables a larger group to continue to innovate freely, while guarding against disaster and minimizing waste.  

    Customer Focus

    When you're getting started, your focus is naturally on the great sea of people out there who aren't your customers but could be. You're all about new customer acquisition (if your business is a web site, this means building UV's as you concentrate on SEO and SEM). When you've got traction of the kind we're talking about, you've got quite a number of people who already are your customers (for a web site, this means people who don't arrive via search or a link from another site). This is great, it's what you wanted.

    What you should do at this point is gradually shift your focus to the people who are already your customers. Instead of putting all your effort into looking for new fertile fields, recognize that you've got some really fertile fields, and your job is to cultivate those fields.

    Farm-combine-machines

    It's true that pioneering and hunting got you where you are. But now that you've actually arrived in the promised land you were searching for, isn't it time to shift gears, gather and cultivate?

    Summary

    You've gotten to where you are by concentrating the efforts of a small team on no-holds-barred innovation to discover and build a customer base. You've got a bigger team now and lots of customers who like what you are already giving them. Make it your first priority to keep what you've got, adding "preserve and protect" to your vocabulary. Your business now depends on the customers you've already won — their needs (in most cases) come before the needs of customers you don't yet have!

    You've found the pirates' gold. Do you ALL need to rush off in search of more gold? Can't you manage to guard what you've got, not to mention invest and grow it?

  • HTML, Assembler Language, and Easy-To-Use Tools

    HTML is the assembler language of the web, and that’s a good thing. All sorts of tools claim they will make your life easier and save you from the awful, nerdy depths of HTML. My conclusion: the tools are trouble; HTML is simple and powerful; just get over it, learn and use HTML!

    There’s a pattern here. I have suffered through decades of tools that are supposed to “insulate” you from the grungy details of actual programming, while in the end, limiting what you can do, and not being so very easy to use after all.

    Here’s the background: My wife has a personal web site. I am her webmaster. A little while ago, she decided she wanted to change the site in a major way. The tool I’ve been using for site creation and editing is way past its expiration date. So I decided to start over and dive into the wonderful world of site editing tools. This has got to be easy, I thought. Even Microsoft Word says that it can create and edit HTML.

    “Not so Fast,” cries out the world of practical reality to me.

    I tried a few “easy to use” site creation and editing tools. I didn’t want to get fancy. I just went to my hosting provider’s website, and did simple internet searches. I tried a few tools. I wasn’t happy with the results for various reasons (it couldn’t import my current site, it had templates but they were all ugly and you couldn’t circumvent them, etc.).

    Then I tried importing the home page of the site into Microsoft Word. It appeared to work. I edited the page, eliminating most of the content, and displayed the results. Wrong! The original had a big-font title that was colored and underlined. Nothing I edited should have changed the color or made the text and the underline different. What’s going on here!

    I did not want to dive into details. I really just wanted to get this done so I could move on! But to make a long story short, I ended up getting the HTML generated by the old site builder I used and the HTML that resulted from Word and studying them. Part of why I didn’t want to do this is that I’m not an expert HTML programmer. But I sucked it up and dove in. Among other things, I learned:

    HTML isn’t so hard

    I already knew the basics (it's just programming, like anything else, and diving in confirmed that view). Even without a deep background, you can learn it quickly. Here’s an example from a nice site (http://www.arachnoid.com/lutusp/html_tutor.html)

     

    HTML Code

       

    Browser Display

    I want to <B>emphasize</B> this!

     

    I want to emphasize this!

     

    Word was astoundingly bad

    There was more crap in the file inserted by Word for its own nefarious purposes than the original text. And it screwed up the original appearance!

    HTML is like assembler language, and that’s good

    I’ve always been a back-to-basics kind of guy, and never felt particularly limited during my many years of programming in assembler language. In fact, because of macro pre-processors, assemblers can be amazingly productive because you can  customize the environment to suit the application, something which the “easy to use,” “higher level” tools make difficult.

    Line Up, all you so-called easy-to-use tools, and Die

    Or die a natural death. I don’t care how you get there. Just get it done!

    Conclusion

    I’ve been writing software for more than 40 years, and the more things change, the more they stay the same. Computers, I willingly grant you, are smaller, faster and cheaper; they hold more and communicate faster. But software just gets more bloated and heavy-weight, all the while promising greater ease of use and functional fitness. Going back to basics is refreshing and, sometimes, the only way to get the job done.

     

  • What is the Best Programming Environment?

    What is the best programming environment? Is it Microsoft C#? What about Java? On the other hand, there are the open source scripting languages: are they all about the same, or is python way better than php? While we're at it, how about databases and operating systems? Isn't it true that you really need Oracle if you want a truly scalable application? And if you're really serious, shouldn't you take a close look at DB/2?

    As a long-time techie who has the opportunity to work closely with a wide variety of software/hardware groups, and often has the chance to take a close look at yet more groups my firm is considering for investment purposes, I confront this question frequently. I also get it thrown at me, sometimes by anxious investors or business leaders. They are worried about the possibility of making the "wrong" choice. They are bombarded with conflicting advice, frequently from techies who are truly knowledgeable people and speak with authority and confidence. It's tough!

    OK, Mr. Smart Guy, dish it out! You've got inside information on all these efforts using the different tool sets. You see which ones are productive, and which are not. You see which scale and which can't. What's the answer?!?!

    The good news is, I do have the answer. And I'm going to tell you. But you have to sit through a story first.

    The scene is fifth grade. The playground was a competitive place for me. Running games were important. I was pretty fast, but not the fastest. I needed to get just a touch faster. After much begging, I finally got the new sneakers I had been pining for. The sneakers that would make me run faster, just like the ads said. I was real excited. I put them on and tried them out. Darn! It's true! I really can run faster in these sneakers. I would do little speed bursts, and was amazed at what a difference those sneakers made!

    Pro-keds-sneaker
    Then I went to the playground. I wore my new secret weapons and a smirk on my face. I felt no need to brag; I would let my amazing new speed do my bragging for me. Then the games began.

    Something was wrong. VERY wrong. HOW COULD THIS BE?? I just KNOW I run faster in these sneakers! But I'm not winning!? And with that experience I took a small step towards growing up…

    Thanks for sitting through that vignette from my childhood. Here's why it's relevant: programming environments are like sneakers, and many of the people who use them are like fifth grade boys who don't actually have to compete against other boys on the playground to find out how much difference those sneakers really make.

    Here's the answer to the original question: differences between sneakers (programming environments) are tiny compared to differences between kids (the skills, sophistication and raw horsepower of the people who use them). Put great shoes on weak, slow, unmotivated kids and it won't help them much; force strong, fast, passionate kids to wear crummy shoes and it won't slow them down much.

    This is not my "natural" way of thinking about this question. It is what scores of data points over many, many years have forced me to. The data points don't just come from things I've heard; they've come from things I know up close and personal. I could give loads of examples.

    That this conclusion about technology surprises many people tells us how isolated the field really is from normal human experience. Who, for example, would be surprised to hear that:

    • in baseball, the batter matters more than the bat
    • in art, the painter matters more than the paint or brush
    • in writing, the writer matters more than the word processing program

    Are there differences between the major programming environments? Yes. Can you "prove" that one is better than another for a particular task? Yes, vendors do this all the time. They want you assume that tools are like trains: all you have to do is pick the "fast" train and it will take you to your destination quicker than the slow one. But the reality is that tools are more like sneakers than trains — the tools are things capable people use to get their jobs done, rather than being machines that transport people to where they want to go.

  • Success with New Technology and Mouse Madness

    You’ve
    got a wonderful new technology. It works. Customers benefit from it. Game over,
    right?

    Wrong.

    Sadly
    (for you), the world does not revolve around you. The world is not on constant
    alert waiting for better mousetraps to appear somewhere so that the world can
    beat a path to your door.

    Let’s
    take the B-to-B case. If you’re a big technology buyer, you’ve got better
    things to do than constantly flirt with new vendors. To the contrary, you want
    to find ways to cut the number of vendors you work with. If your
    existing vendors aren’t screwing up, if their products are good enough and
    their price is good enough, chances are you’ll save time and stress and feed
    them more orders as you grow. You may take meetings from wanna-be’s, mostly
    for your general education; it’s a waste of the wanna-be’s time, but that’s not
    your problem.

    The
    reality is that most big technology buyers have a barn of designated winners,
    all of whom are “approved vendors.” The vendors 
    have won the design competition, and are now baked in to the buyers’
    expansion plans.

    The
    only thing that is likely to change this situation is a combination of buyer
    pain and incumbent supplier inadequacy. While some technology buyers are
    motivated by opportunity, most consider a vendor change only when they feel
    pain. The pain is nearly always driven by a need to reduce costs. In order to
    reduce costs, the vendor needs to do X, and if it can do X, it needs to be able
    to do it for a particular price.

    Since
    this sounds abstract, let me illustrate it with a real example from Xiotech, my
    favorite storage vendor.

    Xiotech
    has invented a new mousetrap, the storage blade, which delivers
    storage in better ways than existing storage products, sometimes dramatically
    better. Is it really, objectively better? Yes. Can buyers get more done and
    spend less money? Yes. Does that matter to most buyers? Do storage buyers beat
    a path to Xiotech’s door? By now, the VP of Sales at Xiotech has accepted the
    fact that they do not. Having hoped for the easy life of taking orders, he is
    resigned to having to go out and sell stuff. The world feels cruel and unjust,
    but that’s how it is.

    Xiotech
    has a better storage mousetrap, and the world has reacted the way it always
    reacts to better mousetraps. So what does Xiotech do?

    It’s
    pretty simple, actually. If you had a mousetrap that was really and truly
    better than the other guys’, wouldn’t it make sense for you to find places that were totally, horribly overrun
    by mice?
    Not just places that have mice – places where the mice are in
    charge; places where the mice start trying to invent “peopletraps” because they
    think they’re infested. Places, in other words, where the inadequacies
    of the best existing mousetrap technology have been put to the test and come up
    short – miles short.

    No
    one expects the incumbent mousetrap vendors to walk away from the business that
    has served them so well for so many years. They are bold and shameless, and
    will come up with all sorts of arguments. They will argue that if you have a
    mouse problem, you obviously haven’t bought nearly enough of their wonderful
    traps; the solution is to buy more! If that doesn’t work, they will wave their
    arms furiously about the new trap that is about to come out, avoiding any
    mention of the increase in maintenance charges for existing traps. Meanwhile,
    you walk around and see the mice dancing on the existing vendor’s obviously
    ineffective traps.

    Pd-mice-sample
    If
    you’ve really got a better mousetrap and are looking for motivated buyers, the
    place with the super-sized, invasion-from-Mars MOUSE problem is your candidate.
    Most people buy the same mousetraps they’ve always bought. They may be lousy
    traps, but they just don’t care. It doesn’t matter enough. But the guy with the
    MOUSE problem, HE CARES. He pays attention to mousetrap technology, because he
    knows he’s got a whole pile of mice that need catching REAL BAD.

    The
    cruel fact of life for inventors of better mousetraps is that, if you can’t
    find anybody with SERIOUS mouse invasions, you are hosed. Your superior trap
    will do nothing but waste the time and money of everyone involved. But even if
    you can find places where the mice are dancing in the halls with impunity, your
    mousetrap had better be SERIOUSLY better than the incumbent. If the incumbent
    knocks off a mouse or two but leaves dozens aspiring for a spot on Dancing with
    the Stars, while yours knocks off two or three or four but still leaves most of
    the mice dreaming about skimpy costumes and getting “ten’s” from the judges,
    you may as well hang it up now. To make a long story short, you had better:

    • Find
      a truly worthy mouse problem.
    • Solve
      it. Really solve it. No kidding, nail it!
    • Solve
      it for a reasonable price. If you’re too expensive, you may sell to a few
      desperate buyers, but you’ll never become the industry-standard mousetrap.

    Back
    to Xiotech storage. Xiotech is focusing on buyers who have the kind of problems
    that Xiotech storage, with its high performance and linearly scalability at a
    reasonable price, is uniquely positioned to solve. Just as mousetrap guys look
    for places with too many mice, Xiotech looks for places that can’t get at their
    storage. Just as the incumbent mousetrap guys boldly say “just buy more of my [crummy]
    mousetraps,” the incumbent storage vendors say “just buy more of my [slow]
    storage [that gets even slower as you fill it up].” In spite of such incumbent
    resistance, smart buyers with mouse madness buy better mousetraps, and smart
    buyers with storage bottlenecks buy better storage.

    Success
    with new technology is usually only achieved when:

    • there
      are pockets of buyers who have SERIOUS pain;
    • the
      pain is worth serious money;
    • you
      can find the people with the pain;
    • you
      can address their pain;
    • your
      technology can really make the pain go away;
    • ideally
      without charging more money.

    Failing
    this, I guess you could try waiting and hoping that the world will beat
    a path to your door…

     

  • Moore’s Law, Less’s Law and Storage

    Everyone who has anything to do with technology knows about Moore's Law. If you don't know it in detail or by name, you know it because you have a set of expectations about technology. You expect that whatever is available this year at a given price, next year you'll be able to get more of it and/or it will be cheaper and/or it will be smaller. This is Moore's Law in effect: computer-based stuff gets physically smaller, cheaper, faster; it can hold more and do more at the same price.

    Moore's Law applies in spades to CPU's, memory, displays and even networking. All these things get amazingly better seemingly just by the passage of time. It even applies to disk storage: For example, the 1MB, 12 inch removable disk drives of my early programming days are now supplanted with tiny 300GB drives hidden somewhere inside my laptop.

    While everyone more-or-less knows about Moore's Law, not so many people know about "Less's Law." Maybe it's because Gordon Moore was famous in his own right as a co-founder of Intel, while Seymour Less is famous only for confounding people who think that Moore's Law results in nothing but more and more good things happening. Seymour was fond of saying things like "the more Moore's Law expands disk capacity, the less Less's Law says you can access that capacity." In a time of belt-tightening, managers everywhere are saying "do more with less." Seymour Less is the guy who originally pointed out that, when it comes to disk, you have to find a way to "do less with more."

    I've talked about the impact of Less's Law before, called it something boring like the "performance gap" in storage, and pointed out how it impacts the move to server virtualization. But I've been realizing recently that the implications of Less's Law go way beyond computer storage. The combined impact of Moore's Law (making most computer things better, faster, cheaper) and Less's Law (making storage less accessible) has a profound impact on software architectures. I still find ten-year-old software architectures being touted as "advanced," when they're anything but. On the other side, I see programming groups who are under pressure to deliver good stuff quickly adapting to the new world, and feeling their way to styles of building software that more or less reflect the combined impacts of Moore's and Less's Laws.

    This is a big subject. I hope to explore it in future posts.

  • What are all the programmers doing?

    Maybe you won’t be surprised to hear that this question comes up a fair amount. Actually, I’m kind of perpetually amazed it doesn’t come up more often than it does. What are all those programmers (and related people, like QA) doing, after all? It sounds like a simple question that deserves a simple answer, but if you’ve ever asked it, you’ve probably discovered that simple answers to this question aren’t so easy to come by.

    To help understand the situation, imagine that you’re the “big boss” of a factory. Of course, there’s little more important to you than how that factory is doing. Are its products good? Are they produced in a timely manner? Is the quality high enough? How about the costs – could they be reduced?

    In a real, physical factory, you could always take a tour. You could observe the machines working, see the supplies coming in, watch the work-in-process as it progressed from one stage to the next, chat with some of the workers, see the goods nearing completion. After spending some time on the shop floor, you would probably have a pretty good sense of how things were going.

    Now, suppose we’re talking about a software “factory.” While you can certainly wander around the offices where the programmer’s work, it’s not likely to be a very enlightening experience. Where is the inventory? Where is the work-in-process? Where are the raw materials? Visual inspection of partly completed products (i.e., source code) is unlikely to lead to satisfaction, since you won’t know what the @#$% you’re looking at. When you’re in a car factory and want to know how close to completion a physical car is, you can probably do a pretty good job just by looking at the assembly line and the car in question.  But in a software “factory,” you can’t do that. About all you can do is ask people, and experience shows that that doesn’t lead to good results either.

    Describing what the programmers are doing in typical programmer terms rarely helps.

    Here’s a way of categorizing what goes on in the software factory that sometimes helps outsiders understand what’s going on. Everyone in the software factory is doing one of these things:

    • Keep things running – in a physical factory, these are the normal factory workers who operate the machines, move parts, etc.
    • Make new or enhanced products – in a physical factory, these are the design engineers who change what is built.
    • Make things more efficient – in a physical factory, these are the manufacturing engineers who make better machines, conveyor belts, holding areas, etc.

    You absolutely need to have people in the “keep things running” category (line workers); without them, your factory stops working. To reduce the need for them, you need people in the “efficiency” category (manufacturing engineers). To make their work result in more valuable things, you need people in the “enhanced products” category (design engineers). Here’s how this translates in the software factory.

    Keep things running (line workers)

    This includes operations, maintenance, break/fix activities, things you need to do to bring new customers on-line or otherwise cope with the normal flow of customers consuming the product/service you provide. These people “keep the lights on.”

    Make new or enhanced products (design engineers)

    These are the people who add and/or change code in order to make the product act in new and valuable ways, essentially to get customers to keep paying, or to pay more. Their fundamental job is to bend the revenue curve. You could fire them all tomorrow (please don’t!) and things would keep running – but running exactly the way it runs today, no worse but no better.

    Make things more efficient (manufacturing engineers)

    In a software factory, this activity encompasses tools (source code management, the build system), re-factoring, clean-up or re-organization of code or systems, and automation of technical tasks that otherwise people (line workers) would have to do.

    The lines can seem blurred between these categories in the software factory, but it is often illuminating to think in these terms, particularly when you’re trying to understand costs, investments and the relationship of software to the business.

    For example, we had a company (call it M) that had a huge staff in the data center, but their service was still breaking down too frequently. They were under pressure to cut costs, and also to increase the rate of producing new services. Everyone was screaming. The people in charge of the data center wanted fewer releases to cope with, and everyone wanted to increase the investment in QA to solve the quality problem. Sound familiar? It turns out that this company had “line workers” and “design engineers,” but they had no equivalent of “manufacturing engineers,” and their software production process was simply horrible! They really needed the huge data center staff to cope with the un-runnable stuff the design engineers kept giving them. They really needed a re-think, particularly from a “manufacturing engineer” perspective, the equivalent of re-organizing and rationalizing their factory floor. When they concentrated on this as an important problem and devoted real resources to it in a smart way, everything got better: they didn’t need as many people in the data center, quality went way up and they could turn out new features more quickly.

    But quite apart from making improvements, I have found that this way of thinking about things helps bring understanding to non-technical people, and a fresh perspective to the techies. Try it sometime!

  • Is Your Site Working? Do You Really Care?

    Like He-Who-Must-Not-Be-Named in the Harry Potter books, I find that there is something that must-not-be-named in the world of computing. It is That-Which-Must-Not-Be-Discussed. It’s not so much that people fear it (although many of them do), it is more that it is (for reasons that mystify me) incredibly low prestige. It’s kind of like maintenance or janitorial services in an office building. The higher prestige you are, the less likely you are to mention the subject – it is simply beneath notice. Why, people who wear uniforms, for goodness sake, do the work.

    Nonetheless, this subject is incredibly high value. In fact, it’s hard to argue there is anything more valuable in the computing world. What is the subject? Well, think Haiti. Think Chile. Think Mexico. Think earthquake. Yes, earth-shaking, building-crashing, crevice-opening earthquake. What is the equivalent of an earthquake in the world of computing? You know, yes you do. If it’s a series of scary tremors, then it’s a site slow-down. If it brings down buildings, then it’s a site crash. If it brings down buildings and cars and people disappear into newly appeared holes in the ground, it’s a major outage with data loss.

    Where does making buildings earthquake-proof stand in the overall priority of things?

    It couldn’t have been too high on the priority list at RIM in the time leading up to the earthquake that struck them last December. Here is a representative story:

    http://www.nytimes.com/aponline/2009/12/23/business/AP-US-TEC-Research-in-Motion-BlackBerry-Outage.html

    What a horrible thing to happen to their business! Lots of free publicity of exactly the kind they don’t want.

    The story reminded me of similar events, less public, that have taken place at a couple of companies I know very well. The story also led me to reflect on how data centers (and related development) issues are typically left to fester until they blow up. Then the alarms ring, everyone runs around, the immediate problem is fixed. What is unusual is for management to take the systemic action that is required to greatly reduce the chance of the failure recurring. Some data center operations resemble a coal-fired heating furnace – they require constant care and feeding, are cranky and don’t like change of any kind, but people just don’t want to think about it. “Upgrade to gas? I don’t have time to think about it. Maybe in next year’s budget.”

    Here’s what I find: the more august the group of people, the higher their status, the less willing they often seem to be to devote real time, effort and brain cycles to  That-Which-Must-Not-Be-Discussed.  This is wrong. It is so wrong, it is perverse. Change your priorities! Take a look at it now (or at least soon), when (I hope) the alarm bells are not ringing.

    Even though the articles about the RIM debacle don’t go into detail, it is reasonable to guess a couple things about the RIM operation from facts that have been revealed. Here are some of the warning signs, most of which applied to the RIM case, and some of which may or may not have. I list them here as a quick check-list to see how vulnerable your operation may be.

    • Highly complex system. RIM’s data center was said by several people to be highly complex. This is almost always a bad sign. Systems naturally become complex over time (kind of like entropy), and sometimes smart people insist for plausible-at-the-time reasons on adding complexity. The trouble is that, for a variety of understandable reasons, the more complex a system is, the more likely it is to fail when changed. It is worth working hard to reduce the number of elements in your data center and generally make it simpler.
    • Change management risk. The failure at RIM is said to have been a result of a software “upgrade.” This is one of the most common opportunities for embarrassment. All too often, people respond by reducing the frequency of change, which actually increases the chance that any one change will cause a disaster (because it is likely to be a larger, more complex change). There are methods of reducing this risk to near zero.
    • “us vs. them.” Most data center disasters I have seen happen when there is a (typically well-intentioned) strict separation between data center operations and the rest of the world.

    At minimum, it is worth a quick, objective look at the “machine room” of your operation to see if it looks and feels like the kind of place to which disasters are naturally attracted.

    Above all, get over That-Which-Must-Not-Be-Discussed – yes (dare I say), be like Harry Potter – call Voldemort by his proper name! Talk about earthquake vulnerability! And above all, do what you have to do so that, when things go wrong, your service keeps working.

     

  • The Chief Architect’s Role in A Tech Company

    The
    overwhelmingly most important job of any tech company’s top architect is …
    [drum roll, please]… assuring the reliability and responsiveness of his
    company’s product and/or service.

    This
    may not be what you think. It often is not what the top architect thinks. If
    that is the case, all I can say is, think again, and think better this time.

    I
    find that the technical staff in computer-enabled companies have all sorts of
    ideas of what things are “important.” Generally speaking, “importance” seems to
    be correlated with distance from day-to-day events, distance from the data
    center, distance from anything concerning “operations,” and distance from the
    concerns that existing customers have working with the product/service the
    company provides in day-to-day use. Anything “strategic” – that’s in; that’s a
    proper concern of the top thinkers in the company. Anything “tactical” or that
    could conceivably be in the realm of the customer service or data center
    operations group – that’s out; that’s just a waste of time for the company’s
    best minds.

    However
    common this way of thinking may be, I still find it to be not just bizarre, but
    perverse. The reason, simply put, is that it’s completely out of sync with what
    customers think the most important issues are.

    If
    your product or service:

    • just
      doesn’t work
    • goes
      off-line unpredictably
    • slows
      way down at key times of day
    • old,
      reliable features suddenly stop working, or change their behavior unpleasantly

    What
    do you think will happen to your customer base? If you think you don’t care
    because you have such a great flow of new customers, think for a moment about
    what causes that flow: do you think reputation, references or word-of-mouth
    might have anything to do with it? Do I have to mention Toyota to remind you
    how fast a great service record can get destroyed?

    Now,
    let’s get to the crux of the issue: when those bad things happen, whose fault
    is it, and whose actions and decisions are most highly correlated with creating
    the conditions that led to the problem? To make this simple, let’s turn again
    to Toyota.

    • Is
      the driver (user) at fault due to improper use? Sure, that makes sense, it was
      the users that made the site crash.
    • Are
      the technicians (for example in the data center) at fault? Sure, they can screw
      up; but the best-architected systems don’t depend on technician action to
      achieve reliability and response time.
    • Are
      the customer service people at fault? Hmmm.

    Here’s
    the reality: while anyone in an organization can screw up and cause problems
    for customers, the most serious issues I’ve seen in companies are the direct
    result of architectural decisions or lack of attention/involvement. This
    includes response time, flakiness, down time, and the other things that drive
    customers nuts, not to mention drive them to your competitors.

    I’ll
    give a couple of illustrations.

    A
    company’s web site was down for an hour or more at a time. Repeatedly. The only
    solution is to re-build a key component and its database on a new machine and
    bring it on-line. Right away, the finger of guilt pointed at data center
    operations for failing to deliver. But the root cause of the problem was a key
    application component that had no fail-over capability. How could that happen?
    Simple. The company’s top architects failed to make scalability and fault
    tolerance the non-negotiable, number one priority when selecting this key
    component. Instead they concentrated on all sorts of other things. Are the data
    center people at fault here? Hardly. They just had this crippled software
    tossed at them, and did their best to hold off the inevitable disaster.

    A
    company was in a vice grip of pain. Existing customers were complaining that
    the service provided was slow and faulty. New partners were putting on the
    squeeze for new releases of functionality that they felt were crucial for
    winning business. The more new code the company released, the more bugs and
    customer problems were created. When the company tried to slow things down to
    stabilize the service, the angrier the new partners got, who accused the
    company of failing to meet its commitment to them. The data center staff
    exploded, the QA staff grew, consultants were crawling around, and life was
    miserable. The root cause? Again, simple. The company’s top architects had
    completely ignored the whole release and go-live process, and built a software
    system that was designed for a set of unchanging requirements, instead of the
    fluid and constantly changing reality of the company’s customers and market.
    The whole nightmare was an architectural side-effect, and the solution was a change
    in architecture – the good, practical kind of architecture that encompasses
    everything about the company’s product/service, including releases and the data
    center.


    I
    think the message is a clear and simple one: if your top minds are not already
    focused on the company’s most important issues, viz., those that are most important
    to your customers, get them focused on those seemingly mundane, tactical,
    near-term, nuts-and-bolts concerns. Now.

  • Server Virtualization Problems and Xiotech ISE Storage Blades

    Server Virtualization
    (Hyper-V, VM-Ware, etc.) is making people aware of the growing crisis in
    SAN/storage performance. There is a solution: Xiotech ISE Storage Blades.
    Xiotech Storage Blades are the least expensive, least disruptive and most
    effective solution to the performance problems that virtualizing servers almost
    always seems to cause.

    Is there a
    problem?

    Anyone who has tried
    seriously deploying virtualization in a data center knows there is. A recent
    post
    by the ESG’s Mark Bowker makes the issue very clear.

    IT sells the business on the value of server
    virtualization and calculates the ROI on the back of a napkin during a lunch
    meeting. They get the green light. … Confidence is high and they start to
    target the next tier of applications, such as Microsoft Exchange, and suddenly
    realize that the 7200RPM SATA drives they purchased to support their entire
    virtualization deployment may not cut the mustard

    The fear is that they drop this new Microsoft
    Exchange VM in place and start having major performance issues… [with] their
    existing virtualization investment that has the compute horsepower and storage
    capacity available, but not the storage performance. …

    As a result of all this and other similar
    scenarios, server virtualization deployments are stalling. 

    The entire post is worth
    reading, but I’d like to point out the core of the issue: the typical
    virtualization environment “
    has the compute horsepower and storage
    capacity available, but not the storage
    performance.

    Why Is there
    a problem?

    The core reason there’s a
    problem is that as disks get more and more capacity, they don’t get any faster.
    Imagine a terabyte of data in the old world, on 10 disks. If you have 5
    programs asking for parts of that data, chances are pretty good it’s going to
    be on a disk that isn’t busy right now, so the performance will be great. In
    the wonderful new world, that same terabyte of data fits on just one disk. So
    if you have the same 5 programs asking for data, there is a 100% probability
    that the one disk that has all the data is already going to be busy with
    someone else’s request. Here is a more detailed discussion of the performance
    gap in storage
    if you’re interested.

    So quite apart from
    virtualization trouble, storage is getting slower and slower.

    Why Does
    Virtualization Make it Worse?

    Server virtualization is an
    excellent thing. It helps you make more efficient use of your hardware. It does
    this by distributing a set of programs that need computing resource
    over a set of servers. This is just like running several programs on one
    machine at the same time, except that now we’re distributing a set of programs
    over a set of machines, and the programs can even require different operating
    systems (like Windows or Linux) and the virtualization still works. So instead
    of having 40 programs running on 40 machines, virtualization might let you run
    them on just 10 machines. A huge savings!

    The trouble comes when those
    programs start asking for data – pesky programs, always wanting data!  Now, instead of requests coming to the storage
    from 40 machines, we have the same number of requests coming from just 10
    machines – a 4 to 1 concentration of requests. The storage doesn’t “know” about
    the 40 programs. It just sees the demand for its services going through the
    roof. It’s like people trying to get into a ball park for a ball game. If you
    suddenly block off 30 of the 40 entrances and make everyone come in through the
    remaining 10, the lines are going to be long, the ticket takers frazzled, and
    everyone is going to be mad. Not unlike what happens when you virtualize
    servers in the average SAN environment!

    We have a problem because programs
    running on fewer servers (because of virtualization) are trying to get to their
    data from fewer disks (because of increased capacity per disk).

    Xiotech ISE
    Storage Blades to the Rescue

    What made anyone think that
    sleek, efficient server blades would work well with the average storage
    mainframe
    in the first place? Inertia, I guess. If you’ve got linearly scalable server blades, wouldn’t
    you want … linearly scalable Storage
    blades
    (bricks) to go with them?

    Let’s talk performance for a
    minute. How about:

    10,000
    Exchange users per 3U ISE

    And then add a second for
    20,000 users, a third for 30,000 users, and so on. Here
    is a post
    with details on how others attempt to meet the need, a video
    about the benchmark, etc.

    There is certainly a problem.
    The amount of money going into expensive SSD’s tells us there’s a problem.
    Stalled virtualization projects tell us there’s a problem. Xiotech ISE Storage Blades
    with awesome performance that doesn’t degrade as the device fills up are the
    solution. There is even software that
    makes setup painless
    in a VM environment!

  • WSJ: Oak Investment Partners’ 22 $100M+ Revenue Companies

    The WSJ had another article
    about venture capital, this time focusing just on Oak Investment Partners, the place I work during
    the day (and at night and on weekends…). The whole article, “The
    $100M Revenue Club: Oak Investment Stocks Up
    ,” is well worth reading. Here
    are a couple of highlights:

     

    “Companies with annual revenue exceeding $100
    million rarely used to show up within venture capital firms’ portfolios.”

    “But few if any firms have as many of them in their
    portfolios as Oak Investment Partners,
    which has 22 private companies that generated more than $100 million in revenue
    in 2009, according to information gathered and confirmed by Dow Jones
    VentureWire.”

     “Thad Gray,
    who is a managing director with fund-of-funds Abbott Capital Management and
    sits on Oak’s Valuation Committee, has become a strong believer in the venture
    growth equity investing model … Gray said Oak has found success thanks, in
    part, to having partners who are recognized as sector experts in complex areas
    including health care information technology, financial technology, digital
    media and energy technology.”

    I have already posted about a
    couple of the companies in the list of 22, including Kayak.com, iCrossing and
    Demand Media.

    In the quote above, Thad
    talked about Oak’s “venture growth equity” investing model. This is a
    relatively new model of venture investing, and Oak is demonstrating what it is
    and how to do it. It combines important aspects of traditional venture capital
    with some aspects of private equity. Since it’s relatively new, it’s worth
    explaining.

    The popular image of venture
    capital is early stage investing. You might think that the internet would favor
    early stage companies, because it is so relatively easy and inexpensive to get
    a web site and make it not only viewable, but findable (as I discussed
    previously) to anyone in the world. The bar is low, so the start-up
    entrepreneur with his genius idea can get it going with a little seed money
    from a savvy early-stage investor and watch it rocket to success. It’s all
    about having the break-through idea; you need hardly any capital to make it a
    reality. Right?

    Let’s take that idea and
    apply it to baseball. Suppose we find a couple of guys who have a terrific new
    approach to pitching and catching. They’ve got it working in the “lab.” Now
    they’re ready to go for it, and they look for a savvy VC who recognizes their
    potential. If they get funded, the money will come from a traditional
    early-stage VC. A VGE investor like Oak will pass; the opportunity is too early
    stage. We don’t invest in individual players, regardless how good they are; we
    only invest in teams that have found a way as teams to compete
    and win in their league.

    The way we see it, when the
    VC invests in the pitcher-and-catcher novelty act, they’re going out and
    competing in a playing field (called the internet) against full teams. Like it
    or not, those two will be “taking the field” against teams that field nine players
    and have a deep bench. The pitcher-catcher combo may be unbelievable, but they
    are sure going to have to be, given that they have no one playing first base,
    no one in right field, etc. Then of course when it’s their turn up at bat, their
    batting order consists of two players – perhaps not so good…

    Demand Media, for example, is
    a full baseball team – they are literally “covering all the bases.” And they
    have a deep bench and value-adding back office. It’s hard to figure out how a
    couple of individual players, regardless
    of how talented and hard working those individual players might be
    , could
    possibly compete against a whole baseball team, particularly when so many of
    Demand Media’s players are all-stars.

    Let’s just take a quick romp
    through the Demand Media “player roster” to illustrate all the different roles there
    are in a fully-staffed team:

    • A design team to
      make their web sites look good.
    • A sales team to
      craft the kinds of advertising deals that fit their content.
    • Separate teams
      for each individual property (golflink.com, ehow, Livestrong, Cracked, etc.)
    • Strong
      non-consumer technology-centric efforts (Pluck.com, enom).
    • A creative,
      numbers-driven and results-focused research effort.
    • Strong technology
      driving a leading-edge business model (Demand Studios).
    • Major value-adding
      data center operation.
    • A group that can analyze
      huge traffic (many tens of millions of uniques a month) and optimize.
    • Unique technology
      derived from the huge volumes that increases effectiveness (this is
      purposefully vague).
    • A sharp finance
      operation to help keep cost focus.
    • Strong,
      charismatic business leadership.

    When the baseball team is a
    bunch of has-beens, you can imagine being just a couple of stand-outs and
    competing against them. But on the internet, you end up competing against teams
    of the best. The scale is so large, like it or not, it takes a team to compete
    and win. That’s why the Venture Growth Equity approach makes sense, even on the
    internet (actually, once you understand the issues, it’s particularly on the internet).

    Like with any venture, there
    are also intangibles, the kind of thing you feel when you’re on site with the
    people, as I was last week with Demand in Santa Monica, along with my buddy
    Ranjan Chak. I seem to feel good every time I visit, whether we’re celebrating
    the good things that have happened or we’re grappling with challenging issues. Or
    both. The attitudes, levels of engagement, and sophistication of approach are
    just outstanding. Above all, they are a nerd-fueled enterprise (a subject I’ll
    go into sometime soon), which by itself puts them at a different level than most
    companies.


  • Nerds in Norway

    I can personally attest that there are nerds in Norway. I have been there. I have seen them. I interacted with them, for hours and hours. They are, indeed, nerdy. Most, though not all, are Norwegian nerds; others are simply nerds who happen, at the moment, to be in Norway.

    It may be that the folks roaming the streets in Oslo are largely nerds; maybe few of them are; I can’t say. What I can say is that there is a whole passel of them in the offices of Point Carbon, a company I visited earlier this week.

    Computer nerds all over the world have lots of things in common, which is part of why it’s so much fun to visit them. Part of the fun is also seeing how they’re different.

    The most obvious differences spring from the fact that these nerds are in, well, Norway, which is kind of far north and is loaded with mountains. Norway, as you may know, came away from the recent Winter Olympics with a huge number of Gold Medals, which only strikes you as the amazing accomplishment it truly is when you realize that the whole country has fewer people than Brooklyn and Queens put together. So I guess it’s not so very surprising that you see skis leaning up against the computer-laden desks of these urban nerds.

    Marianne Amble, their head techie, was kind enough to give me permission to post a couple pictures from a recent winter party she and her nerds had, by way of illustration of the Norwegian-ness of the Point Carbonites.

    Here are nerds getting ready to race down the hill, like the mature adults they all, undoubtedly, are…

     

     PC nerd 1

     

    OK, nerds, get ready, get set…

     

    PC nerd 2

     

    GO!

     

     PC nerd 3

     

    After all that work, it’s time for some relaxation, but let’s have some dry ice to remind us what part of the world we live in, and a colorful greeting from Espen…

     

    PC nerd 4

     

    I had a lot of fun on my recent visit, and really appreciate the hospitality and good, honest, open work we got to do together.

  • Oak Investment Partners in the WSJ’s Top 50 Venture Companies

    Oak Investment Partners has
    backed more than 10% of the WSJ
    list
    of the Top 50 Venture-Backed Companies! 6 out of 50! What’s even
    cooler is that we’ve got quite a number of exciting, substantial, profitable
    companies that didn’t make the list.

    If you click on any company
    in the list, you get a photo of the CEO and a nice summary of the company.

    Here are the 6 Oak companies
    in the list of 50:

    #10: nGenera. Many people are familiar with Don Tapscott and his
    forward-thinking books like Wikinomics. I just discovered that he has
    over 13,000 followers on Twitter!
    But Don is just the tip of the iceberg at nGenera, which is at the forefront of
    helping our major organizations transform themselves into more effective, collaborative
    enterprises.

    #14: Ventana. Oak backed Athena Health, a company that is revolutionizing
    the automation of medical offices. Athena is now public and doing very well.
    When Todd Park, who co-founded Athena (along with Jonathan Bush) was ready to
    try something new, he ended up starting what is now Ventana, which promises to transform
    the relationship between consumers and health care providers. And then Todd got
    called to serve as the CTO of the US Dept of HHS! But the company is in good
    hands with their capable and dynamic CEO, Gio Colella.

    UPDATE: Ventana has a new name: Castlight Health.

    #22: Huffington Post. This is a completely
    amazing company. I’ve written about
    them
    a bit in the context of the media-i-zation of the world. People seem
    to think of Huffington Post in terms of old media companies, or left-wing
    politics, or some other verbally-oriented perspective. But my
    blog post
    about nerds and yakkity-yaks gives the most relevant perspective –
    they have an amazingly powerful tech team who keeps pushing the edge of what’s
    possible in on-line media. When you see how Paul Berry and his team do it on
    the inside, it’s even more impressive. They’re nicely integrated with
    editorial, just like they should be, and like similarly powerful tech teams so
    rarely are. And we can't forget (who could?) Arianna, who as of this moment has over 394,000 Twitter followers.

    #29: Boston Power. The WSJ explained why
    this company is hot, and I don’t think I could say it better. “
    It's in
    the competitive Lithium-ion battery space, but backer Oak Investment Partners
    has deep pockets and its board member, Bandel Carano, has a strong track
    record.
    ” Boston Power is on the road to making,
    for example, all-electric cars truly practical.

    #46: iCrossing. I’ve already blogged about this
    company over
    and over
    again. They are the clear leaders in their fields – yes, more than one!

    #47: SmartDrive. SmartDrive is a classic
    innovative, industry-transforming venture. It makes our roads safer for
    everyone, protects good drivers when they get in bad situations, detects bad
    drivers before really bad things happen, and on top of everything else helps
    reduce the amount of fuel consumed. It’s very satisfying to have a company that
    delivers such a clear range of benefits, leveraging the latest technology and
    an effective service model.

  • The Primacy of SEO, SEM and iCrossing

    What is the absolutely
    most important thing
     about a
    web site? A clean look? Attractive graphics? Usability? I say that win, place
    and show for a web site is visitors — being found. That means that when
    picking a digital partner, there is really only one selection criterion that
    matters: how good are they at SEO/SEM? That, in a nutshell, is the case for iCrossing.

    I've written about this before. But I'm thinking about it
    again because I just reviewed the slides from the recent iCrossing Board
    meeting. The meeting was in Scottsdale concurrent with customer meetings, so it
    included golf and other pleasant, sunny events. Meanwhile, New York City is
    still digging out from a record snowfall, so naturally I chose to stay in NYC
    and skip the meeting. What else is a nerd supposed to do? What do I know from
    $%^$ golf, the surest
    way to ruin what might otherwise be a perfectly pleasant walk??

    Among the events reported at the meeting were a couple customer
    wins in which the general-purpose digital agency of record was replaced by
    (supposedly SEO-specialist) iCrossing. The losers must be grousing about what
    idiots they have (had) for customers, firing wonderful, charming,
    does-everything them and replacing them with a "niche
    search-specialist" player like iCrossing. 

    Partly, the grousing is wrong. iCrossing is, in fact, a
    full-service digital marketing agency. They build web sites, do design work,
    etc. But mostly, the losers are missing something important: it is unbelievably important to be unsurpassedly, awesomely great
    at SEO.

    It all becomes clear when you use physical metaphors instead of
    the usual barrage of TLA's.
    Let's suppose you've got a store that sells sweaters. It's a nice store, with
    its name out front in big letters: "Sally's Sweater Store." It's got
    a big window by the sidewalk with an attractive selection of sweaters. The door
    is inviting. This is the equivalent of building a website. It’s important!
    However, the store is located at the end of a dead-end street away from the
    main shopping area of a small town.

    Which activity do you think will be most rewarding to Sally, the
    owner of the Sweater Store:

    1.  
    Get in some experts on “store face” design to get her a better
    sign and display window.

    2.  
    Get in some experts on “shopper usability” design to work on the
    in-store displays, aisles, mirrors and other factors that make the store more
    pleasant to shoppers.

    3.  
    MOVE THE BLANKITY-BLANK STORE to a high-traffic area of a major
    city with convenient parking, lots of foot traffic, and other stores nearby that
    attract people who want clothing.

    If the answer isn’t obvious, I can’t help you at all.

    However, I will admit that while the answer is perfectly obvious
    in the physical world, it can be a bit confusing in the on-line world. This is
    because the equivalent of action #3 above involves making internal changes to
    the site, just like actions #1 and #2 – but they are entirely different kinds
    of actions, changing different kinds of things for different reasons.

    You see support for the MOVE THE STORE, STUPID strategy every day.
    Just today, a up-and-coming e-commerce company hired an ex-Google exec as CEO. What
    is she going to concentrate on? According to an article
    about her
    in the NY Times Bits Blog, “
    Ms.
    Singh Cassidy said she planned to concentrate on bringing more users to
    Polyvore.
    ” In other words, she wants to move the store.

    You might think that I think that the “S-factors” (SEO, SEM) are
    the only ones that matter for growing traffic. Of course, we all know that
    social media can have a huge impact site visits. (BTW, iCrossing has a great
    social media practice, too.) There is nothing like having positive words about
    your site be spread among a network of friends or twitterers. I don't claim
    that SEO and SEM are the only factors in generating site traffic — far from
    it. But based on experiences I’ve had with a variety of sites, I would say you
    would be well advised to resist painting the walls and fiddling with the
    display windows, and instead put more effort moving your shop out of that
    dead-end street it’s on now.

  • Everything is Media!

    We think that "media" is a small part of "everything." But that's changing. Everything is turning into media: the world is becoming "media-ized."

    Here's a framework for understanding what's happening:

    First, we have broadcast media, the "original" media

        The information flow is one to many

        Examples: newspapers, TV

    Second, we have communications, one person interacts with another

        The information flow is one to one

        Examples: face to face, phone, individuals talk

    Third, we have transactions, a person goes to a merchant to get or do something

        The information flow is many to one

        Example: go to a store and check out
     

    If you think about life in the distant past, that is in the pre-internet era (if you are old enough to remember that long ago), you can recall how very different those three categories were. 

    Sitting down and talking with someone is clearly communications (one to one). While you're sitting down, you may agree to listen to the radio or watch TV. Then the two of you are consuming media (the media source is the one, the two of you are part of the many). You may see or hear an advertisement on the media. Later, you go to a store and buy the item (you are one of many people who go to the store).

    These categories are clear and distinct; no one could possibly confuse (1) talking with a friend, (2) watching TV, and (3) buying something.

    But on the internet, things have changed! These three categories, once so clearly separate from each other, are merging into minor variations of a single thing. They are now the variegated media-transaction-communications complex, a complicated single thing which has the characteristics of all three.

    It's easier, and closer to the facts, just to say that the formerly distinct activities of communicating and buying things have become subsumed under "media." Why? The "place" where this activity happens is on screens that you can touch or have keyboards and/or have a mouse, the same kind of screen we use for watching TV, which is clearly a media experience. When communicating and transacting are brought into the world of screens, they adapt to their new world, and become media-like. That's why I say, the world is becoming "media."

    I think about this a lot, partly because of personal experience, but also because I'm involved with companies that have to adapt to this new world.

    The companies that "get" this convergence of everything to media are the ones who succeed in the new "everything is media" world.

    Here are some of my favorite companies and a little sample of what they're doing that shows how they "get" it.

    • Huffington Post is a "media" company. But they are clearly stretching the definition of what "media" is way beyond anything the media dinosaurs can fully comprehend, much less keep up with. The easiest way to see this is the way they are going beyond the classic "elite" media one-to-many model with thousands of bloggers, citizen journalism and an extremely committed and robust community of reader/collaborators who communicate with each other using the site's comments and connections to Facebook and Twitter.
    • Demand Media is making progress on many fronts, with a full-fledged research operation to help guide their efforts. Some of their sites look a lot like on-line versions of classic niche media, for example www.cracked.com. Others are breaking the tyranny of one-to-many media by pioneering the use of professionally generated content to achieve something closer to many-to-many media, for example www.ehow.com. Finally, they are evolving the many-to-one merchant model in media-savvy ways, for example in the Daily Plate section of the Livestrong.com site.
    • Federated Media is all about the shift from broadcast-style media to what they call conversational media. The whole premise of the company is that there is a new kind of media emerging that transcends traditional broadcast models, and this new media naturally calls for a new kind of advertising for merchants to interact with consumers. In fact, Federated Media is right in the middle of a kind of media that incorporates strong elements of conversation and makes a bridge to transactions.
    • FirstRain is not a media company at all, in the old sense. Their roots are in providing search services to financial professionals. But now, like any new media company, you can search for something relevant and find their pages, for example this report on Yahoo. The harsh rule of media is that consumers will glance at your page; if they like it, they'll stay for awhile and explore; if they don't understand it or like it, they'll navigate away, and you've lost them. FirstRain is already a generation ahead of their peer group in understanding and implementing this.

    You may think you're a media company — have you really gotten all the factors that are now part of succeeding in media? You may think you're an e-commerce company — have you really gotten how being an on-line version of a store isn't even in the right ball park, how you're now a media company? You may be a completely different kind of company, like FirstRain — do you get that success means becoming (at least in part) a media company?

    That's because … in the new world we live in, everything is media!

  • Databases, Logical and Physical

    Everyone seems to assume that having a central database is a good idea. Well, I’m sorry, but “everyone” is wrong. Dead, flat-out WRONG. Get over it.

    Now (if you’re still with me), before you conclude that I’m insane or just stupid, let me point out the applicability of a concept that’s been around in computing, oh let’s say, more than half a century – the difference between “ logical” and “physical.” Generally speaking, we get things done in the world of computers by concentrating on the logical world. Then we apply a logical-to-physical mapping, and that makes things work in the real world. We do this all the time. Practically everything in computing involves layers and layers of logical to physical mappings – you get layers because the “physical” layer you thinking you’re mapping to often itself turns out to be logical, and needs mapping again to another layer, and so on recursively.

    However familiar we all are with logical mappings, and however much we depend on them in our daily lives, we also work in a world of assumptions. There are a set of practices we have grown up with or inherited, and we simply continue them. How could it be otherwise? If you spend too much time questioning assumptions, you’ll be paralyzed and never get anything done.

    The “central database” and how to implement it is one of those deep-down assumptions. There has got to be one reality, one SSN per customer, one balance. This is true and good. I accept it, as a concept that applies to a database at the logical level. But at the physical level?? Exactly one physical copy of the data in a single physical database (not counting backups, etc.)??? Hey, remember that thing we do all the time, that logical-to-physical mapping thing? How about one logical copy of the data in a single logical database, embodied in as many physical databases as are required to get the job done…now, there’s an idea…seems promising, yes?

    So why is, when I walk into some data centers, there is a huge, company-existence-threatening drama about the – get this – one physical database??!!

    It’s so big, it’s slowing down, it’s freezing up almost every day now, what can we do? We’ve already (pick your favorite):

    • “upgraded” to Oracle
    • “upgraded” to Oracle RAC
    • “upgraded” to Sun/HP/IBM mega-servers
    • “upgraded” to ultra-expensive super-storage

    Whine, whine, we’ve spent all this money, “everyone” said we were doing the right thing, now the problem is back, I’m going to lose my job, customers are leaving and/or threatening, my business is under siege, I’ve had the “best” people on the case for months, I’m still in trouble, what can I do???

    Go back and re-read the opening paragraph, the one about central databases being bad – unequivocally, supremely, annoyingly BAD. Remember that paragraph? Now, re-read it in two alternate versions, remembering the concept that pervades your everyday existence in computing, logical-to-physical mappings:

    • Having a central logical database is a good (as in: terrific, why would you have it any other way) idea
    • Having a central physical database is a bad (as in: awful, what are you, stupid) idea

    Any discussion? Any questions? Everyone cowed or shamed into submission? Good.

    Now, if you’re not already in the good place, stop reading stupid sarcastic blogs and go get it done!! On the other hand, if you are already in the good place, I hereby give you permission to wallow in glorious feelings of superiority and smug satisfaction for a little break before you go back and do something useful.

  • Nerds and the “Yakkity-Yaks”

    We have some really smart people at some of our companies. The trouble is, there's more than one kind of smart; when everyone settles on the idea that their kind of smart is the only kind, bad things can happen.

    There is a kind of smart that tends to be really successful in normal worldly terms. This kind of smart is highly verbal, good at communication and interaction. You see loads of these people at prestigious schools, elite institutions, and so on. They are quick on their (verbal) feet and subtle. They know how to shift tone, when to get personal and how much, and when to bring in what kinds of facts and references into a conversation. Get a group of these folks together, and you can just sit back and watch the maneuvering as they attempt to establish hierarchy among themselves.

    What happens to this kind of smart people? They tend to climb organizational hierarchies really well, particularly since their elite institutional training gives them a head start. They do the "important, strategic" work; they hire people to do the regular work.

    I fully accept this kind of "mainstream elite" as a kind of smart. But it's not the only kind.

    One of the kinds of smart that I particularly value is often called "nerdy." An extreme view of the contrast between "talk-y, strategic, people-smart" and nerdy was nicely put today by a nerd's nerd. Here is the start of an interview with Temple Grandin:

    'Who do you think made the first stone spear?" asks Temple Grandin. "That wasn't the yakkity yaks sitting around the campfire. It was some Aspberger sitting in the back of a cave figuring out how to chip rocks into spearheads. Without some autistic traits you wouldn't even have a recording device to record this conversation on."

    While Ms. Grandin has become famous because she is an autistic who is accomplished, what is remarkable about her is how truly accomplished she is. For example:

    Today, half of the cattle in this country pass through the slaughter systems that Ms. Grandin invented. She's a consultant to companies like McDonalds and Burger King. Yet—and she might well be the only person with these two associations—she's also been honored as a "visionary" by PETA for making slaughterhouses more humane.

    Temple Grandin has transformed a huge industry, and she clearly lacks "yakkity yak" type smarts. Before Ms. Grandin came along, there were all sorts of "mainstream smart" people involved in meat packing, an industry that employs over half a million people. If you went to the executive conference rooms of this industry that slaughters roughly 10 billion animals a year in the US alone, you would find piles of well-paid, highly accomplished yakkity yaks who would never dream of actually paying attention to "details" like the walls of the corrals, whether they're curved or straight, solid or slatted. And yet it is details like curvature and slope of walls that determine whether or not a slaughter operation is efficient (not to mention humane). Generations of executives in this industry were all one kind of smart — the kind of smart that impresses other similarly smart people, the kind that is too absorbed with "strategy" and other in-the-clouds kinds of things, the kind whose time is way too valuable to get "lost in the weeds" of details like corral design.

    In a technology-fueled enterprise, it is really important to have smart people. But not just one kind of smart.

    • Yakkity yaks are really valuable to have. They can be great leaders, and they can help find the way to make a company with a disruptive innovation real-world successful.
    • Nerds are really valuable to have. They get totally absorbed in the objects (physical or logical) that need transforming, and can make it happen.

    When the balance between the kinds of smarts is wrong, bad things happen. If the yakkity yaks get out of control and run the show their way, somehow the software doesn't ever work and the cool stuff never gets delivered. If the nerds are left to their own devices, they might spend too much of their time solving problems without real-world relevance.

    When the yakkity yaks and the nerds cooperate, collaborate and work towards a common goal, watch out — that's a place that's going to invent cool stuff that people actually need and use, become a meaningful business, and be barrels of fun for everyone involved.

Links

Recent Posts

Categories