Antiexemplar

E Vicipaedia
Salire ad: navigationem, quaerere

Antiexemplar, in ingeniaria programmaturae sive in operibus societatis vel commercii, est exemplar descriptionis quod saepe adhibetur, quamquam in usu inutile sit vel in errorem ducat.[1][2] Nomen anno 1995 ab Andrea Koenig,[3] per Design Patterns motus, librum Gregis Quaternorum qui notionem exemplarium descriptionis in arte programmandi evolvit, excogitatum est. Nomen post tres annos late per librum AntiPatterns diffusum est, qui sensum nominis praeter artem descriptionis programmaticae in interactionem socialem extendit.

Vide etiam[recensere | fontem recensere]

Notae[recensere | fontem recensere]

  1. "Exemplaria descriptionis, in Long (2001) relata, sunt 'manifestae, sed falsae, explicationes quaestionum recurrentium'" ("As described in Long (2001), design anti-patterns are 'obvious, but wrong, solutions to recurring problems'"): Budgen, D. (2003). Software design. Harlow, Eng.: Addison-Wesley. p. 225. ISBN 0-201-72219-4  .
  2. Scott W. Ambler (1998). Process patterns: building large-scale systems using object technology. Cantabrigiae: Cambridge University Press. p. 4. ISBN 0-521-64568-9   "common approaches to solving recurring problems that prove to be ineffective. These approaches are called antipatterns."
  3. Koenig, Andrew (March/April 1995). "Patterns and Antipatterns". Journal of Object-Oriented Programming 8 (1): 46–48 ; deinde reimpressus in: Rising, Linda (1998). The patterns handbook: techniques, strategies, and applications. Cantabrigiae: Cambridge University Press. p. 387. ISBN 0-521-64818-1   "Anti-pattern is just like pattern, except that instead of solution it gives something thats looks superficially like a solution, but isn't one."

Bibliographia[recensere | fontem recensere]

Nexus externi[recensere | fontem recensere]


stipula Haec stipula ad technologiam spectat. Amplifica, si potes!