Talk:Small matter of programming

My exposure with "SMOP" comes from the early 70s, and I'm more familiar with it being used to indicate that a feature/task is not conceptually complex, and the speaker believes that the person requesting the feature should simply sit down and write the code if it's all that important. Ie, it's not an indication that the effort required would be particularly great, but rather than the requesting party simply needs to do his own homework rather than asking someone else to do it or looking for a pre-packaged solution.drh (talk) 02:30, 14 May 2014 (UTC)


 * That may be, but my own experience, as a programmer who has won multiple international awards for my work on BIG SCIENCE projects, is that I heard it used by managers who were trying to coerce coders to initiate scope creep: "What we're asking for isn't a big deal, it's just a small matter of programming". No coder I know has suggested to a manager that the manager write any code - That would be ridiculous. — Preceding unsigned comment added by 2600:1700:6AE5:2510:0:0:0:24 (talk) 17:40, 5 April 2024 (UTC)

Merger proposal
Simple matter of software is an article with multiple issues. Since "Simple matter of software" and "Small matter of software" are alternate formulations synonymous with "Simple matter of programming" and "Small matter of programming", any relevant content of Simple matter of software (e.g., Coles reference) should be merged into Small matter of programming, instead of fixing the tagged issues. IveGoneAway (talk) 21:01, 2 August 2017 (UTC) IveGoneAway (talk) 21:27, 2 August 2017 (UTC)