82,927
edits
Why is legaltech so disappointing?: Difference between revisions
no edit summary
Amwelladmin (talk | contribs) No edit summary |
Amwelladmin (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{a|tech|}}:''“Unlike a covered call, which is about promising to sell what you actually own, a naked call is about promising to sell what you don’t actually own. | {{a|tech|[[File:Tipp-Ex.jpg|thumb|center|450px|For your monitor, sir.]]}}:''“Unlike a covered call, which is about promising to sell what you actually own, a naked call is about promising to sell what you don’t actually own. | ||
:''Like wearing a nice sweatshirt, learning the lingo, and hanging out at a hackerspace with a code editor open, looking the part, but only scrambling to learn a new skill if somebody actually hints they might want to hire you if their funding comes through in a few months. | :''Like wearing a nice sweatshirt, learning the lingo, and hanging out at a hackerspace with a code editor open, looking the part, but only scrambling to learn a new skill if somebody actually hints they might want to hire you if their funding comes through in a few months. | ||
| Line 28: | Line 28: | ||
*'''Don't be a [[rentier]]''': How do I make money off something which is basically a simple idea that doesn’t require a lot of maintenance? The whole point of this tech is it is meant to be labour saving, right? I can’t do it per unit - the whole point is to eliminate the cost of having meatware do manual, repetitive tasks, and — once you have set it up — there is no actual cost to having a machine do it. So trying to act like a [[rentier]] is (a) a dick move and (b) is going to get you killed, because your big idea isn’t that flash, and someone will do it, and undercut you. See {{author|Roger Martin}}’s the {{br|The Design of Business: Why Design is the Next Competitive Advantage}} | *'''Don't be a [[rentier]]''': How do I make money off something which is basically a simple idea that doesn’t require a lot of maintenance? The whole point of this tech is it is meant to be labour saving, right? I can’t do it per unit - the whole point is to eliminate the cost of having meatware do manual, repetitive tasks, and — once you have set it up — there is no actual cost to having a machine do it. So trying to act like a [[rentier]] is (a) a dick move and (b) is going to get you killed, because your big idea isn’t that flash, and someone will do it, and undercut you. See {{author|Roger Martin}}’s the {{br|The Design of Business: Why Design is the Next Competitive Advantage}} | ||
*'''Remember the [[meatware]]''': If you convert your [[Meatware|user]] experience from “answering nuanced legal questions” into “completing a mandatory questionnaire”, you have lost. [[Document assembly]] applications: I’m talking to you. You are trying to make humans behave like machines. That is stupid. ''Humans aren’t good at emulating machines''. Humans are better than machines precisely because they aren’t machine-like. If you have reduced your process to a rules-based questionnaire, ''you don’t need humans at all''. Get a machine to do it - hook it up to the trading system directly. | *'''Remember the [[meatware]]''': If you convert your [[Meatware|user]] experience from “answering nuanced legal questions” into “completing a mandatory questionnaire”, you have lost. [[Document assembly]] applications: I’m talking to you. You are trying to make humans behave like machines. That is stupid. ''Humans aren’t good at emulating machines''. Humans are better than machines precisely because they aren’t machine-like. If you have reduced your process to a rules-based questionnaire, ''you don’t need humans at all''. Get a machine to do it - hook it up to the trading system directly. | ||
===What reg tech ''should'' do=== | ===What reg tech ''should'' do=== | ||
The aim of [[reg tech]] should be to work with lawyers and to respect this divide between things machines are good at (accurately, cheaply and quickly following orders) and things the meatware is good at (interpretation; judgment; lateral thinking; dealing with conundrums; figuring out what to do when the instructions run out), and to divide labour accordingly: | The aim of [[reg tech]] should be to work with lawyers and to respect this divide between things machines are good at (accurately, cheaply and quickly following orders) and things the meatware is good at (interpretation; judgment; lateral thinking; dealing with conundrums; figuring out what to do when the instructions run out), and to divide labour accordingly: | ||