Eating your own dog food

From Wikipedia, the free encyclopedia
  (Redirected from Eat one's own dog food)
Jump to: navigation, search

Eating your own dog food, also called dogfooding, is a slang term used to reference a scenario in which a company uses its own product to validate the quality and capabilities of the product.[1]

Introduction[edit]

Dogfooding can be a way for a company to demonstrate confidence in its own products. The idea is that if the company expects customers to buy its products, it should also be willing to use those products. Hence dogfooding can act as a kind of testimonial advertising.[2][3]

InfoWorld commented that this needs to be transparent and honest: "watered-down examples, such as auto dealers' policy of making salespeople drive the brands they sell, or Coca-Cola allowing no Pepsi products in corporate offices ... are irrelevant."[4] In this sense, a corporate culture of not supporting the competitor is not the same as a philosophy of "eating your own dog food". The latter focuses on the functional aspects of the company's own product. Compare this to fictional cases where Google employees used Microsoft Outlook to execute the functional task of sending emails, or Microsoft employees writing documents with WordPerfect.

One perceived advantage beyond marketing is that dogfooding allows employees to test their company's products in real-life scenarios,[3][5] and gives management a sense of how the product will be used, all before launch to consumers.[5] In software development, the practice of dogfooding with build branches, private (or buddy) builds, and private testing can allow several validation passes before the code is integrated with the normal daily builds. The practice leads to more stable builds,[citation needed] and proactive resolution of potential inconsistency and dependency issues, especially when several developers or teams work on the same product. For example, the websites of the Wikimedia Foundation engage in this sort of build testing, with the public stable branches of MediaWiki being based off public betatesting of the Wikimedia alpha builds between stable releases. In fact, these same builds are made accessible to the public alongside the stable, proven builds so that the public may become as involved in beta testing the MediaWiki software as the official development staff.

The risks of public dogfooding, specifically that a company may have difficulties using its own products, may reduce the frequency of publicized dogfooding.[6]

Origin of the term[edit]

The editor of IEEE Software recounts that in the 1970s television advertisements for Alpo dog food, Lorne Greene pointed out that he fed Alpo to his own dogs. Another possible origin is the president of Kal Kan Pet Food, who was said to eat a can of his dog food at shareholders' meetings.[7]

In 1988, Microsoft manager Paul Maritz sent Brian Valentine, test manager for Microsoft LAN Manager, an email titled "Eating our own Dogfood", challenging him to increase internal usage of the company's product. From there, the usage of the term spread through the company.[8][9]

Examples[edit]

"Microsoft's use of Windows and .NET would be irrelevant except for one thing: Its software project leads and on-line services managers do have the freedom to choose."

Tom Yager, InfoWorld[4]

Apple Computer president Michael Scott in 1980 wrote a memo announcing that "EFFECTIVE IMMEDIATELY!! NO MORE TYPEWRITERS ARE TO BE PURCHASED, LEASED, etc., etc." by the computer company, with a goal to eliminate typewriters by 1 January 1981.[10] Atari Corp. by 1987 was in the process of using the Atari ST throughout the company.[11]

The development of Windows NT at Microsoft involved over 200 developers in small teams, and it was held together by Dave Cutler's insistence in February 1991 on dogfooding, developing the operating system on computers running on NT using a daily build, initially text only, then with graphics, and finally with networking. It was initially crash prone, but the immediate feedback of code breaking the build, the loss of pride, and the knowledge of impeding the work of others were all powerful incentives.[12][13] Infoworld reported in 2005 that a tour of Microsoft's network operations center "showed pretty much beyond a reasonable doubt that Microsoft does run its 20,000-plus node, international network on 99 percent Windows technology, including servers, workstations, and edge security."[14] InfoWorld argued that "Microsoft's use of Windows for its high-traffic operations tipped many doubters over to Windows' side of the fence".[15] In the mid-1990s, Microsoft's internal email system was initially developed around Unix. When asked why, they publicly moved to using Microsoft Exchange.[16] An email storm known as the Bedlam DL3[17] incident in 1997 allowed Microsoft to build more robust features in Microsoft Exchange Server to avoid lost and duplicate emails and network and server down-time, although dogfooding is rarely so dramatic. A second email storm in 2006[18] was perfectly handled by the system.

In 1999, Hewlett-Packard staff referred to a project using HP's own products as "Project Alpo".[19]

When Time Warner merged with AOL in 2001, AOL's email system was adopted by the new AOL Time Warner, resulting in lost emails and productivity. Use of the system was discontinued.[5][20]

Government green public procurement that allows testing of proposed environmental policies has been compared to dogfooding.[21]

On 1 June 2011, YouTube added a license feature to its video uploading service allowing users to choose between a standard or Creative Commons license.[22][23] The license label was followed by the message (Shh! - Internal Dogfood) that appeared on all YouTube videos lacking commercial licensing.[24] A YouTube employee confirmed that this referred to products that are tested internally.[25]

Criticism and alternative terms[edit]

Forcing those who design products to actually use and rely on them is often thought to improve quality and usability, but software developers may be blind to usability and may have knowledge to make software work that an end user will lack.[5] Microsoft's chief information officer noted in 2008 that, previously, "We tended not to go through the actual customer experience. We were always upgrading from a beta, not from production disk to production disk."[26] Dogfooding may happen too early to be viable, and those forced to use the products may assume that someone else has reported the problem or they may get used to applying workarounds. Dogfooding may be unrealistic, as customers will always have a choice of different companies' products to use together, and the product may not be being used as intended. The process can lead to a loss of productivity and demoralisation,[5] or at its extreme to "Not Invented Here syndrome"; i.e., only using internal products.[7]

In 2007, the CIO of Pegasystems said that she uses the alternate phrase "drinking our own champagne".[27] Novell's head of public relations Bruce Lowry, commenting on his company's use of Linux and OpenOffice.org, said that he also prefers this phrase.[28] In 2009, the new CIO of Microsoft, Tony Scott, argued that the phrase "dogfooding" was unappealing and should be replaced by "icecreaming", with the aim of developing products as "ice cream that our customers want to consume."[29]

See also[edit]

References[edit]

  1. ^ Miguel Helft (December 12, 2009). "Google Appears Closer to Releasing Its Own Phone". New York Times. Retrieved 2009-12-12. "On Saturday morning, Google confirmed that it was testing a new concept in mobile phones, writing in a blog post that it was 'dogfooding' the devices, an expression that comes from the idea that companies should eat their own dog food, or use their own products." 
  2. ^ "Microsoft tests its own 'dog food'". Tech News on ZDNet. Retrieved 2009-11-14. [dead link]
  3. ^ a b Dvorak, John C. (15 November 2007). "The Problem with Eating Your Own Dog Food". PC Magazine. Retrieved 17 May 2010. [dead link]
  4. ^ a b Yager, Tom (2003-05-30). "If it's good enough for Fido …". Retrieved 2013-06-15. 
  5. ^ a b c d e Ash, Lydia (2003). The Web testing companion: the insider's guide to efficient and effective tests. ITPro collection. Wiley. p. 17. ISBN 0-471-43021-8. 
  6. ^ Yager, Tom (30 May 2003). "If it's good enough for Fido … Vendors need to follow Microsoft's playbook". Developer World. InfoWorld. Retrieved 17 May 2010. 
  7. ^ a b Harrison, Warren (May–June 2006). "From The Editor: Eating Your Own Dog Food". IEEE Software (IEEE) 23 (3): 5–7. doi:10.1109/MS.2006.72. 
  8. ^ Inside Out: Microsoft—In Our Own Words (ISBN 0446527394)
  9. ^ Brodkin, John (4 September 2009). "VMworld 2009: Virtualization, controversy and eating your own dog food". Network World. Retrieved 17 May 2010.  Quote: "[Paul] Maritz also poked fun at himself by claiming that one of his only contributions to the IT world is coining the commonly used "eat your own dog food" phrase. "You can read about it on Wikipedia, so it must be true," Maritz said.
  10. ^ Ditlea, Steve (1981-10-01). "An Apple On Every Desk". Inc. Retrieved March 6, 2011. 
  11. ^ Friedland, Nat (1987-03). "Today's Atari Corp. | A close-up look inside". Antic. p. 30. Retrieved 4 July 2014. 
  12. ^ Bolman, Lee G.; Deal, Terrence E. (2003). Reframing organizations: artistry, choice, and leadership. Jossey-Bass business & management series; Jossey-Bass higher and adult education series (3 ed.). John Wiley and Sons. p. 64. ISBN 0-7879-6426-3. 
  13. ^ Zachary, Pascal G. (2009). Showstopper! the Breakneck Race to Create Windows Nt and the Next Generation. E-reads/E-rights. p. 135. ISBN 0-7592-8578-0. 
  14. ^ Rist, Oliver (29 December 2005). "The Microsoft machine churns on". InfoWorld. Retrieved 17 May 2010. 
  15. ^ "If it's good enough for Fido...". 
  16. ^ Cringely, Robert X. (14 August 2000). "Microsoft forgoes eating dog food in favor of Unix as Bobby sneaks a burger". InfoWorld. Retrieved 17 May 2010. 
  17. ^ "Me Too!" The Exchange Team Blog. April 8, 2004 in MSexchangeteam.com
  18. ^ "It's Bedlam all over again..." Larry Osterman's WebLog. September 18, 2006 in blogs.msdn.com
  19. ^ Field, Tom (15 August 1999). "Unleash innovation". CIO. Retrieved 17 May 2010.  Note: Alpo is a brand of dog food.
  20. ^ Stellin, Susan (16 May 2001). "Cultures Clash as AOL Switches to Its E-Mail". The New York Times. Retrieved 8 August 2013. 
  21. ^ Johnstone, Nick (2003). The environmental performance of public procurement: issues of policy coherence. Organisation for Economic Co-operation and Development. ISBN 92-64-10155-1. 
  22. ^ Peterson, Stace (2 June 2011). "YouTube and Creative Commons: raising the bar on user creativity". The Official YouTube Blog. 
  23. ^ LaPine, John (2 June 2011). "(Shh! – Internal Dogfood) – YouTube introduces Creative Commons Attribution license". GaGaGadget.com. Retrieved 2 June 2011. 
  24. ^ "YouTube - Copyright Education - Creative Commons". Retrieved 1 June 2011. 
  25. ^ "YouTube Help Forum". Retrieved 2 June 2011. 
  26. ^ Sperling, Ed (15 December 2008). "Eating Their Own Dog Food". Forbes. Retrieved 17 May 2010. 
  27. ^ "Pegasystems CIO Tells Colleagues: Drink Your Own Champagne". Trendline on CIO.com. Retrieved 2007-07-05. 
  28. ^ "Novell comments on its transition to Linux desktops". DesktopLinux. Ziff Davis Enterprise. 13 April 2006. Retrieved 17 May 2010. 
  29. ^ "Microsoft CIO on a mission to make ice cream out of dog food". TechFlash. November 10, 2009. Retrieved 2010-05-02. 

External links[edit]