@roger,
Oh, another thing about da law:
Not just jargon (and Latin!) but big words in general can really be used to separate the men from the boys, such as it is. And I always hated it. For depositions, you want to get clear answers, so using "prior to" and "subsequent to" is just plain stupid-ass showing off. Use "before" and "after", like a normal person. For cross-examination at trial, do the opposite (usually).
I also learned from the law that a lot of it (duh!) is extraordinarily adversarial. This is good for trial; it's important. For fact-gathering, not so much -- most places have communities and you will see people over and over and over again. If you need extra time to do something, and you've consistently been a jerk to your adversary, they will not give you the time, and it will cost your client mucho bucks to get the same time extension via motion. Be sweet as pie and you'll cost the client a lot less money and actually be able to have fewer attorneys on staff, as prep for conferences and writing letters can be done by paralegals.
That's also what I learned as a legal auditor -- jerkiness begets extra costs, unless it's at trial. Then go ahead and be as passive-aggressive as your heart desires. But don't do it during discovery, which is when you actually want to - surprise! - discover information.
As for what I do now (database reporting and security, plus data loading/ETL): Robert's right, a lot of people care a lot more about prettiness than they do about architecture. But prettiness is still important, in particular when you are either dealing with the public or with high ups (director or VP level and up, which is who I've worked for, for years). Sure they want to see the correct Cleveland data, but they also want it in a lovely graph.
For this crowd, the less said, the better (she says, typing a long reply). But it's true! Short paragraphs, short sentences and visual aids if appropriate, go a long, long way. Get your message across fast because no one's gonna read a long message any way.
As for ETL, it doesn't seem to be well thought-out at times, because it's behind the scenes (although that may be a function of the system I'm using). When things are kludgey and slow on the back end, and not necessarily that sweet on the front end, it's time for a new system.