Paul M. Jones

Don't listen to the crowd, they say "jump."

Libertarianism and Selfishness

In reality, however, libertarianism often requires unselfish behavior. Libertarians routinely condemn politicians who advocate statist policies in order to expand their power or ensure their reelection, bureaucrats who seek to increase the authority and funding of their agencies, businessmen who lobby for government subsidies and handouts, politically influential developers who use the power of eminent domain to acquire property that they covet, law enforcement officials who support the War on Drugs because it increases their funding, public employees unions who support big government in part because it increases their pay, and much other self-interested behavior. The fact that all of these groups are motivated, at least in part, by self-interest doesn’t prevent libertarians from denouncing them. That’s because libertarianism is a theory of the appropriate role of government in society, not a theory that judges the morality of human behavior based on whether or not people are acting out of self-interest.

via The Volokh Conspiracy » Libertarianism and Selfishness.


Blogger outage makes case against cloud-only

Earlier this week, Google rolled out a maintenance release for its Blogger service. Something went terribly wrong, and its Blogger customers have been locked out of their accounts for more than a day. Google’s engineers have been frantically working to restore service ever since, although they haven’t shared any details about the problem.

...

That’s nearly 48 hours of downtime, and counting. Overnight updates promise “We’re making progress” and “We expect everything to be back to normal soon.”

...

Google has owned and operated Blogger since 2003. It’s not like they’re still trying to figure out how to integrate the service into their operation. If it can happen at Blogger, why can’t it happen with another Google service?

...

This, to me, is the strongest possible argument against putting everything you own in the cloud. If your data matters, you need a hybrid strategy, with local storage and local content creation and editing tools. If your local storage fails, you can grab what you need from the cloud. If your cloud service fails, you’ve still got it locally. But if you rely just on the cloud, you’re vulnerable to exactly this sort of failure.

via Google's Blogger outage makes the case against a cloud-only strategy | ZDNet.


Rising food prices are the result of rising oil prices, not a growing market for ethanol

There may well be hunger among the world’s poorest this year, but not because of the U.S. corn ethanol program. Rather, the threat comes from high oil prices, which at $100 per barrel will place a tax on the U.S. economy of $800 billion per year, and $3,200 billion on the world economy as a whole. This will raise the price of all goods and slow down the world economy, thereby throwing millions of people out of work and leaving them without income to buy food. According to a Merrill Lynch analysis, if not for the world’s ethanol programs (of which U.S. production represents about a third), global oil prices would be 15 percent higher than they are, thereby placing an additional $480 billion impost on the world economy.

The problem is not that we are producing too much alcohol to compete against oil, but that we are not producing enough.

via Pajamas Media » Why It’s Wrong to Agree with the Malthusians about Ethanol.


Court: No right to resist illegal cop entry into home

Overturning a common law dating back to the English Magna Carta of 1215, the Indiana Supreme Court ruled Thursday that Hoosiers have no right to resist unlawful police entry into their homes.

In a 3-2 decision, Justice Steven David writing for the court said if a police officer wants to enter a home for any reason or no reason at all, a homeowner cannot do anything to block the officer's entry.

I cannot express my anger strongly enough. Via Court: No right to resist illegal cop entry into home.

Update: further commentary at Volokh.


In Defense of Flogging

The United States now has more prisoners than any other country in the world. Ever. In sheer numbers and as a percentage of the population. Our rate of incarceration is roughly seven times that of Canada or any Western European country. Despite our “land of the free” rhetoric, we deem it necessary (at great expense) to incarcerate more of our people, 2.3 million, than the world’s most draconian regimes. We have more prisoners than China, and they have a billion more people than we do. We have more prisoners than soldiers; prison guards outnumber Marines.

via In Defense of Flogging | The Agitator. Paging Mr Heinlein; Mr Heinlein, please pick up your copy of Starship Troopers at the Rodger Young.


I Like My IT Budget Tight and My Developers Stupid

If you don’t give staff time to recharge their batteries, they burn out. It’s one reason why Goerlich requires his staff to put aside 20% of their time for skills development. He hit on that number back when he ran a consultancy. In those days, he’d have a certain type of consultant out billing “rock-solid” hours, flat-out, wall-to-wall.

They tended to be the young ones.

They’d last six months.

Goerlich noticed that his consultants who weren’t maxing out on hours were hitting the mark at about 60% billable hours. Those people spent about 20% of their time recharging. “Those are people that, year after year, they didn’t have high peaks, but they maintained billables in the high level--say, the top 10%--while the others were going gangbusters for six months and burning out.”

Goerlich wants his current team to match that: Put the majority of yourself into your projects, then put at least 20% aside to get training and to just plain catch your breath.

