This is what happened to lawyers when everyone learned how to read. Then commenced a long evolution of the profession where practitioners did their best to make the law more obscure and to invent as many dirty tricks as possible in order to pull the ladder up and sustain law as a profession through other means of exclusivity than the old education moat.
I have personally coded a system for legal billing, had a variety of direct dealings with the legal system (contracts, etc.), and I live in a household with an attny at a top firm.
I've been surprised by a good number of counter-intuitive things in the law, such that the general rule I've heard repeatedly is that we cannot reason about the law without actually looking at the code in that particular instance — go look it up. This strongly resembles software code - we can assume a bunch of things about how something works, but to really find out, we must read the source code or trace it — go look it up.
Yet I have not found or even heard of a single instance of anything that would remotely qualify as the kind of "dirty tricks" or "exclusivity" you cite.
Every single unexpected or counterintuitive thing I've found, once I dig into it, is actually makes sense in terms of history, e.g., this seemingly odd rule of civil procedure is in place to prevent [bad_stuff] from happening which happened before, and from nearly 250 years of law in the US and 450 in some states, some serious cruft has accumulated, and could use some updating.
This is NOT to say that some laws aren't unreasonable, and to that we need to look to politics, not some "trickery to maintain legal pay".
I should also point out that the legal profession has not artificially limited the supply of lawyers as the medical profession has done by limiting accreditation of professionals. The result is that there are huge numbers of law school graduates, who even pass the bar exam, who literally cannot make a living as lawyers, and being offered $20/hour (literally) to work in some suburban law office with the hiring attny acting like it's a great offer.
And watching from up close and inside it, the idea that 'just because you can read means that you should be able to practice law', is utter nonsense. This has NOTHING to do with any kind of alleged "dirty tricks", and EVERYTHING to do with the inherent complexity that arises from the situation. Just because you can write a "Hello World" app in your favorite language does not mean that you can design and build an ACID-compliant accounting system & database, or even know that concurrency issues exist and what to do about them.
So, the actual facts on the ground are that attnys have not done the kind of exclusivity and dirty tricks that you cite, and in any case, they haven't managed to keep the wages in their profession high.
So just because you have an attitude, does not mean that it is justified.
Ugh. It's so discouraging when my lived experience contradicts with the subjective observation of someone who knows a lawyer and therefore becomes nonsense.
I do want to point out that the "dirty tricks" methodology is in full effect, but has been wholly ineffective at e.g. keeping lawyer salaries and employability high. Just because it failed to deliver on those axes doesn't mean it's not happening.
> Yet I have not found or even heard of a single instance of anything that would remotely qualify as the kind of "dirty tricks" or "exclusivity" you cite.
I'm not really motivated by this interaction to provide examples, but I assure you they are myriad. What I find particularly interesting about this comment is the assertion that the law makes sense if you just read it. This is both technically correct and practically useless. It illustrates that the intellectual moat which sustained law as a historically elite trade has evaporated.
> Just because you can write a "Hello World" app...
I hope that the difference between hello world and the other thing is that the developer has skill which adds value to the product. That's frequently not the case with lawyers. A lot of the time the increase in skill doesn't correlate to added value for anyone but the lawyer. It's a profession where people are largely rewarded for selfishly sequestering value rather than creating a better product/service or efficiently collaborating.
tldr; I hope that the code boot camps AND the law schools go out of business, but that your field can avoid the needless arcane complexity to which mine has long ago capitulated.
OK, you've been much more deeply in it than I have.
I used to have a similar attitude — that I ought to be able to quickly read a law in plain language and know what to do. Yet every time I argued that, I lost to valid often historical explanations from the attnys I was working/living with (& I've lived w/one for decades & been involve in a complex case with lots of BS maneuvering for 7+ years, and worked w/many building software for them).
No one doubts that there is a LOT of needless arcane complexity.
It is obvious to me that law is a monstrous mountain of arcane cruft. And not only the law, but also the caselaw precedents, regulations, etc..
It's also clear that this 1) has a strong exclusionary effect and 2) that those in the profession have little motivation to reduce this exclusionary effect, and some motivation to retain it, and so don't.
But there is a difference between a system that has a tendency towards a result that no one fixes, and a conspiracy to create similar results.
So, I'd really like to hear a good example or two that was deliberately created to exclude. Because AFAICT, it's just a mess that nobody is doing anything about and acting like it is some particular person's fault is self-destructive.
Sure. Here are a few examples of "let's make X as hard as possible so someone can never navigate it without a lawyer:"
1) Divorce.
2) Purchase/sale of land.
3) Adoption.
Notice what's not on my list: civil forfeiture, immigration, corporate mergers. There are certain classes of things which are complicated because e.g. the government wants them to be difficult (immigration), and certain other things which are inherently complicated, but which are made more efficient by cooperation. But there is a third class of thing which should be simple and is not. Transfer of land is complicated because lawyers have a financial interest in making it complicated. Divorce is a little different: you often have two people trying to ruin each other and lawyers enabling that by using procedure and trickery to try to engineer an unfair outcome in favor of a client.
But (assuming what I say is true) what is the functional difference between real estate and divorce? I argue there is none. A system which is deliberately engineered to be user-hostile is functionally identical to one where "cruft" accumulates and nobody is motivated to remove it.
Also realize that there is a cycle of lawyers deliberately making a legal procedure or practice so complicated that someone needs to stop them because they are creating an obstacle to the good functioning of society. See e.g.
1) Service of process
2) Civil discovery reform
3) UCC adoption
Thx for the answers
>> A system which is deliberately engineered to be user-hostile is functionally identical to one where "cruft" accumulates and nobody is motivated to remove it.
This could definitely be true. Of course the solution is different. In the case of buildup of cruft, one needs to generate motivation to improve it, whereas if someone is deliberately engineering bad features, one has to find who to fight and fight them.
I've been involved with service of process and civil discovery enough to know that they are a pain. We got service on one reluctant witness that was more a bit of luck to make it happen than not, and it seemed like a child's game of "tag". I agree that it needs reform, but who is actively making it more complicated? I've had opponents drag discovery out for years to the point of being sanctioned themselves, but it didn't seem to slow them down, but I'd put that more at the feet of judges that put up with the crap than an opaque process, which seemed at base pretty straightforward - they ask, here's the set of responsive docs. But who would we go after to fix it, and who is opposing us?
It’s difficult to tell who the author is addressing and what they want to have happen.
Are they talking to aspiring programmers and saying: stay away!
Are they talking to government officials and saying: change policy (to what I’m not sure and the author doesn’t describe, yet mentions policy several times).
Are they talking to universities/colleges: hey, stop adding courses in programming and advertising them?
The only thing this will do will be that searching for good developers will be even harder.
The shittiest lawyers work for the government.
I have a feeling the same will happen with the shittiest programmers: they will work for the government so now all of the most important government/privacy/identity infrastructure will be done by the least capable programmers.
There’s infinite useful work to be done. Everything broken, inefficient, unjust is work to be done. Every business idea anyone fails to launch, every improvement anyone fails to implement is money left on the table.
I just helped a client launch a tool that captures her decades of specialized knowledge and skill. Now her new hires can do work as well as she does. I charged a lot, but it was worth it because I created even more value. The key here is that even if she could have done it she’d still be creating that value.
The reason the computer industry has persisted is that computers are tools for multiplication of effort. Did you ever wonder when businesses would catch on and stop spending so much money on computers? They never did. Because computers create more value than they cost. Excel allows regular people to do difficult businesses projections because it’s a powerful tool. That’s why businesses keep spending money on it.
If everyone learns to code we get more work done. Every beneficial software tool gets built. (Ever been at work and thought, man this would be so much faster if “random specialized software tool” existed?)
Computers are just tools. Tools help us do work faster, better, with less error. Everyone learning to use powerful tools makes everyone more powerful, multiplies the value of their efforts.
But also, not everyone wants to or has the temperament to code. Civilization is specialization.
> Stroustrup: Well, one day, when I was sitting in my office, I thought of this little scheme, which would redress the balance a little. I thought 'I wonder what would happen, if there were a language so complicated, so difficult to learn, that nobody would ever be able to swamp the market with programmers?
Unironically trying to learn C++ for that reason. Jobs that require that pay REALLY well compared to like Javascript and Python, at least with what I have seen. Noone wants to use it, but businesses need people that know it, so I want to fulfill that need as best as I can
To some level, coding talent could be like Jevons Paradox. The price could go down, but the total spend on coding talent could go way up. I see the point about coding being highly scalable, and of course it makes sense that a limited and expensive talent resource has been used on highly scalable business applications. But if coders were much cheaper, it could make sense to apply code to many more, less scalable business problems. While not great for an individual highly paid coder, could be great for productivity growth.
Unlike churning out more lawyers, more coders can create a lot of economic value as they increase the overall amount of business automation. I think the policy wonks are less clueless than this author seems to assume.
Nice argument, and good examples from other professions.
The problem is that even if the market is "flooded" with freshly-credentialed grads who can supposedly code, that does not mean that they really can.
Knowing the basics of a language is only one step, and not even the most crucial one.
Much more critical is the ability to reason about complex systems, abstract the critical elements, and synthesize useful, practical, & efficient ways of dealing with the required inputs, storage, outputs, and UX issues. How many coders can even understand and identify race condition failures, let alone solve them? Just "knowing" a coding language only gets you a small part of the way to being a useful coder beyond very basic levels.
So, no, "everyone" "learning to code" will not result in everyone having the skills required to work effectively with code, and will not price themselves out of the market.
Another aspect is the Indian market with massive training programs, and hordes of Indians with programming certificates and jobs and fluent English language skills. Many companies outsourced there, only to bring the work back onshore because they failed to find the required skill level in India. Yet, I do not hear of programmer pay in India falling. Is this because it isn't falling due to a 'glut' of "people who learned to code", or because I haven't heard about it?
21 comments
[ 725 ms ] story [ 1582 ms ] threadI have personally coded a system for legal billing, had a variety of direct dealings with the legal system (contracts, etc.), and I live in a household with an attny at a top firm.
I've been surprised by a good number of counter-intuitive things in the law, such that the general rule I've heard repeatedly is that we cannot reason about the law without actually looking at the code in that particular instance — go look it up. This strongly resembles software code - we can assume a bunch of things about how something works, but to really find out, we must read the source code or trace it — go look it up.
Yet I have not found or even heard of a single instance of anything that would remotely qualify as the kind of "dirty tricks" or "exclusivity" you cite.
Every single unexpected or counterintuitive thing I've found, once I dig into it, is actually makes sense in terms of history, e.g., this seemingly odd rule of civil procedure is in place to prevent [bad_stuff] from happening which happened before, and from nearly 250 years of law in the US and 450 in some states, some serious cruft has accumulated, and could use some updating.
This is NOT to say that some laws aren't unreasonable, and to that we need to look to politics, not some "trickery to maintain legal pay".
I should also point out that the legal profession has not artificially limited the supply of lawyers as the medical profession has done by limiting accreditation of professionals. The result is that there are huge numbers of law school graduates, who even pass the bar exam, who literally cannot make a living as lawyers, and being offered $20/hour (literally) to work in some suburban law office with the hiring attny acting like it's a great offer.
And watching from up close and inside it, the idea that 'just because you can read means that you should be able to practice law', is utter nonsense. This has NOTHING to do with any kind of alleged "dirty tricks", and EVERYTHING to do with the inherent complexity that arises from the situation. Just because you can write a "Hello World" app in your favorite language does not mean that you can design and build an ACID-compliant accounting system & database, or even know that concurrency issues exist and what to do about them.
So, the actual facts on the ground are that attnys have not done the kind of exclusivity and dirty tricks that you cite, and in any case, they haven't managed to keep the wages in their profession high.
So just because you have an attitude, does not mean that it is justified.
Stop spouting nonsense.
I do want to point out that the "dirty tricks" methodology is in full effect, but has been wholly ineffective at e.g. keeping lawyer salaries and employability high. Just because it failed to deliver on those axes doesn't mean it's not happening.
> Yet I have not found or even heard of a single instance of anything that would remotely qualify as the kind of "dirty tricks" or "exclusivity" you cite.
I'm not really motivated by this interaction to provide examples, but I assure you they are myriad. What I find particularly interesting about this comment is the assertion that the law makes sense if you just read it. This is both technically correct and practically useless. It illustrates that the intellectual moat which sustained law as a historically elite trade has evaporated.
> Just because you can write a "Hello World" app...
I hope that the difference between hello world and the other thing is that the developer has skill which adds value to the product. That's frequently not the case with lawyers. A lot of the time the increase in skill doesn't correlate to added value for anyone but the lawyer. It's a profession where people are largely rewarded for selfishly sequestering value rather than creating a better product/service or efficiently collaborating.
tldr; I hope that the code boot camps AND the law schools go out of business, but that your field can avoid the needless arcane complexity to which mine has long ago capitulated.
I used to have a similar attitude — that I ought to be able to quickly read a law in plain language and know what to do. Yet every time I argued that, I lost to valid often historical explanations from the attnys I was working/living with (& I've lived w/one for decades & been involve in a complex case with lots of BS maneuvering for 7+ years, and worked w/many building software for them).
No one doubts that there is a LOT of needless arcane complexity.
It is obvious to me that law is a monstrous mountain of arcane cruft. And not only the law, but also the caselaw precedents, regulations, etc..
It's also clear that this 1) has a strong exclusionary effect and 2) that those in the profession have little motivation to reduce this exclusionary effect, and some motivation to retain it, and so don't.
But there is a difference between a system that has a tendency towards a result that no one fixes, and a conspiracy to create similar results.
So, I'd really like to hear a good example or two that was deliberately created to exclude. Because AFAICT, it's just a mess that nobody is doing anything about and acting like it is some particular person's fault is self-destructive.
1) Divorce. 2) Purchase/sale of land. 3) Adoption.
Notice what's not on my list: civil forfeiture, immigration, corporate mergers. There are certain classes of things which are complicated because e.g. the government wants them to be difficult (immigration), and certain other things which are inherently complicated, but which are made more efficient by cooperation. But there is a third class of thing which should be simple and is not. Transfer of land is complicated because lawyers have a financial interest in making it complicated. Divorce is a little different: you often have two people trying to ruin each other and lawyers enabling that by using procedure and trickery to try to engineer an unfair outcome in favor of a client.
But (assuming what I say is true) what is the functional difference between real estate and divorce? I argue there is none. A system which is deliberately engineered to be user-hostile is functionally identical to one where "cruft" accumulates and nobody is motivated to remove it.
Also realize that there is a cycle of lawyers deliberately making a legal procedure or practice so complicated that someone needs to stop them because they are creating an obstacle to the good functioning of society. See e.g.
1) Service of process 2) Civil discovery reform 3) UCC adoption
This could definitely be true. Of course the solution is different. In the case of buildup of cruft, one needs to generate motivation to improve it, whereas if someone is deliberately engineering bad features, one has to find who to fight and fight them.
I've been involved with service of process and civil discovery enough to know that they are a pain. We got service on one reluctant witness that was more a bit of luck to make it happen than not, and it seemed like a child's game of "tag". I agree that it needs reform, but who is actively making it more complicated? I've had opponents drag discovery out for years to the point of being sanctioned themselves, but it didn't seem to slow them down, but I'd put that more at the feet of judges that put up with the crap than an opaque process, which seemed at base pretty straightforward - they ask, here's the set of responsive docs. But who would we go after to fix it, and who is opposing us?
Are they talking to aspiring programmers and saying: stay away!
Are they talking to government officials and saying: change policy (to what I’m not sure and the author doesn’t describe, yet mentions policy several times).
Are they talking to universities/colleges: hey, stop adding courses in programming and advertising them?
Etc.
That's the end game, but I think we all know this already.
Don't devalue yourself.
Also, FAANG aren't the only companies in the world, just like McDonalds isn't the only restaurant.
The only thing this will do will be that searching for good developers will be even harder.
The shittiest lawyers work for the government.
I have a feeling the same will happen with the shittiest programmers: they will work for the government so now all of the most important government/privacy/identity infrastructure will be done by the least capable programmers.
There’s infinite useful work to be done. Everything broken, inefficient, unjust is work to be done. Every business idea anyone fails to launch, every improvement anyone fails to implement is money left on the table.
I just helped a client launch a tool that captures her decades of specialized knowledge and skill. Now her new hires can do work as well as she does. I charged a lot, but it was worth it because I created even more value. The key here is that even if she could have done it she’d still be creating that value.
The reason the computer industry has persisted is that computers are tools for multiplication of effort. Did you ever wonder when businesses would catch on and stop spending so much money on computers? They never did. Because computers create more value than they cost. Excel allows regular people to do difficult businesses projections because it’s a powerful tool. That’s why businesses keep spending money on it.
If everyone learns to code we get more work done. Every beneficial software tool gets built. (Ever been at work and thought, man this would be so much faster if “random specialized software tool” existed?)
Computers are just tools. Tools help us do work faster, better, with less error. Everyone learning to use powerful tools makes everyone more powerful, multiplies the value of their efforts.
But also, not everyone wants to or has the temperament to code. Civilization is specialization.
https://www-users.cs.york.ac.uk/susan/joke/cpp.htm
> Stroustrup: Well, one day, when I was sitting in my office, I thought of this little scheme, which would redress the balance a little. I thought 'I wonder what would happen, if there were a language so complicated, so difficult to learn, that nobody would ever be able to swamp the market with programmers?
Unlike churning out more lawyers, more coders can create a lot of economic value as they increase the overall amount of business automation. I think the policy wonks are less clueless than this author seems to assume.
The problem is that even if the market is "flooded" with freshly-credentialed grads who can supposedly code, that does not mean that they really can.
Knowing the basics of a language is only one step, and not even the most crucial one.
Much more critical is the ability to reason about complex systems, abstract the critical elements, and synthesize useful, practical, & efficient ways of dealing with the required inputs, storage, outputs, and UX issues. How many coders can even understand and identify race condition failures, let alone solve them? Just "knowing" a coding language only gets you a small part of the way to being a useful coder beyond very basic levels.
So, no, "everyone" "learning to code" will not result in everyone having the skills required to work effectively with code, and will not price themselves out of the market.
Another aspect is the Indian market with massive training programs, and hordes of Indians with programming certificates and jobs and fluent English language skills. Many companies outsourced there, only to bring the work back onshore because they failed to find the required skill level in India. Yet, I do not hear of programmer pay in India falling. Is this because it isn't falling due to a 'glut' of "people who learned to code", or because I haven't heard about it?
> The real valuable advice is not “learn to code,” but “be smart and talented.”
Sorry to break it to you, but you can "learn to code" and be quite the opposite and get a six figure job.
Coding is a skill. You don't have to be a computer scientist to know that it is a skill that gives you leverage in today's economy.