Shouldn't it be reasonable for someone to think the infrastructure bill is a good idea but this part is not?
Shouldn't it be reasonable for someone to think the infrastructure bill is a good idea but this part is not?
If your company can only release once every 2–8 years, then naturally the releases would become huge. Unfortunately, our government is so bogged down by divisiveness and the filibuster, etc, that is the state we're in. Except in cases of near outright catastrophe, the only substantive thing they can pass is the budget reconciliation bill, which only requires a majority instead of a super-majority. As a result, that bill becomes enormous, just like the software release.
As with software, the fix is likely to make it easier to pass more small bills, but the very systems that lead to the current status quo make reforming it nearly impossible.
The fact that they want to pass bills which only have a bare majority and not a super-majority is a big part of the problem. If you can't get super-majority (or more like near-unanimous) approval for your bill, odds are that it's not good law or something the government ought to be doing. But the focus is always on these huge, controversial proposals with razor-thin margins and getting them passed over the strenuous objection of approximately half of Congress and a large fraction or possibly even a majority of the population at large. In short, the system is utterly broken.
So those razor-thin margins? They're not necessarily because the bill in question is not good. Indeed, the very politicians who vote against it might concede that it's good - in private. But they have elections to win, and voters to rile up to win them.
Not to mention that Congress, by design, is not really a good representation of public opinion. In fact, Senate is skewed so badly at this point that it's possible to pass and ratify a constitutional amendment through votes of politicians representing less than 1/4 of the country's population, so long as they're concentrated in the right states.
We changed policy at my company from requiring one senior dev to approve pull requests to needing 2. Approvals went from nearly instant to taking much longer, and as a result we did start making longer PRs because of the nuisance of tracking down the second approval for very small changes. When I think about how congress needs 50+ senator approvals for any change to happen, it's no wonder to me that pork and riders became the standard.
Laws are software and should be written and managed like that.
I'd be much more entusiastic about a series of bills. Or a Congress more willing and active about legislation from the liberal-wing. At least that'd fit their marketing better.
But the right-wing is incredibly obstructionist. Without serious action the two are just stuck in a staring contest as the judicial and executive suck up all the power and responsibility they leave on the table.
And who actually writes it? Often industry. In this case maybe law enforcement?
So at this point, your Chesterton fence alarm should be blazing red, because it is unlikely that you, sitting in pure contemplation, can correctly decide that something so widespread and stable across centuries is "preposterously stupid".
So let's try to understand why this is necessary.
To start, we do not live in a democracy, we live in a system where large majorities are needed for something to pass. Democracy is three wolves and two sheep voting on who to have for dinner. It scares the hell out of people, and rightly so.
To defend against this, we institute a number of undemocratic consensus requirements that effectively boil down to large supermajorities being needed in order to get a law passed. This, by the way, is why people are so confused that Biden can't get his infrastructure bill passed even though he has that oh-so-sexy 2 seat margin in the house and a 50-50 senate.
Now imagine you are a team leader with 10 reports, and you are evaluating some course of action, and 6 people feel strongly that option A is the way to go, but 4 people feel strongly that A is a menace and the opposite of A is the correct approach.
Do you go ahead and do A, because 6 is a bigger number than 4? If you do, you are a fool, because you tore your team apart, four people may leave, and you are screwed. You need to govern by consensus, and that means:
1. Abandon option A and find another option, A' that a large majority (8 out of 10) can support. This, of course is the ideal solution. A majority so large that the remaining holdouts feel like assholes for pressing the issue.
2. Come up with a mix, where you do A but also B, where the group that hates A loves B, and is willing to trade doing A for getting B. And the group that love A doesn't like B so much, but is willing to accept B in order to get A. So everyone is a little happy.
#1 we can call "find the one pure course of action we all agree on" approach
#2 we can call "generate a collective basket of actions that, together, we can all agree on".
And very little introspection should tell you that option 1 is almost never available, but option 2 is virtually always available.
So one senator gets more grain subsidies, and in exchange he's willing to tolerate removal of a tax deduction and the subsidy of some solar panels, and another senator hates the solar panel subsidy, but loves getting rid of the tax deduction more, and doesn't much care about the grain subsidy, and the third senator hates getting rid of the tax deduction but loves the grain and solar subsidies more.
Thus there is a policy mix where all of them can agree, even though on each specific policy there is no consensus. This magic by which the sum of policies is able to achieve consensus while each individual policy is not really confuses people who don't understand convex preferences. They think preferences should be linear, not convex. Some even have bizarre moral beliefs about this, which is truly a WTF situation, but that's where we are, people get outraged about literally everything, including convex preferences.
You may have noticed that this basket approach is very reminiscent of the gains from trade you learned in your econ 101 class, and you'd be correct -- this consensus formation is even called "horse trading".
Thus welfare maximization via convex preferences is the process by which a super-majority agreement is reached when there is no one pure action that we all agree on, allowing government to continue while protecting us from the tyranny of majority rules.
The only thing "preposterously stupid" is the shallow dismissal of this consensus formation, seeing as how it is the bedrock that allows consensus to be reached in any group situation, from being an engineering team lead to running a local Kiwanas club to running congress.
Next time you face a divided membership in whatever team you are leading, start some creative horse trading -- there is a good chance you will be able to reach consensus.