According to this post (hat tip Marginal Revolution), doctors don't choose heroic measures at the end of life. I note VA has just announced a database for advance health directives. That's something I really should do.
[updated with the registry link]
Blogging on bureaucracy, organizations, USDA, agriculture programs, American history, the food movement, and other interests. Often contrarian, usually optimistic, sometimes didactic, occasionally funny, rarely wrong, always a nitpicker.
Monday, December 05, 2011
First We Kill All the Lawyers; and Make the World Happier
In two ways: the rest of us have no lawyers to deal with and we lose a bunch of people who are so depressed they bring down the happiness curve for the rest of us. From here--the logic of the research is that lawyers are pessimists, always worrying about what could go wrong.
80,000 Square Yards
The headline on the Treehugger post is: "
Paris to Plant 80,000 Square Yards of Green Roofs and Rooftop Gardens by 2020
That converts to 16.528 acres, which might could provide food for maybe, oh I don't know, 100? gai Parisiennes?
(To give them their due, the actual article doesn't talk about food, but insulation. But this is a prime example of how to lie with statistics; of course if they'd used square feet the figure would be even more impressive.)
Paris to Plant 80,000 Square Yards of Green Roofs and Rooftop Gardens by 2020
That converts to 16.528 acres, which might could provide food for maybe, oh I don't know, 100? gai Parisiennes?
(To give them their due, the actual article doesn't talk about food, but insulation. But this is a prime example of how to lie with statistics; of course if they'd used square feet the figure would be even more impressive.)
Sunday, December 04, 2011
On the Virtues of Patience
Musings from a Stonehead explains what's needed to capture a moment on film.
From a different post, just as an indicator it's worth clicking through to the site.
From a different post, just as an indicator it's worth clicking through to the site.
Who Remembers the Flight Engineer? Whither the Pilot
Used to be a job, but no more. See this Hanson pickup of a story on automated flight.
Saturday, December 03, 2011
EU Farmers and Farm Programs
A picture of EU agriculture from this (the context is the proper relationship between payments for grassland and payments for croplant):
It is about farmers who are farmers just to obtain subsidies and who fulfil their income goals only by subsidies. Perhaps, they have a few animals, although an increasing number of them only own grassland. From the agronomic point of view, this is intolerable, as the cultivation of hay for selling is not considered economically viable. In Slovenia, there are more than a quarter of agricultural holdings with grassland but no animals, but they apply for direct payments. Among them, there are less and less farmers and more and more mere land owners, who will have an increasing interest in the expansion of land, which they would rent out and if nothing else, split the subsidies with a tenant.
Why Do Farms Grow Bigger?
The University of Illinois reports on levels of debt and machinery costs, which says farmers are investing but not overextending. But one chart caught my eye: it's a graph showing the per acre debt/machinery costs by farm size. The curve descends, slowly but steadily. In other words, the bigger the farm, the more acres you can spread the cost of equipment over. What a surprise.
Government Contracting
For many years I lived blissfully without having any dealings with government contractors. Basically ASCS was, at least as far as I knew, all its work using its own employees. So it was an eye-opener in the late 80's when I started to run into government contracting, partly on the System/36 replacement project and a bit later on the Info Share project.
At least in my memory, the contractors were uniformly 8a firms, meaning their ownership was minority, women, disabled, with bigger outfits like Boeing and SAIC as their subcontractors. That seems to have continued with recent FSA projects.
Here's a govloop post from a disgruntled subcontractor (no relationship to USDA) which gives another side of the picture. Essentially the story is that the prime contractor systematically screwed the sub. Don't know whether it's true or not, don't know whether the government agency was satisfied with the performance under the contract, but it sure doesn't increase my faith in the use of contractors.
At least in my memory, the contractors were uniformly 8a firms, meaning their ownership was minority, women, disabled, with bigger outfits like Boeing and SAIC as their subcontractors. That seems to have continued with recent FSA projects.
Here's a govloop post from a disgruntled subcontractor (no relationship to USDA) which gives another side of the picture. Essentially the story is that the prime contractor systematically screwed the sub. Don't know whether it's true or not, don't know whether the government agency was satisfied with the performance under the contract, but it sure doesn't increase my faith in the use of contractors.
Locavore Water?
Onthepublicrecord is a blog about California water, interesting though sometimes hard to follow for an outsider. The most recent post discusses squabbling over who has first dibs on California water, morphing into a thesis about shared resources in a political entity.
I wonder what the locavore position on water is: should we use only the rain which falls on our land, or can the whole watershed share the water, and if so what is the watershed?
I wonder what the locavore position on water is: should we use only the rain which falls on our land, or can the whole watershed share the water, and if so what is the watershed?
Friday, December 02, 2011
Niedermayer Retires: ASCS History
Speaking of retiring employees, Chris Niedermayer is retiring from HUD. Perhaps my clearest memory of Chris is probably from early 1986 or so, in Kansas City Management Office, specifically in the testing section, when we were both working late at night, he probably testing price support software, I involved with production adjustment software. It was the first time our paths crossed, though I'd seen him in the hallways in the South Building.
If I remember correctly, Chris had been separated from a statistical agency (maybe NASS) during one of Reagan's attempts to downsize government. Those fired got help in finding openings elsewhere, so he got picked up by ASCS, initially in the in-house statistical/policy branch of the division I was in. As we started to implement the System/36 he became the go-to person for the price support program automation. Part of the time I was his counterpart for production adjustment. So that night in 1986 while I knew who Chris was from DC, it was the first time I realized how heavily involved he was in the price support automation.
Perhaps as a reflection of differences in persons, price support automation operated differently than production adjustment:
As time went on, things became more specialized on the PA side: program specialists would focus on either procedure or automation, and different units handled different areas, but until I retired the same shop would cover both sides of the subject. I've no idea which setup works best for the field, or whether there is any difference in the end result.
Anyhow by the late 80's the IT guys were worried about the System/36; they had underestimated the extent to which we'd load the System/36 so there was a continuous process of upgrading and moving to bigger models of the System/36, but they feared running out of room. So Chris moved to IRMD and was named the "Trail Boss" for the System/36 replacement, "trail boss" being a then-new, now-obsolete concept GSA had for the process of determining needs and handling procurements of big IT systems. So in 1990-92 Chris managed about 15 people trying to analyze ASCS data and operations, do a cost-benefit analysis to justify procurement of replacement hardware and software, and manage the conversion. In other words, a precursor of the current MIDAS effort, except it was bigger, since the administrative and financial side was also covered by Chris's project.
Unfortunately, Chris couldn't move the project fast enough, so when Clinton won the election and Secretary Espy assumed office, it was subject to not-invented-here syndrome. A part of the intra-office politics of the time was the "ins" versus the "outs". Chris IMHO had antagonized some of the Democratic outs, so when they became the "ins" they weren't inclined to keep his project going. Chris ended up moving to the Department level for several years, then to HUD, becoming deputy CIO, which is the job from which he's retiring.
If I remember correctly, Chris had been separated from a statistical agency (maybe NASS) during one of Reagan's attempts to downsize government. Those fired got help in finding openings elsewhere, so he got picked up by ASCS, initially in the in-house statistical/policy branch of the division I was in. As we started to implement the System/36 he became the go-to person for the price support program automation. Part of the time I was his counterpart for production adjustment. So that night in 1986 while I knew who Chris was from DC, it was the first time I realized how heavily involved he was in the price support automation.
Perhaps as a reflection of differences in persons, price support automation operated differently than production adjustment:
- price support separated the functions of doing policy (regulations and procedures) from doing automation (user requirements, working with programmers, testing). For a while, maybe 1986-89. For a while Chris was the automation guru, then he became responsible for all of price support.
- meanwhile on the PA side we mostly had people wearing two hats, doing both automation and the procedures.
As time went on, things became more specialized on the PA side: program specialists would focus on either procedure or automation, and different units handled different areas, but until I retired the same shop would cover both sides of the subject. I've no idea which setup works best for the field, or whether there is any difference in the end result.
Anyhow by the late 80's the IT guys were worried about the System/36; they had underestimated the extent to which we'd load the System/36 so there was a continuous process of upgrading and moving to bigger models of the System/36, but they feared running out of room. So Chris moved to IRMD and was named the "Trail Boss" for the System/36 replacement, "trail boss" being a then-new, now-obsolete concept GSA had for the process of determining needs and handling procurements of big IT systems. So in 1990-92 Chris managed about 15 people trying to analyze ASCS data and operations, do a cost-benefit analysis to justify procurement of replacement hardware and software, and manage the conversion. In other words, a precursor of the current MIDAS effort, except it was bigger, since the administrative and financial side was also covered by Chris's project.
Unfortunately, Chris couldn't move the project fast enough, so when Clinton won the election and Secretary Espy assumed office, it was subject to not-invented-here syndrome. A part of the intra-office politics of the time was the "ins" versus the "outs". Chris IMHO had antagonized some of the Democratic outs, so when they became the "ins" they weren't inclined to keep his project going. Chris ended up moving to the Department level for several years, then to HUD, becoming deputy CIO, which is the job from which he's retiring.
Subscribe to:
Posts (Atom)