“There’s a lot of work to get done,” Goerlich said. “It’s almost like a Chinese finger puzzle: You pull too hard, and you can’t get out. You put in too many hours, you get diminishing returns.”

He hasn’t lost a key member in a tenure of five years. He credits the training regime as one of the reasons the financial services firm has a high level of IT staff retention. “I tend to have a very motivated team,” he said. “It astonishes me how much they put into the environment, into their jobs. But then, it’s very stressful to try to do work when you don’t know what you’re doing. If you don’t have the confidence that you know what you’re doing, you can’t be creative.”

via I Like My IT Budget Tight and My Developers Stupid. Hat tip to Cal Evans.


Different Definitions of Quality

Recently, I was pondering why it is that programmers and employers have different attitudes toward the quality of the projects they collaborate on. I formulated it like this:

  • The people who do the work are usually the ones who care more about quality. Why?

    • They have a reputation to maintain. Low quality for their kind of work is bad for reputation among their peers. Note that their peers are not necessarily their employers.

    • They understand they may be working on the same project later; higher quality means easier work later, although at the expense of (harder? more?) work now.

  • The people who are paying for the work care much less about quality. Why?

    • The reputation of the payer is not dependent on how the work is done, only that the work is done, and in a way that can be presented to customers. Note that the customers are mostly not the programmer’s peers.

    • They have a desire to pay as little as possible in return for as much as possible. “Quality” generally is more costly (both in time and in finances) in earlier stages, when resources are generally lowest or least certain to be forthcoming.

    • As a corollary, since the people paying for the work are not doing the work, it is easier to dismiss concerns about “quality”. Resources conserved earlier (both in time and money) means greater resources available later.

Dismissing quality concerns early may cause breaks and stoppage when the product is more visible or closer to deadline, thus leading to greater stress and strain to get work done under increasing public scrutiny. The programmer blames the lack of quality for the troubles, and the employer laments the programmer’s inability to work as quickly as he did earlier in the project.

Two Different Definitions

While the above analysis may be true, I realized later that I was approaching the problem from the wrong angle. It's not that one cares more about quality than the other. Instead, it is that they have two different definitions regarding project quality.

  • The programmer’s “quality” relates to the what he sees and works with regularly and is responsible for over time (the code itself).

  • The payer’s “quality” relates to the what he and the customers see and work with regularly and are responsible for over time (what is produced by running the code; i.e., the product, not the program).

That's the source of the disconnect. When approached in this way, "quality" as judged in one view is now obviously not the same thing as when judged in the other view; code quality and product quality are distinct from each other (although still related).

One interesting point is that the developer has some idea about the product quality (he has to use the product in some fashion while building it), but the manager/employer/payer has almost no idea about the code quality (they are probably not writing any code).

The solution to the disconnect in software development may be to involve someone who understands both sets of concerns, and who has the authority to push back against both sides as needed. Then the business as a whole can address the concerns of both sets of people.


Epilogue:

1. Thanks to Brandon Savage for reading and commenting on an earlier version of this article.

2. Incidentally, I think the "quality" definition disconnect also applies to various non-software crafts and trades. You hear about carpenters, plumbers, painters, etc. complaining that they get undercut on prices by low-cost labor who don’t have the same level of quality. And yet the customers who choose the lower-cost option are satisfied with the quality level, given their resource constraints. The developer-craftsman laments the low quality of the work, but the payer-customer just wants something fixed quickly at a low cost.


Markets Make Us More Rational

People, including economists, are imperfect decision makers because of their mental limitations. But this fact does not mean that markets fail. Indeed, markets do far more than induce improved allocation of resources, given wants and resources. Markets induce market participants to be more rational than they otherwise would be because they must pay a price for being irrational. Thus, markets allow--no, require--economists to assume that people are more rational than they are likely to be found to be in laboratory settings, absent meaningful information and incentives and absent market pressures.

via The Volokh Conspiracy » How Markets Make Us More Rational.


Grocery School

Suppose that we were supplied with groceries in same way that we are supplied with K-12 education.

Residents of each county would pay taxes on their properties.  A huge chunk of these tax receipts would then be spent by government officials on building and operating supermarkets.  County residents, depending upon their specific residential addresses, would be assigned to a particular supermarket.  Each family could then get its weekly allotment of groceries for “free.”  (Department of Supermarket officials would no doubt be charged with the responsibility for determining the amounts and kinds of groceries that families of different types and sizes are entitled to receive.)

Except in rare circumstances, no family would be allowed to patronize a “public” supermarket outside of its district.

...

Does anyone believe that such a system for supplying groceries would work well, or even one-tenth as well as the current private, competitive system that we currently rely upon for supplying grocery-retailing services?

via Grocery School.