Welcome to KnowledgeLink - The AKG Blog

Missed opportunities

Posted by Lindsay O'Bannon on Tue, Nov 18, 2008 @ 15:11 PM

By Benjamin Hartley, November 18, 2008

The IBM PC was first sold in August of 1981. The original IBM PC had a 4.77 mHz CPU, 64 kB of RAM, a CGA video card, a pair of built-in 5 ¼" floppy drives, and the ability to easily add a 10 mB hard drive. Nearly three decades ago, that was a very nice personal computer, but it wasn't half the computer it could have been, and it's worth our time to examine why. Let's start at the beginning – how did IBM decide to start selling personal computers, anyway?

In 1980, IBM upper management noticed something very disturbing: IBM accountants were purchasing Apple II computers with their own money and bringing them in to work. This was entirely unacceptable. These people worked for IBM, the supplier of business machines. What could this "fruit" company possibly offer that was worth the loyalty of an IBM employee? (And don't scoff about company loyalty. Back then, IBM had an official corporate song. Songs, in fact.) So these accountants were willing to spend large amounts of their own money, and risk their jobs, for this tool. What did it have?

As it turns out, the Apple II had an awful lot to offer. On examining the product, IBM's upper management decided that they absolutely had to provide a product equivalent to the Apple II. Anything less would be suicide. But they had a problem…

IBM at that time was an incredible, lumbering beast. The level of bureaucracy was simply amazing. It has been compared to a country. It had a decision-making process which was absolutely dedicated to quality. As former IBM programmer Rich Seidner said in "Triumph of the Nerds":

I mean it's like getting four hundred thousand people to agree what they want to have for lunch. You know, I mean it's just not going to happen - it's going to be lowest common denominator you know, it's going to be you know hot dogs and beans. So ahm so what are you going to do? So IBM had created this process and it absolutely made sure that quality would be preserved throughout the process, that you actually were doing what you set out to do and what you thought the customer wanted. At one point somebody kind of looked at the process to see well, you know, what's it doing and what's the overhead built into it, what they found is that it would take at least nine months to ship an empty box.

Nine months to ship an empty box. Nine entire months, and that's without product development, manufacturing, quality control, marketing plans… just to get an empty box. Today, entire industries spring up and die in that period of time, and IBM couldn't even get a product to market. Under normal IBM processes, it would have taken four years and three hundred people to create an IBM personal computer. Obviously, it didn't take that long. IBM found another way. They created Project Chess, a special project for the creation of a PC – in under a year, and with only twelve people on the team.

By traditional IBM processes, that wasn't merely impossible, but outright ridiculous. Project Chess called for radical changes in how IBM worked. Instead of a months-long approval process involving multiple committees, individual team members made snap decisions. Designs were implemented almost immediately. And most importantly, the decision was made to outsource and utilize off-the-shelf components. This decision cut years off the project – but it had far-reaching consequences.

Traditionally, computers were almost entirely designed and built "in-house" by the manufacturer. There were few if any components made by other companies, and the inner workings of the computer were kept closely-guarded secrets. IBM did not have the luxury of following this model. Instead, it had to use an "open source" architecture in which the computer's inner workings were publically known. This was needed to build a computer utilizing components from a number of suppliers. Most notably, rather than using the superior IBM 801 processor, which would have required more development time to add to the PC, they instead used the Intel 8088 processor. Today, Intel is the leading manufacturer of processors, with an annual revenue of $7 billion, mostly as a result of CPU sales.

Btu there's more. Since IBM didn't have time to develop an operating system – a key piece of software – in-house for its new PC, IBM had to once again look elsewhere. Their first pick was a well-known programmer named Gary Kildall. Gary Kildall was the foremost programmer of operating systems at the time. His operating system, CPM, was used on the majority of computers in operation, and had been for several years. He was the logical choice for IBM.

And when IBM employees showed up on his doorstep he wasn't at home. His wife, Dorothy Kildall, refused to sign the non-disclosure agreement IBM insisted on. After a very frustrating day, the IBM employees left without an operating system, and Gary Kildall was relegated to a footnote in computing history.

A more opportunistic company ended up providing the operating system for IBM. One that didn't even have and operating system, but saw an opening and took it. That company, Microsoft, is now one of the largest companies in the world, overshadowing IBM by a sizable margin.

With that last crucial component, IBM was able to get a personal computer on the market in under a year. IT was a resounding success, and for over a decade "PC" and "IBM-compatible" were synonyms. But IBM didn't control the personal computing industry. Within a year of the IBM PC coming to the market, Compaq had a competing product which was equal to or better than the IBM PC in every way. Soon, there were dozens of IBM PC clones. Today, IBM is a bit player in the PC industry.

So what can we learn from the genesis of the IBM PC? Naturally, we can learn a great deal about agility. IBM's first failure was in not noticing the market changes in the first place. By the time IBM realized they should be selling a personal computer, the personal computer industry was already huge. The second failure was in IBM's lack of agility: a company which takes nine months to ship an empty box is in no shape to respond to market changes. This in turn forced IBM to seek outside support – not itself a flaw, but in this case putting IBM in a vulnerable position down the road. Then, Microsoft's ability to catch an opportunity where Gary Kildall failed ultimately spawned the software giant we know today.

Obviously, it's impossible to know where IBM or the computer industry in general would be had IBM been better able to produce a PC on their own. We can, however, learn from history. Even more today than thirty years ago, companies need to stay agile in order to remain competitive. A failure to anticipate and take advantage of a market opportunity today can have very far-reaching consequences.

Read More

Topics: Microsoft, agility, IBM

The third day at Dev Con 2008 cont'd

Posted by Janetra Meyers on Fri, Nov 14, 2008 @ 15:11 PM

2nd Session:  HEC302: Deploying Content Infrastructure in a Web Content Management Environment

Speaker:  Paul Stork

This session was informative because the speaker went behind the curtain on how to properly deploy web solutions in MOSS 2007.

The agenda for this session:

• Content versus Infrastructure
• Automated Content Deployment
• Configuring Content Deployment
• Infrastructure Deployment
  - Creating SharePoint Features
  - Building and Deploying Web Solution Packages

Knowing the difference between Content and Infrastructure is essential to successfully deploying solutions.  Configuring content deployment involves paths and jobs.  The last sentence sounds a bit out of place when talking about Content Deployment, but proper context is everything.  Proper context can be found here:



Selecting the correct Security Deployment Options is extremely important in deploying content and Paul stated the options are "All, Role Definitions, or None".  An overview of what is deployed, the steps for deployment, a final wrap up of building and deploying solutions, and much needed demonstrations were included in this session.  I gained a lot from this session.

4th Session:  HSC301: SharePoint Personality Disorder: FBA, ADFS, LiveID, NTLM, Kerberos, LDAP

Speaker:  Robert Ginsburg

This nicely titled session was extremely long and detailed on the various types of security in a MOSS 2007 environment.

I provided links to web resources to keep this post from getting too dry.  Enjoy!

FBA (Forms Based Authentication)

ADFS (Active Directory Federated Services)

LiveID (Windows Live ID Authentication for SharePoint)

NTLM (Windows Challenge/Response)



Read More

Topics: SharePoint, MOSS 2007, Security, SQL, dev connections 2008

The third day at Dev Con 2008 and the semi-summary

Posted by Janetra Meyers on Thu, Nov 13, 2008 @ 16:11 PM

The recaps for the third day at Dev Con have been cut down because of my focus on subjects that are not as familiar to me.  Although this is true, a brief (very brief) summary is listed below:

1st Session:  HWF302: Design Powerful Workflows with SharePoint Designer

Speaker:  Asif Rehmani

For more information on this subject:  http://office.microsoft.com/en-us/sharepointdesigner/CH100667661033.aspx

3rd Session:  HEC306: Why Content Types Are Your Friend

Speaker:  Sahil Malik

For more information on this subject:   http://msdn.microsoft.com/en-us/library/ms472236.aspx

Another post about the additional sessions (with subject matter not as familiar to me) at Dev Con 2008 day 3 will be added shortly...

Read More

Topics: SharePoint, MOSS 2007, Workflow, SQL, visual studio

And then there was the second day at Dev Con 2008...

Posted by Janetra Meyers on Wed, Nov 12, 2008 @ 14:11 PM

Day Two at Dev Con 2008 (11 Nov 08)

Read More

Topics: moss, SharePoint, Testing, Silverlight, visual studio team system

Dev Con 2008 Keynote Address

Posted by Janetra Meyers on Tue, Nov 11, 2008 @ 11:11 AM

Well the first Keynote address of Dev Con 2008 was eventful enough for a blog post.  The first speaker was Britt Johnson and he talked about the history of database technology.  He then addressed the new and exciting features of SQL Server 2008.  Real world examples of SQL Server 2008 in use were given, with its use with Pan-Starrs  given the spotlight.  Apparently, our existence as a species is dependent on this system as it observes the whole sky and alerts us to oncoming asteroids.  The Pan-Starrs satellite system collects about a terabyte a data every night and SQL Server provides the backend ability to accommodate this data.  Britt Johnson also highlighted Visual Team Studio Team System 2008, but his main focus was on SQL Server 2008.  The top 5 lists of usable SQL Server 2008 features were broken down into two categories, Developers and IT Professionals. 

List: For Developers - 1) Policy Based Management 2) Resource Governor 3) Query Plan Freezing 4) Backup Compression 5) Performance Data Collection

