Not invented here

From Wikipedia, the free encyclopedia
  (Redirected from Not Invented Here)
Jump to: navigation, search

Not invented here (NIH) aka fatal flaw[1] is a stance adopted by social, corporate, or institutional cultures that avoid using or buying already existing products, research, standards, or knowledge because of their external origins and costs.

The reasons for not wanting to use the work of others are varied, but some can include fear of patent infringement, lack of understanding of the foreign work, an unwillingness to acknowledge or value the work of others, jealousy, or forming part of a wider turf war.[2] As a social phenomenon, this philosophy manifests as an unwillingness to adopt an idea or product because it originates from another culture, a form of tribalism.[3]

The term is normally used in a pejorative sense. The opposite predisposition is sometimes called "proudly found elsewhere" (PFE)[4] or "invented elsewhere".

In computing[edit]

In programming, it is also common to refer to the "NIH syndrome" as the tendency towards reinventing the wheel (reimplementing something that is already available) based on the belief that in-house developments are inherently better suited, more secure, more controlled, quicker to develop, and incur lower overall cost (including maintenance cost) than using existing implementations.

In some cases, software with the same functionality as an existing one is re-implemented just to allow the use of a different software license. One approach to doing so is clean room design.

Reasoning in favor of the NIH approach includes:

  • Third-party components or services sometimes do not live up to expectations when high quality is needed.[5]
  • An entity outside one's own control is a vendor lock-in and a constant threat to business in proportion to the repercussions of losing it.[6]
  • Closed solutions can be perceived as lacking future flexibility.

Some specific approaches can alleviate these drawbacks:

  • An external solution can be taken as a base for one's own development, rather than being used as-is.
  • Control of an external solution can be ensured in case of loss of its supply channel, such as by obtaining its source code.

See also[edit]

References[edit]

  1. ^ Burk, Ron (2009-12-01). "A Brief History of Windows Programming Revolutions". Retrieved 2016-09-25. 
  2. ^ "The Innovation Playbook: A Revolution in Business Excellence", Nicholas J. Webb, Chris Thoen, John Wiley and Sons, 2010, ISBN 0-470-63796-X,
  3. ^ The Cambridge economic history of modern Britain
  4. ^ HBS.edu P&G's New Innovation Model
  5. ^ Joel Spolsky (2001-10-14). "In Defense of Not-Invented-Here Syndrome". Joel on Software. 
  6. ^ "Electronic Arts plays hardball". Retrieved 2008-12-29.