The Chaos Factory: The inside story of corporate IT failure
Have you ever wondered why the website of your bank or phone company is so broken and unusable?
Do you find yourself asking: “How this can be”? What is wrong with these people? Why can’t it just work?
Corporate IT departments are wasting billions of dollars on failed IT projects every year, and it has been this way for decades.
On top of that, consultants have extracted billions more from these companies with project management and methodology solutions that have quite obviously failed to make things any better.
This book, written by an insider with 30 years of experience in the trenches, explains the raw truth that corporate executives have been sweeping under the rug. With simple common sense explanations that cut through the typical gibberish that IT departments use to baffle and confuse, The Chaos Factory will explain in plain language how we got to the place where we are now, and what to do to make it better.
Business managers and shareholders alike will applaud this honest assessment that reveals the real root cause of IT project failure. They will be able to use the information contained in this book to protect themselves and demand better.
Adam has spent more than thirty years programming and managing programmers for some of the largest companies in the world. He has also worked in startups, exposed to the latest technology and the newest methods. He is recognized by his peers for his vision, strategy, and ability to find innovative approaches to intractable situations, and has often been at the forefront of technology, with a track record for recognizing value before others do and picking winners.
It all started in 1984, when he wrote his first commercial program, an optimizing media scheduler for an ad agency. Within 2 years he was architecting and installing Canada’s first ATM-over-fiber LAN implementation at Centennial College of Applied Arts and Technology in Toronto. Over the next ten years he continued to be at the leading edge of technology, responsible for other firsts such as Canada’s first industrial application of UNIX: paint shop automation and process control for General Motors Canada.
In 1994, he committed to design all his applications as web-based applications, correctly anticipating what is now a standard, but a visionary move for the times. He designed and delivered a hosted Software as a Service (SaaS) platform to the Washington D.C. based Employee Relocation Council, a full five years before Salesforce.com made SaaS the business model of choice. He also designed and delivered secure data transfer services for the US Federal Home Loan Mortgage Corporation (Freddie Mac) and the International Air Transport Association (IATA). Adam moved on to become the CTO of IATA, where he launched six successful online businesses between 1998 and 2004.
At this point, after 20 years in technical management positions, Adam developed his skills in business by joining Embrase, a Go To Market agency, where with the founder, he built a positioning practice and prescriptive methodology around the principles described in Crossing the Chasm. Embrase worked with venture capital institutions, helping over 50 startups to find optimal market segments and position themselves for success in them. After 7 years he made the move back to corporate IT, managing software development projects for companies such as Yellow Pages, Bombardier Aerospace, and Bell.
What Adam saw over the next 6 years convinced him that the situation facing corporate IT was dire. That things had worsened, not improved in the years he had been away working with startups. This book is based on what he found out, and how to fix it.
An addendum to my very personal history of programming Programmers today… …do not really know where the language stops and the framework begins. What do I mean by this? Up until about 1988 most programs that a person (like you) would use had been programmed from the ground up by a handful of programmers (often …
Working in a modern day IT shop “Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, but just done by brute force and thousands of slaves.” Alan Kay spoke these words in an interview that he gave to the ACM’s Queue magazine …
CPUs speak only one language; they don’t care what language you write in Programmers tend to make a big deal over the supposed difference between compiled languages and interpreted ones. Or dynamic languages vs. statically typed languages. The conventional wisdom goes like this: A compiled language is stored in machine code and is executed by the …