Small matter of programming: Difference between revisions

Revision as of 16:54, 18 July 2021

Latest revision as of 06:17, 19 June 2025

(4 intermediate revisions by 4 users not shown)

Line 1:

{{short description|Ironic phrase in software development}}

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 points out that although the change is clearly possible, it would be very laborious to actually perform. It often implies that the person proposing the feature underestimates its cost.

==Definitions==

Line 16:

Example: "It's easy to change a FORTRAN compiler to compile COBOL as well; it's just a small matter of programming."}}

The IBM Jargon Dictionary defines SMOP as:<ref>{{cite web|url=https://comlayhavantcivicsociety.netuk/wp-content/uploads/2019/05/ibmjarg.pdf|quote=SMOP|title=''IBM Jargon Dictionary, Tenth Edition''|publisher=[[IBM]]|year=1990|page=53|access-date=22 March 2019}}</ref>

{{quote|'''SMOP''' (''smop'') ''n.'' Something quite possible, but requiring unavailable resources to achieve. "Why isn't that function available in the program?" − "It's just a Simple Matter Of Programming". (The implication being that, given a few person-centuries, all things are possible.) Also '''SMOUP''' (''smoop''), a Simple Matter Of Micro-Programming (if handwritten, using a Greek [[Mu_(letter)|mu]]). See also ''how hard would it be.''}}

Line 30:

==See also==

* {{annotated link|Ninety–ninety rule}}

* [[Ninety-ninety rule]]

* [[{{annotated link|Hofstadter's law]]}}

* [[{{annotated link|Hard–easy effect]]}}

* [[{{annotated link|Planning fallacy]]}}

==References==

{{reflist}}

[[Category:Anti-patterns]]

[[Category:Computer jargon]]

[[Category:Software project management]]