Eating your own dog food

Eating your own dog food, also called dogfooding, occurs when an organization uses its own product.[1] This can be a way for an organization to test its products in real-world usage. Hence dogfooding can act as quality control, and eventually a kind of testimonial advertising. Once in the market, dogfooding demonstrates confidence in the developers' own products.[2][3]

Real world utilization

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.

Dogfooding allows employees to test their company's products in real-life situations; a perceived, but still controversial, advantage beyond marketing,[3][5] which gives management a sense of how the product might be used—all before launch to consumers.[5] In software development, dogfooding can occur in multiple stages: first, a stable version of the software is used with just a single new feature added. Then, multiple new features can be combined into a single version of the software and tested together. This allows several validations before the software is released. The practice enables proactive resolution of potential inconsistency and dependency issues, especially when several developers or teams work on the same product.

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

Origin of the term

In 2006, the editor of IEEE Software recounted 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 he remembers is from the president of Kal Kan Pet Food, who was said to eat a can of his dog food at shareholders' meetings.[6]

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.[7][8]

Dave Cutler's February 1991 insistence on dogfooding in development of Windows NT at Microsoft was documented in Pascal Zachary's 1994 book, Showstopper! The Breakneck Race to Create Windows NT and the Next Generation at Microsoft. Microsoft developed the operating system on computers running NT daily builds, initially text only, then with graphics, and finally with networking.

There is also a British expression "Dog's Breakfast", which refers to making such a mess out of something (eg dinner) that it is unappealing and barely usable. In this context, "Eating Our Own Dogfood" means you will not run away from unpleasant work. Instead of "going out to dinner" you stay and choke down the mess -- thus making it disappear. It is a metaphor for the tedious and unpleasant work of debugging a nearly finished product.[9]

Examples

The development of Windows NT at Microsoft involved over 200 developers in small teams, and it was held together by Dave Cutler's February 1991 insistence on dogfooding. Microsoft developed the operating system on computers running NT daily builds. 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 motivators.[10][11] Windows developers would typically dogfood or self-host Windows starting from the early (alpha) builds, while the rest of the employees would start from the more stable beta builds that were also available to MSDN subscribers. In 2005, Infoworld reported 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".[12] InfoWorld argued that "Microsoft's use of Windows for its high-traffic operations tipped many doubters over to Windows' side of the fence."[13]

"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]

In the mid-1990s, Microsoft's internal email system was initially developed around Unix. When asked why, they publicly moved to using Microsoft Exchange.[14] In 1997, an email storm known as the Bedlam DL3[15] incident made Microsoft build more robust features into 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[16] was handled perfectly by the system.

In 1999, Hewlett-Packard staff referred to a project using HP's own products as "Project Alpo".[17] Around the same time, Mozilla also practised dogfooding under that exact name.[18]

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

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.[20][21] The license label was followed by the message (Shh! - Internal Dogfood) that appeared on all YouTube videos lacking commercial licensing.[22] A YouTube employee confirmed that this referred to products that are tested internally.[23]

Criticisms and support

Forcing those who design products to actually use and rely on them is sometimes 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."[24] 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 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.[6]

In 1989, Donald Knuth published a paper recounting lessons from the development of his TeX Typesetting software, in which the benefits of the approach were mentioned:

Thus, I came to the conclusion that the designer of a new system must not only be the implementor and the first large-scale user; the designer should also write the first user manual. The separation of any of these four components would have hurt TeX significantly. If I had not participated fully in all these activities, literally hundreds of improvements would never have been made, because I would never have thought of them or perceived why they were important.

— Donald E. Knuth, "The Errors Of TeX"[25]

Alternative terms

In 2007, Jo Hoppe, the CIO of Pegasystems, said that she uses the alternative phrase "drinking our own champagne".[26] 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.[27] 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".[28] A less controversial and common alternative term used in some contexts is self-hosting, where developers' workstations would, for instance, get updated automatically overnight to the latest daily build of the software or operating system on which they work. Developers of IBM's mainframe operating systems have long used the term "eating our own cooking".

See also

References

  1. ↑ Miguel Helft (December 12, 2009). "Google Appears Closer to Releasing Its Own Phone". The 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. Archived from the original on June 21, 2008. Retrieved 2009-11-14.
  3. 1 2 Dvorak, John C. (15 November 2007). "The Problem with Eating Your Own Dog Food". PC Magazine. Archived from the original on June 28, 2009. Retrieved 17 May 2010.
  4. 1 2 3 Yager, Tom (2003-05-30). "If it's good enough for Fido …". InfoWorld. Retrieved 2013-06-15.
  5. 1 2 3 4 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. 1 2 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.
  7. ↑ Inside Out: Microsoft—In Our Own Words ( ISBN 0446527394)
  8. ↑ 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.
  9. ↑ https://en.wiktionary.org/wiki/dog%27s_breakfast
  10. ↑ 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.
  11. ↑ 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.
  12. ↑ Rist, Oliver (29 December 2005). "The Microsoft machine churns on". InfoWorld. Retrieved 17 May 2010.
  13. ↑ "If it's good enough for Fido..."
  14. ↑ 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.
  15. ↑ Larry Osterman (8 April 2004). "Me Too!". Microsoft Exchange Team weblog. Microsoft.
  16. ↑ "It's Bedlam all over again..." Larry Osterman's WebLog. September 18, 2006 in blogs.msdn.com
  17. ↑ Field, Tom (15 August 1999). "Unleash innovation". CIO. Retrieved 17 May 2010. Note: Alpo is a brand of dog food.
  18. ↑ "15927 – [BETA][DOGFOOD]No proxy authentication". bugzilla.mozilla.org. Retrieved 2017-02-08.
  19. ↑ 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.
  20. ↑ Peterson, Stace (2 June 2011). "YouTube and Creative Commons: raising the bar on user creativity". The Official YouTube Blog.
  21. ↑ LaPine, John (2 June 2011). "(Shh! – Internal Dogfood) – YouTube introduces Creative Commons Attribution license". GaGaGadget.com. Retrieved 2 June 2011.
  22. ↑ "YouTube - Copyright Education - Creative Commons". Retrieved 1 June 2011.
  23. ↑ "YouTube Help Forum". Retrieved 2 June 2011.
  24. ↑ Sperling, Ed (15 December 2008). "Eating Their Own Dog Food". Forbes. Retrieved 17 May 2010.
  25. ↑ "The Errors Of TeX", SOFTWARE-PRACTICE AND EXPERIENCE, VOL. 19(7), JULY 1989, pp 622
  26. ↑ "Pegasystems CIO Tells Colleagues: Drink Your Own Champagne". Trendline on CIO.com. Retrieved 2007-07-05.
  27. ↑ "Novell comments on its transition to Linux desktops". DesktopLinux. Ziff Davis Enterprise. 13 April 2006. Archived from the original on 16 June 2011. Retrieved 17 May 2010.
  28. ↑ "Microsoft CIO on a mission to make ice cream out of dog food". TechFlash. November 10, 2009. Retrieved 2010-05-02.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.