This is funny, but I think it misstates the real problem. This is what would really happen:<p>King: &quot;Make me a toaster.&quot;<p>Software developer: <i>makes toaster</i><p>King: &quot;Okay, that&#x27;s great, but could you also make it scramble eggs? It should just be a small change, right?&quot;<p>Software developer: <i>adds egg scrambling module</i><p>King: &quot;Actually, could the eggs be soft boiled instead?&quot;<p>etc.<p>In other words, OO and other programming abstractions arose precisely because we actually do need to deal with changing requirements, all the time.