← Back to context

Comment by radley

6 months ago

It's not really targeted at tech, insomuch as at Democrats.

Everyone assumed it was a traditional accounting hack. But given the timing and the reinitialization, it's clearly political, not economic.

The code is a strategic time-bomb designed to cause a high-profile economic downturn during a presidential election cycle, specifically when the following president is a Democrat and Republicans have a house majority.

It was used to harm Biden's economy, and it will happen again in 2030 if the next president is a Democrat. While deferred, it will be spun as a major Trump "economic achievement" for the midterms, because companies will be able to afford to hire again.

The tech industry is merely high-profile fodder for extreme politics. It really is that petty.

The Democrats had control of the presidency and the house in 2022 when this provision first went into effect but had 2 fewer senators (1 fewer if you count the tie-breaking VP). Why didn't they try to change it? Is there some reason a change in the tax code like this can't be modified or repealed once its in place?

  • Politics are complicated.

    Generally, in tax bills they try to keep them "neutral" where any tax cuts or tax breaks are coupled with tax increases elsewhere BUT they tend to report the 10-year affect for whatever reason. This bill provided a ~30% cut in corporate tax on profits, with a delayed increase in tax cost on Software R&D pushed to the next term.

    If the next party wants to reverse it, they'd have to find the money with an increase in tax - directly undoing it would be a ~50% increase in corporate tax rate, which (I guess?) would be a tough sell politically. Meanwhile, the tax code on software engineering sounds too niche to expend political capital on.

    Either way, its another example of how corporate America is trading long-term growth (R&D, product development) for short term gain (lower taxes today).

  • Why should they? Why did we allow a president to put in tax raise for the future. Replicants were playing politics from the start. Pass a bad bill, and then hope to get about it when the bad parts kick in when the other side woo be in power

If this was passed in 2017 to go into effect during the next presidential term, wouldn't that only work as a time bomb for Biden's presidency if Trump didn't expect to win a second consecutive term?

Given the history of prior presidents winning 2 consecutive terms, it seems like Trump could have reasonably expected a 2022/2023 tax change to be his problem.

This is just wrong. It was passed in 2017 (during Trump’s presidency). It was to go into effect in 2020 (a presidential election year during Trump’s presidency). He hoped to be re-elected.

  • No. It went into effect in 2022 [0], which means the timeline absolutely does track with OP's theory. That gives a hypothetical Trump term 2 a full year to fix it but also imposes enough of a time crunch that they could plan on sabotaging attempts to fix it by another party.

    I'm not saying it's the actual story, but the timeline does track.

    [0] Page 60, Sec 1306(e) sets the date: https://www.congress.gov/115/bills/hr1/BILLS-115hr1enr.pdf

    • I don’t think it really changes the narrative. 2020 was also a congressional election year, even had Trump won (as he appeared to want desperately) he could not have been assured of a Republican congress.

      My argument is simple: Occam’s Razor

      The Republicans in congress put the provision in solely as a gimmick to get past the CBO.

      Frankly I don’t think legislators in either party are competent enough to have foreseen the consequences and even if they had been they wouldn’t have put a bomb like this in that would be more likely than not to backfire and affect them.

      I just think that too often people interpret incompetence as malice, especially nowadays when things are so polarized that it’s fashionable to hate people who differ with one’s political opinions.

      2 replies →