For IT Professionals - 1) Spatial Data Support 2) Report Builder Enhancements 3) ADO.NET Entity Framework 4) Change Data Capture 5) Table Value Parameters

The next presenters Demoed Spatial Data Support using Mapping with SQL Server 2008 as the backend database.  The most impressive part of this demonstration was the ability to query data points of map without having to instantiate the database.  The Schema Developer ability in SQL Server 2008 gives developers the ability compile before deployment.

The next part of the keynote speech focused on Business Intelligence (BI) with search collaboration content management, Excel, and Performance Point.  SQL Server 2008's improved Reporting Services was demoed and provided many new features to assist developers and IT pros.  A new technology called Tablix (Table + Matrix) is included on Report Designer for SQL Server.  A demo with Tablix using Report Builder 2.0 (includes Office Ribbon Integration) showed how collaboration with Model Data, Query Data, Free Data, SQL Services (SQL Data Services is the foundation), and Cloud Services (Windows Azure ) have incredibly improved Reporting Services while allowing for more detailed data reports.

All in all, it was a good keynote address and many new and exciting things with SQL Server technology have emerged or are emerging.

Read More

Topics: SharePoint, asp.net, sql server, visual studio

First blog post from Dev Con 2008

Posted by Janetra Meyers on Mon, Nov 10, 2008 @ 11:11 AM

I received a free backpack from Dev Con. My backpack is a nice black and red color and full of developer goodies.

Backpack Items:

A Show Guide - this lists all the happenings in the Expo Hall (includes vendors)

A Schedule Guide - self-explanatory

Free Magazines - All .Net Magazines (MSDN, Code Focus, ASP.Net, etc...)

Additional notes: The keynote address on SQL 2008 is tonight and I'll have more to blog about during and after the address.

Read More

Topics: SharePoint, asp.net, devconnections, sql server