Small matter of programming: Difference between revisions

Content deleted Content added
quote jargon file; not really a stub
No edit summary
Line 2:
 
When used in computer science, a SMOP is the smallest unit of software engineering effort which can be allocated at the onset of a project. A SMOP has the curious property that its size increases exponentially as the project progresses. It is not uncommon for a SMOP to grow to man-decades. There is anecdotal evidence of SMOPs encompassing man-centuries.
 
The implication of using itthe phrase is either
* to remind one's colleagues that ''every'' design change seems like a small matter of programming, until implementation starts, or
* to reassert by irony one's awareness of the danger of underestimating required effort.
 
The [[Jargon File]] describes a SMOP<ref>[http://www.catb.org/jargon/html/S/SMOP.html Simple Matter of Programming] in the [[Jargon File]]</ref> as:
Line 9 ⟶ 13:
 
Note that SMOPs are often logarithmic in nature. Each additional SMOP adds another order of magnitude onto calendar time.
 
The implication of using it is either
* to remind one's colleagues that ''every'' design change seems like a small matter of programming, until implementation starts, or
* to reassert by irony one's awareness of the danger of underestimating required effort.
 
==References==