The Daily Parker

Politics, Weather, Photography, and the Dog

Ah, conferences

The Tech Forum goes on. Tomorrow, though, I don't need my work laptop, and so will bring my personal one, enabling me to post a little more.

I've also thought about finally writing my own blog engine. Or, at least, forking an existing one (maybe even this one?) and going to town on it. During some downtime today I purged a lot of crap from my Microsoft Azure subscriptions, but I still have old applications (like this blog) running in old workloads.

Tonight: the Fun Dinner. Oh, boy.

Weather Now 5 close to launch

Last night, I finished the last major feature in the Weather Now upgrade that I started in earnest back in October 2020. That means the development app can do most of what the version 4 can do, except better in most cases. By extension, that means I just have a few things to do in order to replace version 4 in production. But "a few things" includes setting up all the production assets for the new version, including the DevOps pipelines. That's not a small job.

That last bit may take a while. I'll have more extensive release notes closer to launch. The Search feature will have the most limitations immediately post-launch as it requires replacing the current 7.5-million-row gazetteer from the external sources, rather than simply porting the data. A few other things (full internationalization, configuring your language and measurement systems, and historical data) will also take time. Modernizing the deployment pipeline makes adding these features back in a lot easier, though.

For now, the development app has weather archives back to last May and much simpler methods of accessing data than v4. I encourage you to try it out.

Busy couple of days

I've had a lot to do at work the last couple of days, leading to an absolute pile-up of unread press:

Finally, on this day in 1940, Woody Guthrie released "This Land is Your Land," a song even more misunderstood than Bruce Springsteen's "Born in the USA."

More about the insanity of crypto

A couple more resources about "web3" (cryptocurrencies, NFTs, DAOs, etc) crossed my inbox this week. Even before going through these stories and essays, the only way I can understand the persistence of the fantastic thinking that drives all this stuff is that the people most engaged with it turn out to be the same people who believe all kinds of other fantasies and wish-fulfillment stories.

Case in point: the extreme right-wing protestors up in Canada have received almost all of their funding from American right-wingnuts. Remember: the protestors believe, counter to all evidence, that vaccines cause more harm than good, and that they have a right to remain part of a common society without the responsibility of protecting others in that society from easily-avoided harm.

Because Canada really wants them to go away, and even more than that does not want foreigners funding domestic terrorists, the Canadian government blocked the cross-border financial transfers to the Maple Morons through the regular banking system. It took about 36 seconds for the Americans to try again using cryptocurrencies, and about 14 seconds longer for scammers to piggyback on the effort:

Canada Unity 2022, the group of anti-vaccine protestors who have snarled traffic in Ottawa and earned accolades in the right-wing media, wants to talk to you about Bitcoin.

A handful of the group’s organizers held a press conference on Facebook Live Wednesday that quickly devolved into a presentation on the popular form of cryptocurrency, confusing many of their supporters who were watching online.

“Are we at a press conference for Freedom Convoy 2022 or having some guy shove Bitcoin down our throats?” one commenter griped. “Very disappointed! I came to see updates about progress made by our Truckers.”

In some respects, the convergence of the anti-vaxx protests and Bitcoin was probably inevitable. Last month, the protests drew support from one of the biggest proponents of Bitcoin in the world, Tesla CEO Elon Musk, who tweeted “Canadian truckers rule.” Former President Donald Trump has voiced support, and right-wing figures from Tucker Carlson to Ben Shapiro to Michael Flynn have seized on the trucker protests.

Even better, the way organizers have decided to distribute the Bitcoin meant for the rationality- and education-challenged protestors might not exactly show the benefits of cryptocurrencies in the best light:

Instead of giving the truckers the money in a cash format they can actually use, the "professional orange-piller" in charge of the Bitcoin distribution has explained a multi-step plan to give truckers pieces of paper with seed phrases printed on them. The seed phrases will be placed into sealed envelopes along with instructions on how to create a Bitcoin wallet, which are then "numbered and squiggly random lines should be drawn on the envelope to help with later identification". The volunteers then plan to physically destroy the printer with shears and screwdrivers, to try to prevent attackers from pulling the seed phrases out of the device memory. Of course once the trucker has their seed phrase, they have to go through the multi-step process of gaining access to the Bitcoin wallet on their smartphone, and then figure out how on earth to actually use their newfound Bitcoins to, say, pay for fuel.

That comment comes from software engineer Molly White, who has a delightful and detailed series of essays on blockchain in general. If you have any questions about web3 or blockchain and don't want a sales pitch from someone trying to keep the value his holdings inflated until he can dump them on you, start with White.

