https://en.wikipedia.org/wiki/Pork_cycle

https://en.wikipedia.org/wiki/Bullwhip_effect

Check out Jürgen Habermas's Theory of Communicative Action (1981).

Elinor Ostrom's design principles for managing common pool resources (2009 econ Nobel) indicate that nested enterprises have been necessary to scale throughout human history.

Cryptocurrencies allow market participants to communicate value to each other without having to trust other market participants or an institution. Mining verifies transactions and commits them to the public record, earning the miner a fee for their work.

https://strudel.cc/ Strudel on HN: https://news.ycombinator.com/item?id=45571822

Ships coming through the Gulf of Aden to reach African ports south of it are advised to head east until they were south of India (past the Maldives) before heading south, and then head due west to reach their destination. It's really expensive advice though, and not everyone follows it.

I was on the USS Momsen's VBSS team in the Gulf of Aden back in 2010-2012. We showed up with overwhelming force and they knew they'd survive if they didn't fight back. It was relatively safe and boring. We had protection from our reputation.

I think the US Navy's reputation has been squandered in the last year and I've worried it would make VBSS a lot more dangerous.

Edit: we also didn't hear much from the Houthis while I was there. Things got worse in Yemen after my time.

https://www.maritime.dot.gov/msci/2025-012-red-sea-bab-el-ma...

I used to be a purist about IDE configurations, but if everyone isn't on the same page about formatting and stuff like that you see a lot of file churn as things move around.

I would have said the same thing about the .github/ folder, but I've had to add things to it to prevent Copilot from thinking bad patterns in existing code are actually good patterns that should be repeated.

It makes more sense when your communication between teammates is constrained to the repository, because your other communication channels are already saturated. They're meta concerns that really have nowhere to go outside the repository without getting lost.

I thought it was a Windows thing. My Windows work computer is so heavily managed and monitored I assumed that was why Copilot stops being able to get terminal output or find the file I'm looking at. It's the same problem in IntelliJ and VSCode, with different models trying to find things in different ways.

Now that I think of it though, I've only used Copilot at work. At home I use Debian but I've never tried using Copilot. Claude, OpenCode, Gemini, and IntelliJ's AI Chat pointed at local Ollama models never have issues finding files or reading files and terminal output.

I can't imagine we'll really be able to trust AI without it's use in open source software where we can see how reliable it is.

Erlang would offer similar benefits, because what we're doing with these things is more message passing than processing.

Rust is what I'd want agents writing for edge devices, things I don't want to have to monitor. Granted, our devices are edge devices to Anthropic, but they're more tightly coupled to their services.

Putting data centers in space keeps them out of reach of humans with crowbars and hammers, which may have been a vulnerability for those robots Tesla is building.

I haven't found anything more effective than making sure it happens fast enough other devs don't have time to think about disabling it. They might make their changes locally relying on an IDE without running the full build, which pushes the exceptions to the build agent. Developers may not have privileges to modify those builds directly, but complaints and emergencies slowly erode impediments to deploying.