3 ms·
So is this just "trying to formalize and build automation for a/some business process[es] reveals ambiguity in people's mental models about that/those process[e
by majormajor 3y ago
So is this just "trying to formalize and build automation for a/some business process[es] reveals ambiguity in people's mental models about that/those process[es]"?
I'm still not sure that this is unique to programming. Lawyers seem like the closest immediately parallel - I've seen lawyers in this same sort of "you're all asking me individually-reasonable questions but you have hidden assumptions that disagree with each other which would render the legal advice I give any one of you somewhat useless or harmful" situation in a large company.
And that seems like very much the same sort of "you're asking for a technical answer to an ill-defined problem" issue.
Medicine has its own "this is the standard playbook, but everybody is unique, and sometimes it's going to be harmful for various reasons, and a good doctor has to be able to spot and navigate that and go off-book" stuff too.
Code and medicine both have the "hardest" intersections of these areas, IMO - legal matters will ultimately get decided by people, not by machines or still-pretty-mysterious biological processes.
- sdiupIGPWEfh 3y agoI think you are correct that it's not completely unique to programming, but it seems understandable why some might feel otherwise. With the modern world looking to apply code based solutions everywhere imaginable, developers will tend to uncover such conflicts in problem areas that law and medicine will never interface with. Lawyers and doctors are also more likely to hold societal positions of respect and authority that most developers will never possess, so they don't have to get drawn into fruitless arguments quite the same way.