In a world where people devalue the study of history and economics in favor of shouting to the world about their magical beliefs, the rise of crypto doesn't surprise me. I don't know what will happen when it all collapses, but I have a pretty good idea who'll get hurt. I wonder who the right-wingnuts will blame when they lose everything? Probably not themselves.

Happy 20th birthday, .NET

Today is the 20th birthday of the Microsoft .NET Framework. I remember it vividly, because of the job I had then and its weirdly coincidental start and end dates.

I joined a startup in Chicago to write software using the yet-unreleased .NET Framework in 2001. My first day of work was September 10th. No one showed up to work the next morning.

Flash forward to February 2002, and our planned release date of Monday February 18th, to coincide with the official release of .NET. (We couldn't release software to production using the unreleased beta Framework code.) Microsoft moved the date up to the 14th, but we held to our date because releasing new software on a Thursday night in the era before automated DevOps pipelines was just dumb.

I popped out to New York to see friends on Saturday the 16th. Shortly after I got back to my house on the 17th, our CTO called me to let me know about a hitch in our release plans: the CEO had gotten caught with his hand in the till. We all wound up working at minimum wage (then $5.25 an hour) for two weeks, with the rest of our compensation deferred until, it turned out, mid-2004.

So, happy birthday, .NET Framework. Your release to manufacturing date meant a lot more to me than I could have imagined at the time.

The real daylight saving

A friend on social media posted a graph of how quickly or slowly the amount of daylight changes per week. Unfortunately the graph was for London, and pretty ugly, so I decided to make one for Chicago that was a bit more spare:

Here in Week 6, we get 15 more minutes of daylight than we got last week. For most of March, we'll get 17 minutes more per week before things slow down a bit, then reverse. The weeks of both solstices have zero change.

The friend wondered in her post what it would look like in the southern hemisphere. So, voilà Sydney:

And just for giggles, I graphed Fairbanks, too:

Neat, huh?

(Incidentally, the links point to the Weather Now v5 Beta site. Even after the v5 launch sometime this spring, the Beta URL should stay functional.)

Lazy Sunday

Other than making a hearty beef stew, I have done almost nothing of value today. I mean, I did some administrative work, and some chorus work, and some condo board work. But I still haven't read a lick of the books I've got lined up, nor did I add the next feature to the Weather Now 5 app.

I did read these, though:

  • An Illinois state judge has enjoined the entire state from imposing mask mandates on schools, just as NBC reports that anti-vaxxer "influencers" are making bank off their anti-social followers.
  • Across the border, Canadians, generally a less sociopathic lot than American conservatives, have run out of patience with their own anti-vax protestors.
  • The Washington Post demonstrates how the worst gerrymanders in the US work—like the one here in Illinois.
  • Local bicyclists have had enough of winter, blaming the city for filling bike lanes with slush. But...the city didn't make it snow, right?

OK, back to doing nothing. Cassie, at least, is getting a lot of attention.

NotPetya was NotRussia, says court

Via Bruce Schneier, the New Jersey Superior Court has found that the NotPetya attack that disabled much of Merck's shipping network in 2017 was not an act of war by the Russian government, and therefore Merck's insurer may be on the hook for a $1.4 billion payout:

The parties disputed whether the Notpetya malware which affected Merck's computers in 2017 was an instrument of the Russian government, so that the War or Hostile Acts exclusion would apply to the loss.

The Court noted that Merck was a sophisticated and knowledgeable party, but there was no indication that the exclusion had been negotiated since it was in standard language. The Court, therefore, applied, under New Jersey law, the doctrine of construction of insurance contracts that gives prevalence to the reasonable expectations of the insured, even in exceptional circumstances when the literal meaning of the policy is plain.

The Court also noted that under New Jersey law, 'all risks' policies extended coverage to risks not usually contemplated by the parties unless a specific provision excluded the loss from coverage.

36 Group's article included the court order from December 6th. The ruling only applies to New Jersey, but I expect insurance companies will take hard looks at all of their "all risks" policies to see how much exposure they could have to another cyberattack. I suspect insurers will start demanding people protect their networks better, too, the way they have encouraged people to buy safer cars.

It might also bankrupt Ace American Insurance Co., but that won't change the follow-on effects of this ruling.

Is the Covid test plan a stealth argument for single-payer? One can dream

New Republic Natalie Shure points out the absolute, crashing idiocy of getting private health insurance companies involved in procuring free Covid testing, because their whole reason for being is to prevent the efficient procurement of health care:

This rollout will be a disaster. And really, that should have been obvious: There’s a reason that the Covid-19 vaccines, monoclonal antibody treatments and antiviral drugs have been made free at the point of use, rather than routed through private insurers. It’s because the insurance industry is structurally incapable of achieving anything universally or efficiently.

That’s not hyperbole, it is by design: The role of private insurers within a for-profit multi-payer system is to restrict access as a gatekeeper, determining who is entitled to use which healthcare services and how much they pay for this. To keep these obligations profitable, they employ an army of claims assessors to argue with you, erect arbitrary hoops for providers and patients to jump through to prove you actually need certain care, raise copays and deductibles as high as possible, and foist as much of the paperwork as possible onto patients.

Insurance companies play the single ghastliest role in a legendarily ghastly healthcare system: Whatever invective you can hurl in Big Pharma’s direction, they at least produce something we actually need. Health insurers offer no value whatsoever; they have nothing to do with care itself and if the industry vaporized completely tomorrow, no one would mourn its demise—we’d all be better off. We’re maddeningly stuck with them for now, owing to a host of reasons ranging from inertia to political capture by industry.

[T]his is an object lesson: We’re in the hands of an industry that was never built to serve patients, a problem which no regulatory tweak will ever fix.

Yes, this is true. I learned that early in my career, leading to a long-standing policy of never working for a health insurer in any capacity.

Let me catalog some of my own experiences when big health-insurance companies have claimed to pay me to write software:

  • The first time, a major health-insurance company hired me to write software using a then-current technology, but the project wasn't ready to start, so they involuntarily put me on a team working with obsolete technology and a process so stultifying I didn't actually get to write code. I literally picked up my signing bonus on the way to several interviews in New York, and quit the day I got back. The entire division got dissolved about a year later.
  • Well into my professional career, I went to another major health-insurance company along with 8 other developers and managers, but under the aegis of a moderately-big consulting firm. The on-site project cost the client of about $150,000 per week. Of course, they couldn't get us network access or even a project charter. After about a month and about $750,000 spent, the company cancelled the project. I never even found out what software they proposed to build, had they gone through with, you know, building it.
  • More recently, a major health-insurance company hired me through a recently-acquired subsidiary as the 6th member of a team writing software in a language less than 3% of software developers ever use. I only took the gig because the subsidiary claimed a level of autonomy from the parent company it did not, in fact, enjoy. It occurred to me less than a week after starting that if the product we were building worked, it would undermine one of the key revenue streams of the parent company. Nevertheless, they hired a new developer to the team about every three weeks (despite an admitted 6-month ramp-up time in the language and product), at an average all-in cost of $18,000 per month per developer. I left after three months, as the team grew past 12 people and yet only completed about 5 function points a week.
    The parent company killed not only the project but also the entire acquired company about two years later. The software never shipped, though I did hear they had completed about half of the planned function points.
    On my way out the door I asked my manager what it said to him that the parent company didn't care about burning $200,000 a month on software that he and I both knew a couple of us could build in a garage in four months. He didn't say anything, but Upton Sinclair did*.

You may not see the connection between these failures, or why I jumped ship so quickly the third time, but it's actually really simple. In all three cases, the companies needed to show their shareholders ongoing investments in technology, and needed to show the general public plans for really great tools to make people's lives better any day now. But the best way any of these companies could have made anyone's lives better would be for the US government to obviate their health divisions by paying for our health care directly.

According to the World Bank, the US spends 17% of GDP on health care, behind only Tuvalu and the Marshall Islands (combined populations: 72,000). The first OECD countries on the list are Switzerland (11.9%), Germany (11.4%), and France (11.3%), all of which have vastly better outcomes than the US. How do they achieve this? By not having fat, bloody leeches draining their health spending on useless bullshit. Example: the National Institutes of Health found in a 2020 study that a staggering 34.2% of health-care expenditures in the US went into administration, compared with just 17% in Canada—and Canada has better health-care outcomes overall than we do.

Shure ends her column with an inescapable truth:

[I]t’s pretty telling that the very moment a life-threatening pandemic necessitated mass vaccination, the idea of involving private health insurance companies with that project was absolutely unthinkable. Who in their right mind would attempt to involve them in something urgent? And if they’re such a dismal way to confer access to Covid-19 testing to anyone who needs it, why the hell are they still playing the role they do in the healthcare system writ large?

Let's end this farce and get real single-payer health care in the US, so we can finally enter the 21st century with the rest of the OECD.

* "It is difficult to get a man to understand a thing when his salary depends on him not understanding it."