Thanks for the feedback.  I find it generally interesting because most technical folks I&#x27;ve talked to have the same attitude I do.  (Upvoted.)<p>&gt; What is it about information machines (as opposed to humans) that make them unable to handle ambiguity?<p>Of course, if designed for ambiguity, information machines can handle it.<p>But in my experience, solving a problem with software first involves defining the problem.  Most problems are &quot;squishy&quot;, in that they are ill defined.  The end user has needs and knows those needs, but hasn&#x27;t thought through all the ramifications of automation.<p>I&#x27;ve started a requirements process many a time with the question: &quot;what do you want this to do&quot;, and then diving down to specify each behavior, including critical path functionality, error conditions, alternate paths, roles in the system, performance, timeframes, and other attributes.  All of these are fundamental pieces of automating information flow, but aren&#x27;t typically considered by a non technical person.  Hence my use of the term &quot;squishy&quot;.  (I wrote a blog post in 2003 about how software crystallizes business processes: <a href="http:&#x2F;&#x2F;www.mooreds.com&#x2F;wordpress&#x2F;archives&#x2F;46" rel="nofollow">http:&#x2F;&#x2F;www.mooreds.com&#x2F;wordpress&#x2F;archives&#x2F;46</a> )<p>And I don&#x27;t know of any software process that can handle that.  Even tools designed for non developers like Excel and Zapier force users to go through edge cases.<p>Finally, I&#x27;m certainly no expert on some of the new AI technologies that might be game changers. (I did enjoy reading The Master Algorithm, which talks about the schools of AI and some of the achievements.)