13 ms·

As far as made-up "bullshit jobs" go in this society, patent lawyers are likely well-positioned on the compensation scale, but if you enjoy actually building so

As far as made-up "bullshit jobs" go in this society, patent lawyers are likely well-positioned on the compensation scale, but if you enjoy actually building something and having some fruit of your labor to show at the end of the day, it might not be a good place for an engineer. You'll be "solving" a problem that is the result of a completely artificial and particularly badly designed system. Such jobs can get to you as you curse the stupidity of the people who came up with and run that system daily. That said - as long as nothing changes - someone has to do the job.

JTbane 5y ago
I don't think I could personally make it as a lawyer in any capacity; from those I have talked to in the legal profession it seems like 100% pushing papers around. Also, I don't agree with patents in a political sense.
- D13Fd 5y ago
  It's not mindless "pushing papers around" -- that job is done by paralegals and administrative assistants. But 50-100% of most attorneys' time is spent either "reading things," "researching things," or "writing things," if that is what you mean. That is the bread and butter of legal work these days, whether it's writing briefs, e-mails, letters or something else, and reading legal opinions, research materials, discovery, etc. Basically most of your job as a patent litigator is to read things and occasionally depose people, then research things, then write things (not always in that order). The remainder of time is mostly spent on client communications and marketing. Occasionally you may make it to trial or a mock trial, where you spend a lot more time on your feet and speaking (or sitting and listening while someone else speaks), but still generally around 25-50%+ of your trial time is spent reading and writing.
  - amusedcyclist 5y ago
    Its pretty mindless, even the "reading" and "researching" is extremely dull. The level of logical complexity isn't that great and its a lot of overworded nonsense.
    - D13Fd 5y ago
      It depends on what you are doing. Legal research and writing can be anywhere from kind of dull to fascinating. That's also true for pretty much any job, so I'm not sure what your point is.
      - amusedcyclist 5y ago
        That I think if you're going from software to legal work you're likely to be bored.
    - hnfong 5y ago
      Are you sure you know what you're talking about? The body of knowledge in law is vast and some areas can be intellectually stimulating as well (depending on one's interests). "Overworded nonsense" that you usually see (in contracts or legislation, I suppose) happens when less than stellar lawyers are made to write stuff upon a deadline, and is the equivalent of "spaghetti code". Usually, it's fine since nobody (I think) gives you a bonus for succinct writing when drafting a contract. But you might get in trouble for missing some "edge cases". There's also a lot of cargo culting (magic Latin incantations) and building on questionable templates (technical debt). Sometimes people intentionally write in weird illegible ways to impress people (think Perl one liners). Anyway, when most programmers see an unfamiliar codebase for the first time, they'd probably think most of the code are "overworded nonsense" until they fully understand the "business requirements" and the special cases implemented. (This is where the adage against complete rewrites comes from.) Unless you're really an expert in the area of law, you're probably not qualified to say that some legal texts are overworded nonsense. But yeah, there's more parallels in law and software engineering than one might think. I'm a software engineer by trade, not a lawyer, but I do have a degree in law, and I often read up on cases or occasionally do my own legal research mostly for fun and personal interest. I would contend your "extremely dull" claim. TBH I might read more legal texts than Other People's Code, the latter which I generally hate doing, and is usually more boring for me (and occasionally infuriating when I know the coders spewing writing crap instead of putting effort in making the stuff succinct and clean). That said, believe whatever you want.
      - 5y ago
deleted 5y ago
[deleted]

JTbane 5y ago

I don't think I could personally make it as a lawyer in any capacity; from those I have talked to in the legal profession it seems like 100% pushing papers around. Also, I don't agree with patents in a political sense.

D13Fd 5y ago
It's not mindless "pushing papers around" -- that job is done by paralegals and administrative assistants. But 50-100% of most attorneys' time is spent either "reading things," "researching things," or "writing things," if that is what you mean. That is the bread and butter of legal work these days, whether it's writing briefs, e-mails, letters or something else, and reading legal opinions, research materials, discovery, etc. Basically most of your job as a patent litigator is to read things and occasionally depose people, then research things, then write things (not always in that order). The remainder of time is mostly spent on client communications and marketing. Occasionally you may make it to trial or a mock trial, where you spend a lot more time on your feet and speaking (or sitting and listening while someone else speaks), but still generally around 25-50%+ of your trial time is spent reading and writing.
- amusedcyclist 5y ago
  Its pretty mindless, even the "reading" and "researching" is extremely dull. The level of logical complexity isn't that great and its a lot of overworded nonsense.
  - D13Fd 5y ago
    It depends on what you are doing. Legal research and writing can be anywhere from kind of dull to fascinating. That's also true for pretty much any job, so I'm not sure what your point is.
    - amusedcyclist 5y ago
      That I think if you're going from software to legal work you're likely to be bored.
  - hnfong 5y ago
    Are you sure you know what you're talking about? The body of knowledge in law is vast and some areas can be intellectually stimulating as well (depending on one's interests). "Overworded nonsense" that you usually see (in contracts or legislation, I suppose) happens when less than stellar lawyers are made to write stuff upon a deadline, and is the equivalent of "spaghetti code". Usually, it's fine since nobody (I think) gives you a bonus for succinct writing when drafting a contract. But you might get in trouble for missing some "edge cases". There's also a lot of cargo culting (magic Latin incantations) and building on questionable templates (technical debt). Sometimes people intentionally write in weird illegible ways to impress people (think Perl one liners). Anyway, when most programmers see an unfamiliar codebase for the first time, they'd probably think most of the code are "overworded nonsense" until they fully understand the "business requirements" and the special cases implemented. (This is where the adage against complete rewrites comes from.) Unless you're really an expert in the area of law, you're probably not qualified to say that some legal texts are overworded nonsense. But yeah, there's more parallels in law and software engineering than one might think. I'm a software engineer by trade, not a lawyer, but I do have a degree in law, and I often read up on cases or occasionally do my own legal research mostly for fun and personal interest. I would contend your "extremely dull" claim. TBH I might read more legal texts than Other People's Code, the latter which I generally hate doing, and is usually more boring for me (and occasionally infuriating when I know the coders spewing writing crap instead of putting effort in making the stuff succinct and clean). That said, believe whatever you want.
    - 5y ago

deleted 5y ago

[deleted]