Small matter of programming: Difference between revisions

Revision as of 15:14, 10 December 2018

Revision as of 05:10, 10 March 2019

Line 1:

<!-- Please do not remove or change this AfD message until the discussion has been closed. -->

{{Article for deletion/dated|page=Small matter of programming|timestamp=20190310051015|year=2019|month=March|day=10|substed=yes|help=off}}

<!-- Once discussion is closed, please place on talk page: {{Old AfD multi|page=Small matter of programming|date=10 March 2019|result='''keep'''}} -->

<!-- End of AfD message, feel free to edit beyond this point -->

In [[software development]], '''small matter of programming''' ('''SMOP''') or '''simple matter of programming''' is a phrase used to ironically indicate that a suggested feature or design change would in fact require a great deal of effort; it often implies that the person proposing the feature underestimates its cost. Such underestimated costs are common during [[Cost estimation in software engineering|cost estimation]], particularly near the beginning of a project. The [[Jargon File]] describes an SMOP<ref>[http://www.catb.org/jargon/html/S/SMOP.html Simple Matter of Programming] ([[Jargon File]], version 4.4.7)</ref> as: