Showing posts with label Code. Show all posts
Showing posts with label Code. Show all posts

Tuesday, March 4, 2014

Opinion analysis: Justices stick with Bankruptcy Code text, rejecting Ninth Circuit’s creative punishment of lying bankrupt

As quick off the mark as usual, Justice Scalia’s unanimous opinion for the Court in Law v. Siegel was the Court’s first opinion from the January argument calendar and his fourth opinion (more than any other Justice) of the 2013 Term.



Justice Scalia delivers opinion (Art Lien)

Justice Scalia delivers opinion (Art Lien)



The case involves a bankrupt (Law) who tried to keep money from his creditors by claiming that his home was subject to a fictional lien.  Law’s activity in support of this fiction was remarkable; as the Court’s opinion notes, it extended (according to the courts below) to the filing of fictitious pleadings that he forged in the name of the fictitious lienholder.  By the end of the day, the trustee in the bankruptcy proceeding (Siegel) spent several hundred thousand dollars proving that Law’s claim was wholly fabricated. Outraged by the conduct, the bankruptcy court (following established Ninth Circuit precedent) held that the trustee could collect the expenses of that litigation out of the funds Law received from the sale of his homestead. Ordinarily, those funds would have been exempt under California’s homestead exemption (which differs in no material way from the homestead exemptions of every other state).


My posts on the briefs and on the argument suggested that the case presented the Justices with a stark choice between applying the plain language of the Bankruptcy Code (which would require it to reverse the Ninth Circuit), and giving in to the understandable impulse to affirm the capacity of the bankruptcy courts to dole out stern punishment for the remarkably deplorable conduct at issue here. The quick and unanimous reversal suggests that the Justices whose comments at the argument expressed so much outrage at Law’s conduct could not, on reflection, find a colorable basis for upholding the Ninth Circuit.


The Court’s brisk and workmanlike statutory analysis reads like the answer a talented student would give to a relatively simple exam question. The absence of qualifications or quibbles in its description of the relevant principles make it just the kind of opinion that is likely to be cited frequently in future briefs to the Court. The basic argument for punishing Law is that Bankruptcy Code § 105’s grant of general authority to “issue any order . . . that is necessary or appropriate to carry out the provisions of [the Bankruptcy Code]” is so general that it should be read to permit the sanction imposed in this case.  The fundamental problem, which Law could not overcome, is that the Code could hardly be any clearer in stating that bankruptcy courts cannot take exempt property (the proceeds of Law’s homestead) to fund administrative expenses (like the trustee’s litigation costs). Because the Court concluded that the order in question “contravened” the exemption rules, the Court found the order impermissible.


Among other things, the Court pointed to the provision in Section 522(k) stating that exempt assets are “not liable for the payment of any administrative expense.” The trustee’s litigation costs have to be administrative expenses for bankruptcy purposes, because they were incurred by the trustee litigating on behalf the estate; if they weren’t administrative expenses, they wouldn’t be reimbursable at all.  The suggestion that administrative expenses should have a narrower meaning in Section 522(k) than in the framework that makes those expenses an obligation of the estate was dismissed out of hand.


Nor did the Court find any substantial merit in the idea that the bankruptcy court has inherent power to deny an exemption as a sanction for misconduct.  For one thing, the courts in this case didn’t in fact deny the exemption – they granted the exemption and then “surcharged” it (the Ninth Circuit’s euphemism for confiscation). But more generally (and this part of the opinion probably will make it into future casebooks), the Court denied bankruptcy courts any authority to “withhold exemptions based on whatever considerations they deem appropriate.”  The “Code’s meticulous—not to say mind-numbingly detailed—enumeration of exemptions confirms that courts are not authorized to create additional exemptions.”


Finally, the Court rejected Law’s reliance (seconded by the United States Trustee) on its 2007 decision in Marrama v. Citizens Bank.  To be sure, the Marrama Court did have to work very hard to find a statutory basis for refusing to allow the debtor in that case to convert a bankruptcy case from Chapter 7 to Chapter 13. The easy answer for Justice Scalia would have been that he dissented from Marrama’s creative statutory construction in the first place.  But of course, with Justices Kennedy, Ginsburg, and Breyer still on the Court from the Marrama majority, he couldn’t get a unanimous Court for that explanation. So instead he summarized the statutory analysis of Marrama as colorable on its own facts but not so untethered to reality as to justify the statutory distortion that would be necessary to affirm the Ninth Circuit.


It’s a refreshingly reassuring experience to read an opinion for a unanimous Court that blithely upholds a result that most of the Justices must find distasteful. It just goes to show, even to the cynical, that legal rules, in fact, every now and then, constrain the Justices’ actions.


PLAIN LANGUAGE: When someone files for bankruptcy, ordinarily the courts cannot take the individual’s home, because it is “exempt” from the bankruptcy.  The Court in this case held that the home remains exempt even if the individual’s flagrantly deceptive conduct results in hundreds of thousands of dollars of litigation.


In association with Bloomberg Law




SCOTUSblog



Opinion analysis: Justices stick with Bankruptcy Code text, rejecting Ninth Circuit’s creative punishment of lying bankrupt

Monday, January 13, 2014

Twister: Decentralized Twitter Alternative Built with Code from Bitcoin/BitTorrent, Lavabit Encryption Scheme, No IP Recording

At Not Just The News, the privacy of our visitors is of extreme importance to us (See this article to learn more about Privacy Policies.). This privacy policy document outlines the types of personal information is received and collected by Not Just The News and how it is used.


Log Files


Like many other Web sites, Not Just The News makes use of log files. The information inside the log files includes internet protocol (IP) addresses, type of browser, Internet Service Provider (ISP), date/time stamp, referring/exit pages, and number of clicks to analyze trends, administer the site, track user"s movement around the site, and gather demographic information. IP addresses, and other such information are not linked to any information that is personally identifiable.


Cookies and Web Beacons


Not Just The News does use cookies to store information about visitors preferences, record user-specific information on which pages the user access or visit, customize Web page content based on visitors browser type or other information that the visitor sends via their browser.


DoubleClick DART Cookie


  • Google, as a third party vendor, uses cookies to serve ads on Not Just The News.

  • Google"s use of the DART cookie enables it to serve ads to users based on their visit to Not Just The News and other sites on the Internet.

  • Users may opt out of the use of the DART cookie by visiting the Google ad and content network privacy policy at the following URL - http://www.google.com/privacy_ads.html.

These third-party ad servers or ad networks use technology to the advertisements and links that appear on Not Just The News send directly to your browsers. They automatically receive your IP address when this occurs. Other technologies ( such as cookies, JavaScript, or Web Beacons ) may also be used by the third-party ad networks to measure the effectiveness of their advertisements and / or to personalize the advertising content that you see.


Not Just The News has no access to or control over these cookies that are used by third-party advertisers.


You should consult the respective privacy policies of these third-party ad servers for more detailed information on their practices as well as for instructions about how to opt-out of certain practices. Not Just The News"s privacy policy does not apply to, and we cannot control the activities of, such other advertisers or web sites.


If you wish to disable cookies, you may do so through your individual browser options. More detailed information about cookie management with specific web browsers can be found at the browser"s respective websites.



Twister: Decentralized Twitter Alternative Built with Code from Bitcoin/BitTorrent, Lavabit Encryption Scheme, No IP Recording

Thursday, October 24, 2013

HealthCare.gov: Team Obama and Its Dysfunctional 500 Million Lines of Code


Big government projects fail because real world business dynamics are absent


Kurt Nimmo
Infowars.com
October 24, 2013


HealthCare.gov used ten times the amount of code used in Windows Vista.

HealthCare.gov used ten times the amount of code used in Windows Vista.



The Obamaites are scrambling to cover their political posteriors in the wake of the crash and burn of their multi-million dollar fiasco known as HealthCare.gov.


It’s not their fault, Politico insists. Building a complicated website is a difficult thing to do. We are told the site contains 500 million lines of code and it will take time to ferret through it all and patch it up.


500 million lines of code? Really. Windows Vista, the notoriously bloated and slow computer operating system, only had 50 million lines of code.


“If you contract something out and get 500 million lines of code back, there’s no way it’s going to work correctly,” noted Slate’s vice president for technology, Dan Check.


But then we’re talking about government and over-budget contractors here. It’s only natural that big government projects fail because real world business dynamics are absent. Crash and burn is a routine feature of the state when it takes on projects better suited for business.


In government, if something fails bureaucrats simply throw more expropriated money around until they get the results they want. And even if they don’t get the results they want or expect – as in the case of Obamacare – they just force it down our throats at gunpoint.


Here’s an idea. Instead of bitching and moaning about how difficult it is to get a website up and running, Team Obama should head out to Utah and round up a few of the geeks who worked on the super-secret software the NSA is using to suck up all our email, text messages and phone calls.


Or Facebook. The social media network runs on around 20 million lines of code. It has over a billion users. Maybe they can spare a couple programmers.


Obamacare and its malfunctioning website constitute a magnificent train wreck. But when we assume government can do what the private sector and for-profit business can do more efficiently, we can expect not only to be disappointed but also taken to the cleaners.


This article was posted: Thursday, October 24, 2013 at 10:06 am


Tags: , , ,









Infowars



HealthCare.gov: Team Obama and Its Dysfunctional 500 Million Lines of Code

HealthCare.gov: Team Obama and Its Dysfunctional 500 Million Lines of Code


Big government projects fail because real world business dynamics are absent


Kurt Nimmo
Infowars.com
October 24, 2013


HealthCare.gov used ten times the amount of code used in Windows Vista.

HealthCare.gov used ten times the amount of code used in Windows Vista.



The Obamaites are scrambling to cover their political posteriors in the wake of the crash and burn of their multi-million dollar fiasco known as HealthCare.gov.


It’s not their fault, Politico insists. Building a complicated website is a difficult thing to do. We are told the site contains 500 million lines of code and it will take time to ferret through it all and patch it up.


500 million lines of code? Really. Windows Vista, the notoriously bloated and slow computer operating system, only had 50 million lines of code.


“If you contract something out and get 500 million lines of code back, there’s no way it’s going to work correctly,” noted Slate’s vice president for technology, Dan Check.


But then we’re talking about government and over-budget contractors here. It’s only natural that big government projects fail because real world business dynamics are absent. Crash and burn is a routine feature of the state when it takes on projects better suited for business.


In government, if something fails bureaucrats simply throw more expropriated money around until they get the results they want. And even if they don’t get the results they want or expect – as in the case of Obamacare – they just force it down our throats at gunpoint.


Here’s an idea. Instead of bitching and moaning about how difficult it is to get a website up and running, Team Obama should head out to Utah and round up a few of the geeks who worked on the super-secret software the NSA is using to suck up all our email, text messages and phone calls.


Or Facebook. The social media network runs on around 20 million lines of code. It has over a billion users. Maybe they can spare a couple programmers.


Obamacare and its malfunctioning website constitute a magnificent train wreck. But when we assume government can do what the private sector and for-profit business can do more efficiently, we can expect not only to be disappointed but also taken to the cleaners.


This article was posted: Thursday, October 24, 2013 at 10:06 am


Tags: business, domestic news, healthcare, technology









Infowars



HealthCare.gov: Team Obama and Its Dysfunctional 500 Million Lines of Code