Skip to main content

The BUSKLAW 2019 Year in Review



'Tis the week before "Happy New Year" and a good time to look back on the topics that we covered in 2019. So while you look forward to the 2020 college football bowl games, how to spend those gift cards, or what fine champagne to pop on New Year's Eve, let's reminisce: 

>January: We examined the reasons for auditing your contracts, pointing to five potentially troublesome contract provisions: identification of the parties, agreement term, payment, intellectual property rights, and confidentiality.  
> February: We continued that discussion, examining these essential provisions: indemnification, insurance, limitation of liability, exclusion of certain damages, governing law, jurisdiction, venue, and whether it's better to resolve contract disputes through litigation or arbitration.
>March: We explained why you should never use "form" contracts
>April: We pulled apart the purchase agreement for the Icon A5 light-sport aircraft, a/k/a the "jet ski with wings."
>May: We talked about the "useless accuracy of legal jargon" in the context of the Icon A5 purchase agreement.
>June: We examined the strategy of using buried contract provisions to effect social change, using the Salesforce contract with Camping World as a prime example. 
>July: We found out what happens when you sue for everything, including the kitchen sink.
>August: We focused on the importance of cleaning out those pesky cobwebs in your contracts.
>September: No post - late-summer hiatus.
>October: We discussed two cases that show how disrespecting contract mechanics can cut both ways.
>November: We examined the curious contract between the U.S. Army and To the Stars for the acquisition of the latter's extraterrestrial(?) technology. 
>December:  We discovered what can happen when you sue for lost profits - and don't listen to the judge.

And along the way we had a few "asides":

> We discussed the information technology side of my law practice.
> We heard what it means to write well on Christmas.

Many thanks to my readers over the past year. I know that your time is precious and hope that you have found these posts informative and (occasionally) entertaining. We'll try to continue that approach in 2020!
___________________________________

If you find this post worthwhile, please consider sharing it with your colleagues. The link to this blog is www.busklaw.blogspot.com and my website is www.busklaw.com. And my email address is busklaw@charter.net. Thanks!

Comments

Popular posts from this blog

The BUSKLAW 2021 Year in Review - Brit English Sums It Up!

  I'm at a loss to describe 2021 using American English, sorry. AmE has grown tiresome. Don't believe me? Just turn on your local TV news and listen for how many times the news people use "prior" instead of "before" and pepper their speech with "as well," frequently tacking it on after using "also" in the same sentence, as in "It will also rain tomorrow as well." How can all be WELL when every other sentence ends with AS WELL? Warning: don't play a drinking game to count the number of  AS WELLs or you'll be pished (as they say in Scotland) in 10 minutes. Which reminds me of why we should be thankful for Brit English to describe 2021: it was another year that we good guys got knackered .   Consider: Covid continues unabated - now improved with variants (get your booster, wear a mask)! The peaceful transition of the U.S. government after the 2020 presidential election almost didn't happen (can you say "insurrectio...

The BUSKLAW Halloween 2022 Post: Stephen King's Asides on Poor Writing in Fairy Tale

  Having just read  Stephen King's Fairy Tale in time for Halloween, it's appropriate to examine his asides on poor writing included in the book. (BTW, Fairy Tale is a good read with King's typical well-executed character development, plot, and a great finish to the story. But you have like the whole Grimm fairy tale genre before you read his take on it.)  Stephen King doesn't tolerate anything less than crisp prose. When the story's hero, Charlie Reade, tries to read a book about the origins of fantasy and its place in the world matrix ("what a mouthful"), he can only scan it because: It was everything I hated about what I thought of as "hoity-toity" academic writing, full of five-dollar words and tortured syntax. Maybe that's intellectual laziness on my part, but maybe not. Later on, Charlie tries to focus on a particular chapter in the "origins of fantasy" book about the story of Jack and the Beanstalk but is put off by "t...

The BUSKLAW May Newsletter: The Foolhardy Practice of Using Faux Terms of Art in Your Contracts

  Most lawyers draft contracts. That's what lawyers do. And they use perceived terms of art ("TOAs") because they want to be paragons of contract-drafting precision. But here is where the canker gnaws:  the words that lawyers insert in their contracts as TOAs are actually not, potentially causing problems in clarity and interpretation. And as I've said time and again, these problems lead to disputes, and disputes lead to litigation, which is always time-consuming and expensive for the parties involved.  Let's first define TOAs in the legal context. According to Professor Bryan Garner in his Dictionary of Legal Usage , TOAs have specific, precise meanings that are "locked tight" and based on legal precedent. But then there are the faux TOAs, "whose meanings are often unhinged." Expert contract drafters, Garner says, know that clear, simple drafting is less subject to misinterpretation than using TOAs that are nothing more than "mere jargon....