Google Bought the Prairie

I read this one on my phone this morning, before the day had really started, and I had to read it twice. Not because it was confusing. Because of the direction it points.
Google is building its first data center in Wyoming. Laramie County, near Cheyenne. Seventeen billion dollars, long term. That came from Google's own blog on Thursday.
But the part that actually got me came a day later. The site Google is building on wasn't empty land it picked out. It belonged to a company called Crusoe. Crusoe spent months getting that site ready. Permits. Approvals. A power strategy. All of it. Then Crusoe tried to get Google to sign on as a tenant, and Google said no. On Friday, Crusoe announced it sold the whole unfinished campus to Google instead. The price wasn't disclosed.
So Google didn't rent the building. It bought the project. The developer became the seller, and the tenant became the owner.
Why Wyoming, why now
The power plan is the part worth slowing down for. Google says the campus will run on a 702-megawatt fuel cell development, built by American Electric Power, with carbon capture and storage. The fuel cells burn natural gas and turn it into electricity. Most of the carbon gets captured and stored underground at Tallgrass Energy's sequestration hub nearby. AEP is putting about $4 billion into the fuel cell plant, under a 20-year deal with Google, and it should be fully running by the end of 2028.
Google also says it will pay for 100 percent of the power it uses, cover the grid upgrades its growth causes, and air-cool the data center so it doesn't lean on local water. It expects hundreds of millions in new property taxes for Laramie County.
I want to be straight about what this is and isn't. Nothing here is built yet. The fuel cell plant is a plan with a contract and a date, not a running facility. Google hasn't given a construction schedule or a computing capacity for the data center itself, and nobody has published a capture rate for the carbon capture. A promise with a contract behind it is better than a promise without one. It still isn't a result.
And this fits a pattern that showed up the same week. Bloomberg reported on Thursday that Microsoft is tightening oversight of its neocloud partners, Nebius, IREN, and Nscale, and debating whether to sign new deals with them at all. Those three have disclosed Microsoft contracts worth about $70.9 billion. IREN said the same day that Microsoft asked for a network redesign at its Childress site, which pushed some deliveries back and moved its target of more than $4 billion in annual revenue to January.
Put those two stories next to each other and the direction is hard to miss. The biggest buyers in the AI buildout are done renting capacity from middlemen. They want the site, the power contract, and the schedule in their own hands. I wrote about voters saying no to data centers in dozens of towns earlier this week. Google's answer, three days later, was to go where the land is wide open and buy the project outright.
For me, that's the part that matters for a job search. The scarce work in all of this isn't prompting. It's the building. Permits, power, cooling, fiber, access control. The people who run the building stay, even when the logos on the door change. I said that a few weeks ago about Microsoft's buyouts, and this week said it again, louder.
The pull request moved into the chat
Second story, smaller, closer to my own nights.
On Friday, GitHub made its @GitHub integration generally available in Slack and Microsoft Teams. You type @GitHub in a conversation, and it investigates a bug, files an issue, writes the change, and opens a pull request, all without leaving the chat. In Teams there's a new Canvas view, so the plan, the diff, and a preview sit next to the conversation while your team talks it over. Every issue and PR it opens says where it came from: "Created from a Slack/Teams conversation with @username."
GitHub's own guide this week had a number that stopped me. More than 1.2 billion commits in one week in October, over 400 percent more than a year earlier. That's GitHub's number, not an independent count, so take the precision with a grain of salt. The direction is obvious either way.
The number that matters more came from a Faros AI study GitHub cited. When teams moved from low to high AI adoption, pull requests spent 441 percent longer in review. The code got faster. The reading got slower.
That's the part I keep coming back to. I commit code by hand most nights. Small repos, nothing fancy, and the part nobody can skip is reading what came back and deciding if it's right. CodePath drills the same thing in a different shape. Read the code. Say why it's wrong. Say why it's right.
So the week ends with two pictures that fit together. The companies building the biggest computers on earth stopped renting and started buying the land. And the tool every developer lives in just moved the pull request into the chat window, which means the bottleneck moved to the one thing a chat message can't do for you.
Read it yourself.
Sources: Google, "Google's data center investment in Wyoming," Nov 5, 2026 · Reuters, via The Brief, "Crusoe Sells Unfinished Wyoming Data Center Campus to Google," Nov 6, 2026 · Bloomberg, via AI Agent Update, "Microsoft steps away from risky neocloud deals," Nov 6, 2026 · GitHub Changelog, "@GitHub in Slack and Teams is generally available," Nov 6, 2026 · GitHub's agentic engineering guide, via Medium, Nov 6, 2026
Cover photo: southwest Wyoming sage-steppe, Dave Kimble / U.S. Fish and Wildlife Service, via Wikimedia Commons (CC BY).