Eating your own dog food

From Vero - Wikipedia
Jump to navigation Jump to search

Template:Short description Template:Use dmy dates

Eating your own dog food or "dogfooding" is the practice of using one's own products or services.<ref>Template:Cite news</ref> This can be a way for an organization to test its products in real-world usage using product management techniques. Hence dogfooding can act as quality control, and eventually a kind of testimonial advertising. Once in the market, dogfooding can demonstrate developers' confidence in their own products.<ref>Template:Cite web</ref><ref name="dvorak">Template:Cite news</ref>

Origin of the term

In 2006, Warren Harrison, the Editor-in-Chief of IEEE Software recounted that in the 1970s television advertisements for Alpo dog food, spokesperson and actor Lorne Greene pointed out that he fed Alpo to his own dogs. Another possible origin he remembered was that the president of Kal Kan Pet Food was said to eat a can of his dog food at annual shareholders' meetings.<ref name= ieee>Template:Cite journal</ref><ref>Template:Citation</ref>

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.<ref>Template:Cite book</ref><ref>Template:Cite news</ref>

Real world usage

InfoWorld commented that this needs to be a transparent and honest process: "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."<ref name="yager">Template:Cite news</ref> 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,<ref name=dvorak/><ref name= testing/> which gives management a sense of how the product might be used—all before launch to consumers.<ref name= testing>Template:Cite book</ref> 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.Template:Citation needed

The risks of public dogfooding, specifically that a company may have difficulties using its own products, may reduce the frequency of publicized dogfooding.Template:R

Examples

In February 1980, Apple Computer president Michael Scott wrote a memo announcing "Effective Immediately!! No more typewriters are to be purchased, leased etc., etc. […] We believe the typewriter is obsolete. Let's prove it inside before we try and convince our customers."<ref>Template:Cite web</ref> He set a goal to remove all typewriters from the company by 1 January 1981.<ref>Template:Cite news</ref>

By 1987, Atari Corp. was in the process of using the Atari ST throughout the company.<ref name="friedland198703">Template:Cite news</ref>

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. The software 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.<ref>Template:Cite book</ref><ref>Template:Cite book</ref> 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.Template:Citation needed 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".<ref>Template:Cite news</ref> InfoWorld argued that "Microsoft's use of Windows for its high-traffic operations tipped many doubters over to Windows' side of the fence."<ref>Template:Cite news</ref>

Template:Quote box

Microsoft's internal email system initially ran on Xenix.<ref name="flynn19870223">Template:Cite magazine</ref> The only employees using Microsoft Mail worked on the software itself, and used it as a client for Xenix mail servers.Template:R When asked why Microsoft used Unix, it publicly moved to using Microsoft Exchange.<ref>Template:Cite news</ref> During the 1993-1996 migration, the internal test environment was codenamed "Dogfood".<ref name=xenix1>Template:Cite web</ref> In 1997, an email storm known as the Bedlam DL3<ref name="Me Too">Template:Cite web</ref> 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<ref name="Bedlam all over again">"It's Bedlam all over again..." Larry Osterman's WebLog. 18 September 2006 in blogs.msdn.com</ref> was handled perfectly by the system.

In 1999, Hewlett-Packard staff referred to a project using HP's own products as "Project Alpo" (referring to a brand of dog food).<ref>Template:Cite news</ref> Around the same time, Mozilla also practised dogfooding under that exact name.<ref>Template:Cite web</ref>

Government green public procurement that allows testing of proposed environmental policies has been compared to dogfooding.<ref>Template:Cite book</ref>

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.<ref>Template:Cite web</ref><ref>Template:Cite news</ref> The license label was followed by the message "(Shh! – Internal Dogfood)" that appeared on all YouTube videos lacking commercial licensing.<ref>Template:Cite web</ref>Template:Failed verification A YouTube employee confirmed that this referred to products that are tested internally.<ref>Template:Cite web</ref>

Oracle Corporation stated that Template:As of it "runs Oracle Linux with more than 42,000 servers [to] support more than 4 million external users and 84,000 internal users. More than 20,000 developers at Oracle use Oracle Linux".<ref name="oracle201610">Template:Cite web</ref>

After the CrowdStrike outages in July 2024, CEO Adam Meyers testified before the US Congress that "dogfooding" (increasing its internal testing before deployment) was one measure the company had put in place to prevent future problems.<ref>Template:Cite web</ref>

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.<ref name=testing/> 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."<ref>Template:Cite news</ref> Dogfooding may happen too early to be viable, and those forced to use the products may get used to applying workarounds or may assume that someone else has reported the problem. 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,<ref name=testing/> or at its extreme to "Not Invented Here" syndrome, i.e. only using internal products.<ref name=ieee/>

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:Template:Blockquote

Alternative terms

In 2007, Jo Hoppe, the CIO of Pegasystems, said that she uses the alternative phrase "drinking our own champagne".<ref>Template:Cite web</ref> 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.<ref>Template:Cite web</ref> 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".<ref>Template:Cite web</ref> 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".<ref>Template:Cite web</ref>

See also

References

Template:Reflist