Read the Senate's roughly $1T infrastructure bill
washingtonpost.com
washingtonpost.com
Subtitle D—Climate Change
Subtitle B—Cybersecurity
TITLE II—SUPPLY CHAINS FOR CLEAN ENERGY TECHNOLOGIES Includes:
Sec. 40205. Rare earth elements demonstration facility
Sec. 40207. Battery processing and manufacturing
Sec. 40208. Electric drive vehicle battery recycling and second-life applications program
TITLE III—FUELS AND TECHNOLOGY INFRASTRUCTURE INVESTMENTS
Which includes:
Subtitle A—Carbon Capture, Utilization, Storage, and Transportation Infrastructure
Subtitle B—Hydrogen Research and Development
Subtitle C—Nuclear Energy Infrastructure
Subtitle D—Hydropower
Sec. 40341. Solar energy technologies on current and former mine land.
Sec. 40342. Clean energy demonstration program on current and former mine land.
TITLE IX—WESTERN WATER INFRASTRUCTURE
(going to stop there for now - this is a long bill, lots to digest)
The actual text is pretty terse, but the formatting makes the text much longer than another text would be. If I could have written my college essays in this formatting those 10+ page essays would have amounted to maybe 2-3 pages of words. They make use of many call outs to existing law (for modifications of them) and other sections. The funding stuff is in the first few sections for the rest of the sections.
Edit-in short, the formatting is a little intimidating at first, but it’s nothing a group of programmers and associated-skilled HN readers couldn’t tackle and fast.
Edit-
Here's the .gov source:
https://www.congress.gov/bill/117th-congress/house-bill/3684
https://www.congress.gov/bill/117th-congress/house-bill/3684...
Imagine joining a team using an entire toolstack novel to you. Just takes time to onboard.
As an activist, I got to know the laws, regulations, rules for my domain (federal, state, local). Utterly daunting, intimidating at first. Then over time, not so much.
I also spent a lot of time "popularizing" my activism. Much like some authors popularize science. No one expects to read popular science books and then be able to work in the field. But good communication can distill all the craziness to key points.
Same learning curve with every interesting domain.
There are some similarities, but while this is a popular metaphor it is misleading. Government isn't a machine running code, its a bunch of people pursuing their own interests. Law is one means of establishing and communicating social expectations and consequences as a way of shaping incentive structure in society at large, including government, so that people pursuing their own interests act in “acceptable” ways, but it is very much not deterministic in operation.
Complicated stuff is complicated. Dismissing policy work for its complicity is a oft used trope.
> ...its a bunch of people pursuing their own interests.
What org is immune to proxy fights thru code, rules, budgets?
I've won a few internecine knife fights by shipping code first. (TBH, I lost most of these fights, by whatever means.)
Dismissing various forms of activism because “the law already handles that” is also a popular response, and the “law is code” meme reinforces it. As it does the misreading of laws that are superficially symmetric but don't apply in contexts of symmetric incentives, e.g., the DMCA safe harbors notice and counternotice provisions.
> What org is immune to proxy fights thru code, rules, budgets?
None.
But machines running code are, hence one of the major problems of the “law is code” metaphor.