255 karma · joined November 5, 2014
The U.S. has (had?) colossal stockpiles of shells and ammunition. There is a false equivalence between the ability to supply the Ukrainians at a rate of 10,000+ shells a day for years on end and the ability of the United States to engage in a major conflict. The Russians are also having trouble keeping their artillery pieces adequately supplied. The calculus is about the acceptable rate of drawdown of stockpiles in relation to the increase in the likelihood of a near-peer conflict arising due to the support given by the very drawdown of those stockpiles. If we give everything we have to Ukraine, and they lose, for whatever reason, then we have disadvantaged ourselves.
However, any major conflict between the United States and a near-peer adversary wouldn’t be so heavily reliant on artillery as this current war is — the U.S. has spent decades building an Air Force that can dominate the battle space in ways that artillery alone cannot match. As Ukraine is set to receive several squadrons worth of F-16s this year, I believe we will see things change. Planes can interdict resupply and troop movements in ways that are beyond the capability of artillery. SEAD aircraft can target and destroy SAM radars to allow large strike packages to accurately blow bridges and rail lines with a much greater radius and accuracy than any other conventional munition.
It is very cynical realpolitik, but Russia’s armed forces have been gutted with this approach.
In practice, this means that most manufacturers do not build systems that are standards compliant by default, and definitely do not install systems that are standards compliant in their initial configuration. Then, individual healthcare practices add customization on top of that, which further complicates data integration.
The thing I’ve noticed when stepping into a codebase where this problem has been allowed to occur is the lack of layers of abstraction. Having those different models built up from the start allows for an application to shift along with the needs of the product. Having a single layer, with the endpoints talking literally directly to the ORM models, almost inevitably leads to calcification, spaghettification, and disastrous performance.
The great irony is that the initial Obamacare proposal was a Republican policy — originally proposed in the mid-‘90s as an alternative to the proposal from the Clinton White House, and implemented in Massachusetts by Mitt Romney when he was the governor. The Republican congress and conservative media machine were so invested in seeing Obama fail that they instead branded it socialism and fought it tooth and nail. It would’ve been a fantastic opportunity for a resurgence in bipartisanship in government, and could potentially have averted the subsequent 14 years of animosity and bitter obstructionism. Ah well, so it goes.