Chris's Wiki :: blog/programming/ProductAndUtilityCode Commentshttps://utcc.utoronto.ca/~cks/space/blog/programming/ProductAndUtilityCode?atomcommentsDWiki2020-06-22T20:52:41ZRecent comments in Chris's Wiki :: blog/programming/ProductAndUtilityCode.From 147.253.3.84 on /blog/programming/ProductAndUtilityCodetag:CSpace:blog/programming/ProductAndUtilityCode:faafa9bb4c985a73fea00413a74709687c1629adFrom 147.253.3.84<div class="wikitext"><blockquote><pre>
If the programmers think its product code and the users think its utility code, you get users angry about the inconvenience of constant updates and change for change's sake.
</pre>
</blockquote>
<p>Say hi to systemd :)</p>
</div>2020-06-22T20:52:41ZBy Anonymous Coward on /blog/programming/ProductAndUtilityCodetag:CSpace:blog/programming/ProductAndUtilityCode:527e188ae684bf4476b855bf1d1b693d8c9e15c6Anonymous Coward<div class="wikitext"><p>I'd suggest that a lot of user dissatisfaction comes from users and programmers disagreeing about whether something ought to be "product" or "utility" code. </p>
<p>If the programmers think its utility code and the users think its product code, you get complaints about the hidebound, sluggish IT department or software vendor getting in the way of people who are trying to get their work done. If the programmers think its product code and the users think its utility code, you get users angry about the inconvenience of constant updates and change for change's sake. My (limited and biased) experience is that the former used to be the more common of these, but nowadays the latter is more prevalent.</p>
</div>2020-06-15T04:25:27Z