@darkosubotica this looks great, would love to see a project-based view where you can group resources and visualize how services connect to each other, almost like an architecture diagram built into the console
my biggest issue is the cloud environments, they still feel clunky, i want to spin up a container, run tests, preview changes and iterate without constantly being pushed back to local development, Cursor does this really well with their cloud computers, and i'd happily pay more for something similar
JACK MALLERS: "Gold is stuck in the ground. Bitcoin is stuck in the future." โก
Jack took the stage in Amsterdam to rediscover Bitcoin through Satoshi's white paper, and he breaks down how money, time, energy, and information combine to create the hardest money ever made.
Timestamps:
0:00 - Bitcoin Is the Greatest Discovery
1:02 - Why Bitcoin Is a Discovery, Not an Invention
3:37 - Rediscovering Bitcoin Through the White Paper
5:37 - The 8 References: Money, Time, Energy, Information
6:38 - Why We Need Money (Dunbar's Number)
9:13 - Physical Tokens vs. Lists: How Money Broke
11:13 - The Map Is Not the Territory
13:20 - The Double Spend Problem
15:28 - Everyone Maintains the List: Wei Dai's b-money
19:11 - Time: Why Order Matters
21:22 - Satoshi's Arrow of Time
24:59 - The Timestamp Server & The New York Times
29:36 - Energy: Replacing the Newspaper with Proof of Work
33:20 - How Proof of Work Connects Physics to the Digital World
36:23 - The Difficulty Adjustment: Bitcoin's Heartbeat
38:35 - Gold Is in the Ground. Bitcoin Is in the Future.
41:09 - Game Theory: Why It's Better to Play by the Rules
43:45 - Information: Merkle Trees & the World Cup
46:00 - Chess, Seed Phrases & The Map Is the Territory
48:54 - Bitcoin = Money + Time + Energy + Information
@zachlloydtweets i'd argue observability is just as important as orchestration, without execution traces, failure metrics and cost visibility, you're basically running a very expensive guessing machine
@southphxceleb@ThePrimeagen i see your point, but i don't think an agent needs the entire repo in its context window, targeted retrieval should handle that, the real advantage is being able to coordinate changes across services
@rustypython24@ThePrimeagen being able to retrieve code from github isn't the same as maintaining a consistent dependency graph, coordinating schema migrations and validating changes across services in a single reproducible build environment, but sure, github
@carnotengine273@ThePrimeagen i think it really depends on how you're running your agents, local development is one thing, but once you're orchestrating agents in cloud containers with shared dependencies and integration tests, monorepos start making a lot more sense