December 03, 2018

Why Ohio Republicans Differ from Texas Republicans

Heard interesting NR “Editors” podcast in which Charlie Cooke asked Reihan Salam why Ohioan Republicanism is different from Texas’s libertarianism:
“Ohio is a state where Gov John Kasich basically reversed his early approach. Soon after coming to office he decided he wanted to curb collective bargaining rights for public employees including firefighters, police officers – so in some ways he was more aggressive than Gov. Scott Walker, his contemporary, yet Kasich then got this intense pushback from organized labor and then he caved. Then he pushed through a Medicare expansion.
"One argument about the Ohio Republican party is that it really did move to the center of opinion in Ohio (whether folks in the Democratic party acknowledge it or not), [since Ohioans] were for Medicare expansion and more pro-life than pro-choice, so that’s where the party went and it wound up being a recipe for the party’s success.

"I guess my big picture thought is that at the state and local level I believe in small government, that’s lean, effective.  At the national level I believe you have to do something about the huge disparities across states. A state like Ohio, or more so West Virginia - has very limited fiscal capacity. What this winds up meaning that 1.5% spent of West Virginia’s GDP on teachers means a very low teacher salary, while 1.5% of New Jersey’s would mean a relatively high teacher salary.

"Those disparities across regions make it really hard to have the kind of decentralized government I’d prefer.  You’re not going to be able to say that Medicare is going to go down to the states and leave them in charge of it when some states just don’t have the fiscal capacity and others do.  That’s why Canada is actually a lot more decentralized country than the U.S. is.  We have to have some sort of redistribution across regions. This isn’t too popular now because the Left, the traditional party of redistribution, happens to now represent all the rich parts of the country.

So I see the politics of Ohio as part of the perverse reaction to how we haven’t gotten things right at the federal level."

All Code Works By Accident

Tweet storm from CTO of VividCortex, Baron Sc​hwartz:
Something that isn’t a “Law,” but has held true through my entire career: when you instrument and measure something, you always learn surprising things.

--The code is doing WHAT?
--That query usually runs in microseconds but sometimes hours?
--We have a server nobody knew about?

This isn’t just database-monitoring-related. It’s true of any system, like… application code; off the shelf software; company finances; my personal health and vital signs—whatever.

Example: what happens to my bodyweight in the 2-3 days after a night of bad sleep? SURPRISE!!!

An example from early in my career as a developer. I discovered that the MySQL protocol has a notion of “warnings” and the number of warnings generated by a query is exposed in the Perl driver. I was curious, so I put a wrapper around our DB access library to check for warnings.

If you’re a software developer, this might not surprise you, but I’m sure some of you wouldn’t believe the broken things I found. I don’t just mean “broken like a tire with low pressure, but the car still drives.” I mean, like the car is in the ditch upside down and nobody knew.

In this specific example, some of the fundamental underpinnings of what the business was supposed to be doing, weren’t working. At all.

The surprises come from realizing your mental model isn’t reality. You think you have awareness of this, but it’s order-of-magnitude wrong. (Meta: your mental model of your mental models’ brokenness, is itself broken.)

You never understand how badly your model of the world and the world itself, have diverged until you measure. Then you’re aghast. But it’s just business as usual. Pick yourself up, go on.

One of the things I learned from that incident was that the stuff I thought was the fundamental, non-negotiable underpinnings of the business was just a nice-to-have.

I didn’t find just ONE thing broken, though. I found dozens, immediately. And many more in subsequent years.

Simple things reveal these totally invisible ways in which your mental models are broken. Quick: pick a server, SSH in, look at any log. Any one. Odds are you’ll find something ghastly.

Pick your system and your tools, do it any way you like. Dig into the bank account statements, look at HR data, whatever. (We recently got a gas+water bill from the city for an astronomical amount.) There’s always broken, weird stuff because NOBODY KNOWS HOW ANYTHING WORKS.

And a lot of what’s broken doesn’t even need to be fixed, despite the engineer’s impulse to make things perfect. The broken world turns on its axis every 24h anyway.
In reply someone said, "All code works by accident." Ha.