Meatware: Difference between revisions

220 bytes added ,  10 July 2020
no edit summary
No edit summary
No edit summary
Line 30: Line 30:


===Humans aren’t perfect===
===Humans aren’t perfect===
Nor should you underestimate the [[meatware]]’s capacity to misunderstand the possibility presented by technology. This is much needed advice for those who write [[playbooks]]. It’s all very well having clever software that can read your confidentiality agreements and mark them up according to a [[playbook]], that is to say, but if the sad sack who wrote the playbook believes — and it is a sad fact of life that many of our learned colleagues do believe this, my friends — that pointless back-and-forths on low-value agreements in the name of procedural perfection ''because you can'' is a good idea, then your clever software will only allow you to waste the organisation’s time and money a little more efficiently and comprehensively than you were already doing by yourself beforehand.
Nor should you underestimate the [[meatware]]’s capacity to misunderstand the possibility presented by technology. This is much needed advice for those who write [[playbook]]s. It’s all very well having clever software that can read your [[confidentiality agreement]]s and mark them up according to a [[playbook]], that is to say, but if the sad sack who wrote the [[playbook]] believes — and it is a sad fact of life that many of our learned colleagues do, my friends — that [[tedious]] back-and-forths on low-value agreements — you know, the “''directors, {{insert|officers,}} employees, agents, {{insert|contractors}} and {{insert|professional}} advisers {{insert|(as the case may be)}}''” kind of mark-up — in the name of procedural perfection ''because you can'' is a good idea, then your expensive new [[Saas]] [[natural language processing]] app will only allow you to waste the organisation’s time and money a little more efficiently and comprehensively than you were already doing by yourself.