
Sign up to save your podcasts
Or


Most engineering failures don’t come from bad algorithms or insufficient data.They come from something much more basic:
We didn’t define the system properly.
That’s what this episode of Coordinated with Fredrik is about — system boundaries, thermodynamics, and how we should think about a home once it stops being a passive consumer and starts behaving like an active energy system
Where does a system begin — and where does it end?
This sounds almost philosophical, but it’s one of the most practical questions an engineer can ask.
Every system needs a boundary. Without one, it’s impossible to reason about control, optimization, or even responsibility. This is true for software systems, mechanical systems, and very much so for energy systems.
Ludwig von Bertalanffy, the father of systems theory, once said:
“The boundaries of a system are not given in nature but are determined by the observer.”
That’s true in many domains — but energy is special.
In energy systems, the boundary is not arbitrary.It is physical, legal, and enforced.
That boundary is the electricity meter.
The meter is not a billing device
We tend to think of the electricity meter as something purely administrative — a device that exists to calculate our bill. But that’s a mistake.
The meter is the point of common coupling (PCC) between your home and the grid.Everything you consume passes through it.Everything you export passes through it.
It is where:
* Ownership changes
* Responsibility changes
* Grid physics ends and home physics begins
* Billing, tariffs, export limits, and fuse constraints apply
In thermodynamic terms, it is the membrane between two systems.
Once you see the meter this way, the right question stops being “What is my inverter doing?” and becomes:
What crosses this boundary, when, and under what constraints?
That single shift changes everything.
Why the old model worked — and why it broke
Historically, homes were boring.
They were passive loads.Power flowed in one direction.Individual behavior didn’t matter much.
From the grid’s perspective, you could aggregate thousands of homes and get remarkably accurate forecasts. The system was statistically predictable because nothing interesting happened at the edges.
So our tooling reflected that worldview.
We read registers.We polled Modbus TCP.We collected telemetry.
And for a long time, that was enough.
The moment homes stopped being predictable
Then we added things.
Solar PV at the edges of the grid.Batteries that store energy over time.Electric vehicles with large, deadline-driven loads.Heat pumps with thermal inertia and weather-dependent efficiency.
Suddenly:
* Power flows both ways
* State matters (SOC, temperature, availability)
* Timing matters more than magnitude
* Homes can go from “doing nothing” to exporting 8 kW in seconds
From the grid’s point of view, a home that used to be a smooth, boring signal becomes bursty, stateful, and hard to predict.
A house might sit at zero net flow for hours — perfectly balanced by solar and storage — and then abruptly inject a large amount of power when a battery fills up or a cloud passes.
The old statistical assumptions no longer hold.
A short detour into thermodynamics (the useful parts)
Thermodynamics gives us the correct mental model for all of this.
Clausius summarized the first and second laws in a single sentence:
“The energy of the universe is constant. The entropy of the universe tends to a maximum.”
Everything that happens inside a home — or any site — sits inside that frame.
The first law: accounting
Energy doesn’t disappear. It transforms.
For a home:
* Energy can be stored chemically (batteries)
* Stored thermally (hot water tanks, slabs, buildings)
* Converted between electrical and thermal forms
* Exported or imported across the meter
Power is just energy per unit time.Storage is what happens when generation and consumption don’t align in time.
In that sense, storage isn’t a device category.It’s a consequence of time mismatch.
The second law: usefulness
The first law tells us energy is conserved.The second law tells us not all energy is equally useful.
Electricity is high-quality energy.Low-temperature heat is low-quality energy.
You can easily turn electricity into heat.You can’t easily turn heat back into electricity.
This is why heat pumps matter so much: they don’t create heat — they move it, exploiting temperature differences to deliver more heat than the electrical energy they consume.
None of this is optional. Software that ignores the second law will always look good in simulations and fail in reality.
From signals to systems: Site, Device, DER
This is where thermodynamics meets software architecture.
Site
The site is the system boundary.Everything behind the meter.
A site has:
* Objectives (cost, comfort, self-consumption, grid services)
* Constraints (main fuses, export limits, tariffs)
* State that evolves over time
Optimization only makes sense at this level.
Device
A device is something you can communicate with.
It has:
* Protocols (Modbus, REST, cloud APIs)
* Registers
* Firmware versions
* Vendor quirks and bugs
Devices answer the question:What can I technically talk to right now?
That’s necessary — but insufficient.
DER (Distributed Energy Resource)
A DER is a logical abstraction.
It represents capability, constraints, and state — independent of protocol.
A battery DER might represent:
* Total capacity
* Current SOC
* Charge/discharge limits
* Efficiency
Whether that battery consists of one module or twenty cells doesn’t matter unless it affects system behavior.
DERs answer the real question:What can this resource do for the system?
Devices are how you talk.DERs are what you reason about.
Why this abstraction matters
Once you define:
* The boundary (the site)
* The resources (DERs)
* The constraints
Control stops being reactive.
The problem becomes:
What should the energy flow across the meter look like over time?
The grid doesn’t care how your system is wired internally.It cares about magnitude, direction, and timing at the boundary.
In that sense, the meter becomes the objective function.
Homes are no longer loads
A modern home has:
* State
* Constraints
* Objectives
* Time-coupled decisions
That’s not a load.
That’s an agent.
We inherited an energy system architecture from a time when homes were boring. They aren’t anymore. That creates real challenges — but also real opportunities.
And none of them can be addressed without going back to first principles and defining the system correctly.
Episode Summary
We tend to think about infrastructure in physical terms: wires, pylons, transformers, steel and copper. But modern systems—especially energy systems—are held together by something less visible and just as critical: the messaging layer.
In this episode, we trace the hidden history of how machines learned to talk to machines. From Wall Street trading floors to oil pipelines in the desert, from telecom switches in Sweden to rage-coded weekends in Silicon Valley, this is the story of frustration-driven innovation.
We explore:
* Why synchronous “telephone-style” software broke at scale
* How publish/subscribe became the software equivalent of a system bus
* Why RabbitMQ, Kafka, NATS, and MQTT exist—and what specific pain each one was born to solve
* The architectural tradeoffs between smart brokers and dumb pipes
* Why replayability, liveness, and reliability are fundamentally different goals
* How modern systems increasingly combine all of these tools
* And why the next architectural leap will come from today’s friction points
This episode isn’t about choosing the “best” messaging system.It’s about understanding why each one exists, and what happens when you use the wrong tool for the wrong kind of problem.
Key Concepts
* Messaging as the nervous system of physical infrastructure
* Subject-based addressing and decoupling
* Smart broker vs. dumb broker architectures
* Append-only logs and replayability
* Control planes vs. data planes
* Edge constraints and low-power networks
* Friction as a signal for architectural evolution
Mentioned Systems & Ideas
* TIBCO and the original information bus
* AMQP and the open-standard rebellion
* RabbitMQ and Erlang’s “let it crash” philosophy
* Kafka and the log as the source of truth
* NATS and the “dial tone” model
* MQTT and constraint-driven protocol design
* ZeroMQ, Pulsar, Redis Streams (briefly)
The Invisible Grid
How Messaging Systems Became the Nervous System of Modern Infrastructure
Close your eyes for a moment.(Not if you’re driving—but mentally.)
When we talk about infrastructure, we picture the physical grid: copper wires, transformers humming in empty fields, pylons cutting across landscapes. It’s tangible. You can touch it. You can see it rust. You can watch a tree fall on it.
If that grid fails, everything stops.
But there is another grid—one we almost never visualize.
An invisible grid, running inside software.A nervous system made of messages.
And just like the physical grid, when this system clogs, desynchronizes, or collapses, the lights go out anyway—no matter how much copper is in the ground.
Modern energy systems, financial markets, cloud platforms, and industrial control loops don’t merely use software. They depend on it at the level of physics. Signals must arrive on time. Control decisions must propagate. State must remain coherent across thousands or millions of moving parts.
This post is about how we got here.
Not as a clean, planned evolution—but as a genealogy of frustration.
The Original Sin: The Telephone Call
Early software systems communicated the same way humans did: by calling each other directly.
Application A opens a connection to Application B, waits for it to respond, sends data, and blocks until it hears back. This is synchronous coupling—the software equivalent of a phone call.
It works fine for two systems.
It collapses at scale.
On a trading floor—or an energy grid—one event must fan out to many consumers: risk engines, dashboards, control systems, settlement layers. In the telephone model, the sender must call each one, sequentially.
If any receiver is slow or unavailable, everything backs up.
Latency accumulates. Failure cascades.In finance, you go bankrupt.In energy, you destabilize the grid.
This brittleness created the first great insight.
The Software Bus: Publish, Don’t Call
In the mid-1980s, an engineer looked at a computer motherboard and asked an uncomfortable question:
Why is software dumber than hardware?
A CPU doesn’t “call” the graphics card. It broadcasts onto a system bus. Whoever is listening picks up the signal. The sender doesn’t care who receives it—or if anyone does at all.
That idea became publish/subscribe.
Instead of sending data to addresses, you publish it to subjects.Instead of knowing who consumes it, you just agree on what it means.
This decoupling was revolutionary. It gave us the first real software nervous system.
And it worked—so well that it created the next problem.
When Middleware Ate the Budget
By the early 2000s, large enterprises had dozens of incompatible messaging systems. Each vendor had its own protocol, its own servers, its own licensing model.
Banks were spending absurd portions of their IT budgets not on business logic—but on plumbing.
The rebellion that followed wasn’t technical at first.It was economic.
Why don’t we have a TCP/IP for messaging?
That question led to open standards. And open standards led to open source.
RabbitMQ and the Power of “Let It Crash”
RabbitMQ emerged from a near-perfect alignment between problem and tool.
The problem: routing messages reliably, flexibly, transactionally.The tool: Erlang—a language built for telecom switches that cannot go down.
Erlang’s philosophy is radical: don’t prevent failure—contain it.
Instead of one giant program sharing memory (where one bug burns the house down), Erlang runs millions of tiny isolated processes. If one crashes, a supervisor instantly replaces it.
Failure becomes routine. Boring. Managed.
RabbitMQ embodies this mindset. It is a smart broker: it routes, retries, buffers, tracks acknowledgements, and guarantees delivery.
It is a post office.
And like all post offices, it has limits.
Kafka and the Log That Changed Everything
When LinkedIn tried to track everything, the post office model broke.
Too much sorting. Too much state. Too much overhead.
The breakthrough was deceptively simple:Stop routing messages. Start recording history.
Kafka treats data as an append-only log—an immutable sequence of events. Producers write to the end. Consumers read at their own pace. The broker doesn’t track who’s done what.
This aligns perfectly with disk physics. Sequential writes are fast. Replays are free. History becomes an asset.
In this model:
* The log is the source of truth
* Databases are just materialized views
* You can replay the past with new intelligence
Kafka isn’t a post office.It’s a newsstand.
NATS and the Dial Tone
Then came cloud platforms, microservices, and another frustration.
Messaging systems had become pets—delicate, stateful, needy.But cloud infrastructure demands cattle—replaceable, disposable, boring.
NATS was born from that tension.
Its original design was ruthless:
* No persistence
* No buffering for slow consumers
* No guarantees beyond “best effort right now”
If you’re too slow, you’re dropped.If no one’s listening, the message vanishes.
This sounds dangerous—until you realize what it’s for.
Control planes. Heartbeats. Service discovery. Real-time signals where the latest state matters more than history.
NATS is not a database.It’s a dial tone.
MQTT: Innovation Under Constraint
The most elegant designs often come from the harshest constraints.
MQTT was built for oil pipelines in the desert, running over satellite links so slow and expensive that saving two bytes mattered.
The result was a protocol stripped to its bones:
* Tiny headers
* Persistent low-power connections
* Explicit handling of unreliable networks
* A “last will and testament” for dead devices
Years later, the same properties made MQTT perfect for smartphones.
From oil rigs to billions of pockets.
Today, MQTT is the language of the edge.
Synthesis: No Winners, Only Tradeoffs
There is no perfect messaging system.
Each of these tools exists because an engineer hit a wall:
* Too slow
* Too heavy
* Too expensive
* Too fragile
They encode those frustrations into architecture.
That’s the real lesson.
Modern systems don’t pick one.They compose:
* MQTT at the edge
* Kafka for history and analytics
* NATS for control and coordination
* RabbitMQ for transactional work
Different pipes for different fluids.
The Real Question
Every major evolution in messaging came from irrita…
Most conversations about supplements are useless.
They start too early, aim too low, and ask the wrong question.
This is not a beginner’s guide. This is not “eat your vegetables” or “drink more water.” This is a discussion for someone who has already done the hard part.
You wake up early.You train consistently.Alcohol is gone.Food is clean.Sleep is a priority.
In other words: the foundation is already built.
So the real question becomes uncomfortable, almost heretical:
When you’re already operating at the 95th percentile of discipline, does supplementation actually move the needle — or are you just creating expensive urine?
This episode of Coordinated with Fredrik was built to answer that question with one lens only: return on investment.
Not vibes. Not biohacker cosplay. ROI.
The Core Thesis: No Magic Pills, but Real Feature Upgrades
After combing through meta-analyses, randomized controlled trials, and clinical protocols published through early 2025, the answer is not a naïve yes.
It’s a qualified yes.
Supplements do not replace fundamentals. They do not compensate for poor sleep, weak conditioning, or a chaotic life. But even a perfect modern lifestyle leaves gaps — gaps created by:
* Soil depletion
* Indoor work
* Chronic cognitive load
* Latitude and lack of sun
* Stress-induced mineral loss
The opportunity lies in biological arbitrage: small chemical inputs that produce disproportionate output for a high-functioning executive.
Out of all the noise, four compounds consistently survive scrutiny.
Not exciting. Not exotic. Just effective.
The Core Four
1. Creatine: Decision Fatigue Insurance
Creatine has undergone one of the most dramatic rebrandings in modern science.
Once dismissed as “gym bro powder,” it is now increasingly understood as cognitive fuel.
The reason is simple: the brain is an energy-hungry organ. When ATP runs low, processing speed, attention, and working memory degrade. Creatine acts as the fastest phosphate recycling system in the human body — a rapid charger for neural energy.
Recent meta-analyses show statistically significant improvements in:
* Short- and long-term memory
* Attention span
* Processing speed
The benefits are strongest under metabolic stress: sleep deprivation, high cognitive load, intense work periods. In one striking study, a single high dose of creatine largely preserved cognitive performance during 21 hours of wakefulness.
For a CEO, this is not about muscle.
It’s about staying sharp when the margin for error is thin.
Protocol
* Creatine monohydrate only
* 3–5 g daily
* No loading phase
* Consistency over intensity
Kidneys: safe.Hair loss: unsupported by evidence.Marketing variants: ignore them.
2. Magnesium: The Off Switch
If creatine is about output, magnesium is about recovery.
Magnesium quietly governs over 300 enzymatic reactions, including energy metabolism, neural signaling, and muscle relaxation. Yet 50–60% of adults in the Western world are insufficient.
Why?
* Mineral-depleted soil
* Stress-driven magnesium loss
* Caffeine and training increasing excretion
For high performers, magnesium deficiency is almost structural.
Recent imaging studies link adequate magnesium intake to structurally younger brains, fewer white matter lesions, and improved cognitive resilience. One targeted form, magnesium L-threonate, has shown particularly strong effects on brain magnesium levels due to its ability to cross the blood–brain barrier.
Choosing the form
* L-threonate: cognitive longevity, focus, brain health
* Bisglycinate: sleep quality, relaxation, recovery
* Oxide: avoid (unless you want a laxative)
Take it in the evening. Make it a ritual.
3. Omega-3s: Structural Maintenance of the Brain
Omega-3s are not supplements. They are building materials.
EPA and DHA are structural components of neuronal membranes. Their status can be measured directly through the omega-3 index — a four-month rolling average of membrane composition.
Targets matter:
* <5%: common, suboptimal
8%: associated with cardiovascular and cognitive protection
* 10–12%: what aggressive optimizers aim for
Higher omega-3 index levels correlate with:
* Reduced cardiovascular events
* Slower cognitive aging
* Improved mood stability
Plant-based omega-3s (ALA) do not convert efficiently. For DHA, conversion is effectively negligible. If you don’t eat fatty fish, supplementation is non-negotiable.
Key insight: do not guess. Test. Adjust dosage based on blood data.
Potency vs purity is a real trade-off:
* Fish oil: higher doses, contamination risk
* Algae oil: cleaner, lower doses
* Fish roe: superior bioavailability, lower required intake
There is no ideology here. Only measurement.
4. Vitamin D: System-Wide Regulation
Vitamin D is misclassified. It is not a vitamin in function — it is a hormonal regulator.
It directly influences the expression of over 1,000 genes. Above the 37th parallel, winter synthesis is effectively zero. For Northern Europe, deficiency is structural.
Beyond bone health, recent data links adequate vitamin D levels to:
* Slower telomere shortening
* Lower dementia incidence
* Improved immune and metabolic regulation
The mistake is dosing without context.
High-dose vitamin D without:
* Magnesium (cofactor)
* Vitamin K2 (calcium traffic control)
…creates risk.
Safe stack
* Vitamin D3: often 5,000 IU+ (test to confirm)
* Vitamin K2 (MK-7): 100–200 mcg
* Adequate magnesium intake
This is an ecosystem, not a pill.
The Stoic Frame: Don’t Major in the Minors
Supplements are the final 5%.
They polish the machine — they do not build it.
Zone 2 cardio.Sleep.Strength training.Consistency over decades.
Miss a day? Nothing breaks.Forget a week? No catastrophe.
The stoic advantage is restraint.
The goal is not obsessive optimization. The goal is protecting cognitive capital — the asset that compounds everything else you do.
The real biohack isn’t copying anyone’s protocol.
It’s knowing your own numbers.
Measure. Adjust. Repeat.
That’s the whole game.
This post is adapted from the podcast episode transcript and reflects the discussion as presented in Coordinated with Fredrik .
I’ve been thinking about this paradox since my PhD days. Back then I was trying to make ships more fuel efficient, believing it would reduce emissions. Then I discovered William Stanley Jevons and his 1865 book “The Coal Question.” It nearly broke me.
Jevons noticed something counterintuitive about James Watt’s steam engine. Watt made steam engines roughly four times more efficient than the old Newcomen engines. Common sense says this should have reduced coal consumption. The opposite happened. Coal use exploded.
Why? Because efficient steam power suddenly became cheap enough to use everywhere. Factories, railways, mines. The efficiency didn’t save resources. It unlocked demand that hadn’t existed before.
“It is wholly a confusion of ideas to suppose that the economical use of fuel is equivalent to a diminished consumption. The very contrary is the truth.”
That quote has stuck with me for years.
Now look at AI. In 2024, data centers consumed about 415 terawatt hours globally, roughly 1.5% of all electricity. Projections put that at 945 terawatt hours by 2030. Virginia already sends 26% of its electricity to data centers. Ireland is at 21-22%.
DeepSeek showed you can train competitive models far more cheaply. Did that reduce compute demand? No. It opened the door for more companies to train more models. Same pattern as Watt’s engine.
Here’s where I land on this: the paradox isn’t a warning. It’s a description of how economic systems work. Fighting it is pointless. The question is whether we can meet rising demand with clean, abundant energy.
Solar is already the cheapest electricity source available. The sun has always been Earth’s power plant. Even the coal Jevons worried about is just ancient stored sunlight.
We’re going to use more electricity. A lot more. That’s not a crisis. That’s an opportunity to finally build the energy system we should have had all along.
More on this in future episodes.——SHOW NOTES:
Episode recorded Sunday morning, Kalmar, Sweden
The History
* William Stanley Jevons, Liverpool-born economist, published “The Coal Question” in 1865
* UK consumed 93 million tons of coal annually at the time, nearly all of Britain’s energy supply
* Coal production had grown 3.5% per year for the previous 80 years
* British coal production didn’t peak until 1913, almost 50 years after Jevons wrote his warning
The Famous Quote “It is wholly a confusion of ideas to suppose that the economical use of fuel is equivalent to a diminished consumption. The very contrary is the truth.”
The Steam Engine Story
* Thomas Newcomen developed the atmospheric engine in 1712, less than 1% efficient
* James Watt (born 1736) was given a Newcomen engine to repair in 1763
* Conceived the separate condenser idea in 1765, patented in 1769
* Watt’s engine was roughly 4x more efficient than Newcomen’s
* Result: coal consumption exploded because steam power became economical for everything
The Paradox More efficiency didn’t reduce coal use. It made steam power cheap enough to deploy everywhere. Textile mills, railways, factories. The efficiency unlocked demand that didn’t exist before.
Modern Examples
* More fuel-efficient cars → people drive more
* LED lights → we install far more lights
* Air conditioning → billions of new users as it became affordable
AI and Data Centers Today
* 2024: Global data centers consumed 415 TWh (1.5% of global electricity)
* 2030 projection: 945 TWh (nearly 3% of global electricity)
* Data center electricity growing 15% per year (4x faster than overall electricity growth)
* US: 4% of total electricity goes to data centers
* Virginia alone: 26% of state electricity to data centers in 2023
* Ireland: 21-22% of national electricity to data centers
The DeepSeek Parallel Early ChatGPT models might be the Newcomen engine of AI. Useful for specific tasks but extremely inefficient. DeepSeek and other breakthroughs are making AI cheaper and more efficient. According to Jevons Paradox, this won’t reduce compute demand. It will increase it.
The Optimistic Take Rising electricity demand isn’t a problem if we meet it with abundant, cheap, clean sources. Solar is now the cheapest electricity source on earth. The sun has always been Earth’s power plant. Even fossil fuels are just stored sunlight.
In this episode, I share a candid, thinking-out-loud reflection on how fast agentic coding is evolving—and what that speed means if you’re building and leading a company right now.
From a CEO’s perspective, I talk about why old mental models for software development no longer fully apply, and why it’s no longer enough to ask how we build, but who (or what) should be doing which parts of the work. I don’t have all the answers—and I’m very explicit about that—but I believe it’s better to share pragmatic, half-formed thoughts than to wait for perfect clarity.
Over the last few weeks, my own workflow has shifted dramatically. I describe moving from “sitting in a terminal pressing yes” to running agents on sandboxed virtual machines, orchestrating long-running tasks, and increasingly treating AI systems less like tools and more like collaborators. At times, it genuinely feels magical—and at other times, cognitively overwhelming.
“If you can suddenly build things that weren’t possible just weeks ago, you can’t rely on old standards of thinking.”
I also explore what feels like the next inflection point: moving beyond single agents toward true multi-agent orchestration, where planning, coordination, and even delegation are increasingly handled by AI itself. Today, humans still act as the operator-in-the-loop. Tomorrow, that role may shift upward—toward taste, direction, and judgment rather than execution.
Throughout the episode, I reflect on what this means for engineers, “intelligence workers,” and small teams—especially in high-impact domains like the energy transition, where I’m grateful to be building with a 10-person team using these new tools.
This episode is less about conclusions and more about momentum. It’s a snapshot from an extremely exciting moment in time—shared in public, in real time, while everything is still changing.
For the first time, this isn’t AI-generated or scripted — it’s a live, unscripted monologue recorded early in the morning, just before heading to work. No plan, no outline. Just me speaking freely, partly for anyone listening, and partly for myself.
I wanted to try this format because the last few weeks have felt intense. The pace of change in AI — especially what many are calling the agentic era — has accelerated in a way that feels qualitatively different from past hype cycles. This time, it feels real. And with that comes both excitement and stress.
One recurring feeling I talk about is how traditional software moats are eroding. Having large codebases, teams of engineers, and long-lived products used to be a clear advantage. Increasingly, those same assets can also become constraints. The more you own, the more you have to maintain — and the slower you can move. There’s a growing case for minimalism: owning less, building faster, and treating software as something that can be created, adapted, and discarded quickly.
Internally, we’ve been pushing agentic coding tools hard, especially Claude Code. I’ve experimented with AI-assisted development for a long time — Cursor, VS Code integrations, Codex, and others — but something clicked recently. Around early December, the combination of Claude Code, Opus 4.5, and effectively unlimited usage changed how productive these tools felt. It finally started working the way it should. That shift has been genuinely mind-altering.
Zooming out, I’m broadly optimistic. The evolution of AI and agentic tools is good for society and the economy, even if the transition will be messy. Uncertainty creates opportunity, and builders who enjoy being at the frontier are likely to thrive. We may even be closer to AGI than many previously thought, which means second-order effects we haven’t anticipated yet — including in areas like healthcare, where people closest to real problems could now build their own solutions at almost no cost.
Of course, most people won’t take advantage of this. Just like with the internet, the tools will empower a minority — but that minority is no longer blocked by access to capital, engineering teams, or specialized skills. Ideas and the will to execute are becoming the main bottlenecks.
This episode is short, informal, and experimental. I’m not yet sure if this format will continue, but it felt worth trying. Sometimes thinking out loud is the best way to understand what’s actually changing.
More to come — maybe.
A War Room, Not a Holiday
This episode of Coordinated doesn’t begin with a product launch or a funding announcement. It begins in silence.
December 26, 2025. The food is gone, the house is quiet, and most of the tech industry is still mentally offline. That’s when Fredrik, CEO of Sourceful, opens Claude Code “just to see what it can do.”
What follows over the next four weeks—through January 22, 2026—is not incremental progress. It’s an existential reckoning.
This episode is a case study in leadership during what increasingly feels like an agentic inflection point: a moment when the constraints that defined software work for decades simply collapse.
The Snowy Epiphany
At first, the logs show curiosity. Then surprise. Then stress.
By the morning of December 26, Fredrik is no longer experimenting—he’s replicating core parts of Sourceful’s codebase. Rust pipelines. Test suites. Simulated runs of the ZAP platform. All in a single weekend.
This is not empowering. It’s destabilizing.
If a CEO—someone who does not identify as a traditional developer—can do this in days, what does that say about the barriers the organization assumed were real?
The realization lands hard: the moat was never syntax. It was time. And time just collapsed.
That emotional whiplash mirrors what others in the industry were reporting at the same moment. Andrej Karpathy described feeling both 10× more powerful and simultaneously behind. Speed had increased, but so had the ceiling—and the floor had dropped out entirely.
January 3rd: The Manifesto
On January 3rd, the private reckoning becomes public.
Fredrik posts a blunt, unambiguous message internally. It is not inspirational fluff. It is a directive:
* Do not identify as a developer.
* Identify as an engineer who solves problems.
* There is no leaning on tenure.
* I expect a few terminals crunching away all the time.
The framing is binary: adapt, or the company is doomed. Harness this shift, or miss the most exciting opportunity of a lifetime.
This wasn’t happening in a vacuum. Across the industry, leaders were independently reporting similar accelerations. David Holz and Tobi Lütke both described shipping more in weeks than in years through what’s now casually called “vibe coding.”
This wasn’t hype. It was structural.
From Coding to Orchestration
One signal makes the shift undeniable: Stack Overflow traffic falling back to 2008 levels.
The era of searching for syntax is ending. We are moving from task execution to system orchestration.
For Sourceful—working with real-world energy grids, physical infrastructure, and regulatory constraints—this matters deeply. The work was never about typing code. It was about understanding systems. The new tools simply strip away the pretense.
The Infrastructure of One
You can’t demand 10× speed without providing a rig.
That leads to one of the most concrete takeaways of the episode: the Mac Mini employee.
The idea is simple:
* Your laptop is for you.
* Your agent needs a persistent home.
A headless Mac Mini, running 24/7, accessed remotely, becomes a permanent agent workstation. No sleeping when the laptop closes. No lost context. No runaway cloud bills.
For long-running simulations, inference loops, and overnight experimentation, a $600 machine outperforms many cloud setups on both cost and continuity.
This isn’t theoretical. It’s operational leverage.
Why Monorepos Win in an Agentic World
Another reversal emerges: monorepos.
Microservices and repo fragmentation were designed to reduce human cognitive load. Agents have no such limitation. They want context—all of it.
In a monorepo, an agent can see:
* The API
* The frontend that consumes it
* The database schema underneath
* The simulation models upstream
Hallucinations drop. Refactors become holistic. A change to how solar output is modeled can propagate cleanly across the entire stack in one pass.
Fragmented repos blind your most powerful worker.
The RALF Loop: Engineering Over Typing
At the heart of the episode is the RALF loop (Read–Analyze–Loop–Fix), popularized by Jeffrey Huntley.
The premise is uncomfortable but increasingly true: typing code is becoming a commodity. Engineering—thinking, specifying, anticipating failure—is not.
In a RALF workflow:
* Humans define the problem, constraints, and edge cases.
* Agents write tests.
* Agents write code.
* Agents refactor.
* Agents repeat until the spec is satisfied.
Weeks of work collapse into hours—not because quality drops, but because feedback loops vanish.
Persistence, Memory, and Councils
The biggest bottleneck isn’t intelligence. It’s memory.
Tools like persistent Claude harnesses (internally nicknamed “snake oil”) compress massive conversation histories by up to 95% without losing decisions or constraints. That makes week-long engineering conversations viable again.
For high-stakes systems, one agent isn’t enough. The episode outlines LLM councils: multiple agents independently proposing solutions, with a judge agent synthesizing and critiquing them.
It’s peer review at machine speed.
The Skill Flip
One of the most unsettling shifts discussed: designers are becoming top-tier builders.
As Ryan Nystrom observed at Notion, product designers—armed with taste, empathy, and agents—are shipping production-ready systems. The AI handles syntax. Humans supply judgment.
If your value was “I know React best,” you’re exposed.
If your value is architecture, coherence, and system thinking, you’re more valuable than ever.
This aligns with David Heinemeier Hansson’s updated triad:
* Computers make it work
* AI makes it fast
* Humans make it beautiful
Strategy: Platforms, Not Features
Zooming out, the episode lands on a critical business implication.
Generic SaaS is getting crushed. If an agent can build it in a week, it will race to zero.
The value concentrates at the extremes:
* Cultural, story-driven consumer apps
* Deep, physical-world platforms: energy, biotech, defense, infrastructure
Sourceful lives on the second edge. You can’t “vibe code” grid compliance in Germany or physical connections to inverters.
That’s why the warning from Gokul Rajaram matters: build platforms, not features. Features are faucets. Platforms are the pipes in the walls.
The Open-Source Dilemma
The episode doesn’t dodge the dark side.
As agents ingest public code wholesale, some maintainers—like Mark Schmidt—are closing source entirely, arguing that open code now directly trains replacements.
For companies with real IP—physics models, grid algorithms—the question is unavoidable: what stays open, and what must be protected?
There’s no easy answer. But pretending the trade-off doesn’t exist is no longer viable.
Money as Exhaust
The episode ends not with tactics, but philosophy.
Borrowing from Foz, Fredrik frames money as exhaust—not the goal, but the byproduct of a well-built engine.
Obsess over the real problem. Build the strongest system possible. Let the exhaust take care of itself.
That December stress wasn’t weakness. It was signal.
While others unplugged for the holidays, Sourceful spotted the shift early. The task now isn’t panic—it’s institutionalization: using agents, infrastructure, and process to sustain speed without burning out humans.
Or as the episode signs off:
Don’t chase the exhaust.Build the engine.
Listen to the full episode of Coordinated by Fredrik for the complete discussion and practical details behind this transformation.
https://www.vibekanban.com/
The most uncomfortable truth in crypto is not that the technology fails. It’s that it works exactly as designed—right up to the moment a human touches it.
This episode begins with a paradox that should unsettle every technically literate founder: the largest losses in crypto history are not caused by broken cryptography, failed audits, or consensus bugs. They are caused by moments of trust, urgency, habit, desire, fear, and authority. The protocol holds. The person breaks.
What we explored is not “how hacks happen,” but why sophisticated, rational, engineering-minded people lose generational wealth in systems that are mathematically secure. The answer is brutally simple: security thinking rarely extends beyond the protocol layer.
Crypto didn’t eliminate trust. It relocated it—onto the human holding the keys.
The Gap Between Secure Systems and Vulnerable Operators
Every case we examined followed the same structure. The cryptography was sound. The exploit occurred elsewhere.
A prominent investor loses $24 million because a telecom employee accepts a $500 bribe. A DeFi CEO signs an irreversible transaction because habit overrides scrutiny. A startup founder loses $50,000 because optimism and social pressure disable skepticism. A software engineer loses six Bitcoin because romance becomes leverage.
Different attacks. Same weakness.
The attack surface is not the chain. It is identity, attention, emotion, routine, and fear.
This is where engineering intuition often fails. Engineers expect adversaries to attack systems where entropy lives—in code, math, randomness. Instead, attackers go where predictability lives: human behavior.
Old Cons, New Interfaces
Nothing about these scams is novel.
They are Ponzi schemes, advance-fee frauds, honey traps, authority impersonation, and extortion—centuries-old psychological weapons. Crypto simply gives them three properties that make them devastating: speed, irreversibility, and pseudonymity.
A forged letter becomes a deepfake Zoom call. A bribe becomes a SIM swap. A blackmail envelope becomes a hotel room and a QR code. The medium changes. The playbook does not.
What has changed is the payoff structure. A single successful attack can move millions in minutes, across borders, beyond recovery. That incentive justifies patience, sophistication, and hybrid digital-physical operations.
The episode makes this explicit: modern crypto crime is layered. Social engineering enables technical exploitation. Technical compromise enables physical coercion. Digital footprints enable real-world targeting.
Once you see this, “cybersecurity” feels like a dangerously incomplete word.
The Engineering Failure Mode No One Likes to Admit
The most important insight of the episode is also the most uncomfortable for founders: personal security posture is a first-order business risk.
It does not matter how secure your protocol is if your keys can be coerced, copied, or socially engineered. It does not matter how many audits you pass if a single person can sign away irreversible value under pressure.
This is why the conversation keeps returning to habits. Clicking confirm without reading. Trusting urgency. Believing authority. Treating personal devices as safe by default. Fragmenting security across accounts and wallets instead of thinking systemically.
Engineers are trained to remove single points of failure from machines. Many still tolerate them in themselves.
From Cryptographic Resilience to Human-Aware Security
The episode doesn’t end in paranoia. It ends in design.
Security that works in this environment must assume humans are fallible under stress. That assumption changes everything. It leads to layered authentication that resists phishing, device separation that limits blast radius, multi-signature schemes that survive coercion, decoy strategies that reduce physical escalation, and operational habits that prioritize verification over speed.
More importantly, it reframes the goal. The goal is not perfect security. The goal is to become an economically unattractive target.
Criminals optimize for return on effort. Harden enough layers—technical, procedural, physical, reputational—and the model breaks. They move on.
That is engineering logic applied correctly.
The Unresolved Question
The episode closes on a question that deliberately remains unanswered: is individual hardening enough?
As long as single humans can be coerced into signing irreversible transactions tied to their physical safety, there is a systemic problem that personal discipline cannot fully solve. Multi-sig wallets help. Social norms help. But the incentive landscape remains.
The real battle may not be fought at the wallet level at all, but at the intersection of identity, custody, and social systems. Until then, the uncomfortable truth stands:
In crypto, the weakest link is not the protocol.It is the person who believes they are rational under pressure.
Modern leadership discourse is saturated with abstractions: vision, values, strategy, alignment. These words are cheap. They float easily above reality. What is scarce—vanishingly scarce in large organizations—is consequence.
This episode of Coordinated revolves around a single, brutal question: who actually pays when decisions go wrong? Not rhetorically. Not reputationally. Literally.
Nassim Nicholas Taleb popularized the phrase skin in the game, but the idea is far older than Taleb, older than capitalism, older than corporations. It is the civilizational insight that systems decay when decision-makers can externalize downside. When gains are private and losses are socialized, fragility is not an accident. It is the default outcome.
In complex, high-stakes domains—energy, finance, infrastructure, defense—this asymmetry becomes lethal. Failures are not theoretical. They cascade. They compound. They don’t politely wait for quarterly reports.
The central claim of this episode is simple and uncomfortable: leadership without personal exposure is not merely unethical; it is an engineering flaw .
Moral Hazard Is Not a Personality Problem
We like to explain systemic failure through individual bad actors. Greedy executives. Incompetent managers. Corrupt consultants. This is comforting and mostly wrong.
The real culprit is structure.
When executives collect upside through bonuses, stock options, or prestige, while the downside is absorbed by employees, customers, taxpayers, or “the market,” behavior predictably shifts. Risk migrates into the tails. Maintenance is deferred. Redundancy is cut. Catastrophic failure is postponed just long enough for the decision-maker to exit.
Economists call this moral hazard. Taleb calls it fragility. Engineers recognize it immediately: remove feedback and the system lies to you.
The absence of skin in the game is not a character flaw; it is a broken feedback loop. People do not learn. Organizations do not adapt. Errors accumulate invisibly until they rupture.
This is why so many post-mortems sound identical. The same mistakes, recycled under new branding. The same “unexpected” failures that were, in fact, inevitable.
Skin in the Game as a Truth Filter
One of the most important reframings in the conversation is this: skin in the game is not primarily about punishment. It is about epistemology.
When your livelihood, reputation, or capital is on the line, reality corrects you quickly. Delusion becomes expensive. Wishful thinking burns.
Taleb’s famous line captures it perfectly: “Don’t tell me what you think. Tell me what’s in your portfolio.”
In organizations, this translates cleanly. Trust the arguments of people who will personally live with the consequences. Discount those who won’t. The best signal of belief is exposure.
This is why consultants are structurally dangerous in mission-critical systems. They are paid upfront, insulated from long-term outcomes, and rarely present when consequences arrive. Their feedback loop is severed. They do not learn. The system pays the tuition.
Skin in the game restores learning by re-coupling belief and consequence.
Engineering, Not Ethics
The episode deliberately avoids framing this as a moral sermon. Ethics without enforcement are decoration.
Historically, civilizations understood this viscerally. Hammurabi’s Code was ruthless but effective: if a builder’s house collapsed and killed the owner, the builder paid with his life. If it killed the owner’s son, the builder’s son died. Horrifying, yes. But as a safety incentive, unmatched.
Modern societies rightly reject collective punishment and inherited guilt. Kant’s moral philosophy replaces outcome-based justice with duty and intent. But Kant’s framework assumes moral saints. Systems cannot.
Skin in the game is the pragmatic synthesis. It does not require virtue. It requires alignment. Even flawed humans behave responsibly when their own downside is real.
This is why skin in the game is best understood as systems design, not ethics. It is how you force honesty without trusting character.
Leadership Credibility Is Bought, Not Claimed
In infrastructure companies, trust is not built through vision decks. It is built through shared exposure.
A founder who has their capital locked into the company, who uses the product personally, who absorbs pain before asking others to sacrifice—this sends a costly signal. Costly signals are the only credible ones.
This is why symbolic gestures matter when they are real. When leaders cut their own compensation before cutting staff. When they remove executive luxuries during downturns. When they are subject to the same risks they impose on others.
The late Nintendo CEO Satoru Iwata halving his salary to avoid layoffs wasn’t charity. It was leadership legitimacy. The organization responded with loyalty, innovation, and endurance.
Leadership without visible vulnerability collapses under stress. People can smell asymmetry.
Decentralization Is Not a Preference. It Is a Requirement.
Skin in the game scales poorly under centralization. Distance dilutes consequence.
Complex systems—energy grids, logistics networks, software platforms—require decisions to be made close to where reality manifests. Local engineers, operators, and teams hold knowledge headquarters never will.
Hayek called this the knowledge problem. Taleb gives us the enforcement mechanism: empower the exposed.
Decentralized authority paired with local accountability produces faster adaptation and fewer catastrophic failures. Centralized command paired with insulated leadership produces paralysis and brittle systems.
History, from military disasters to grid collapses, confirms this relentlessly.
The Founder Advantage Is Time
Perhaps the most underappreciated dimension of skin in the game is time horizon.
Founders with deep exposure think in decades. Hired executives with short vesting cycles think in quarters. The difference is not subtle.
Research consistently shows that CEOs approaching equity vesting dates cut maintenance, inflate earnings, and pursue flashy acquisitions that destroy long-term value. They get paid. The system weakens.
Institutionalizing skin in the game—long vesting periods, mandatory shareholding, post-tenure exposure—is how organizations manufacture a synthetic founder mindset.
Without it, short-termism is not a risk. It is a certainty.
The Price of Credibility
This episode ultimately circles one unavoidable conclusion: leadership without consequence is fragile, and often fraudulent.
The price of credibility is not rhetorical skill or moral posturing. It is personal exposure. Time. Capital. Reputation. Visible vulnerability.
Skin in the game is the mechanism that forces alignment between words and reality. It turns leadership from a role into a risk-bearing function.
If you are not exposed to the downside, you are not truly in charge. You are managing optics.
And systems built on optics do not survive contact with reality.
This essay is based on the episode “Skin in the Game” from the podcast Coordinated with Fredrik, exploring leadership, infrastructure, and accountability through the lens of systems design and philosophy
There’s a quiet failure mode creeping into modern leadership: you look faster and smarter because AI outputs are clean and confident, but your actual judgment gets weaker—because you stop doing the hard work that builds judgment in the first place. In this episode of “Coordinated with Fredrik”, we unpack a framework we call The Vigilant Mind Playbook—not as “AI wellness,” but as competitive strategy: how to keep an asymmetric edge when everyone has the same models.
TL;DR
AI doesn’t just change productivity. It can change how your brain allocates effort—and how your organization converges into the same strategic blind spots as your competitors. The playbook is about building “cognitive sovereignty by design”: protecting human judgment, forcing friction at critical decision points, and preventing the “algorithmic hive mind” from turning your strategy into a commodity.
The core tension: optimization versus judgment
Right at the start, the episode frames the dilemma in a way every exec will recognize: in complex sectors (like energy), you live on ruthless optimization—yet the technology that boosts optimization can quietly erode the one asset you cannot replace: independent judgment.
A line that lands like a punch: we’re watching a shift where “optimization replaces wisdom and performance becomes a substitute for truth.”That’s not just philosophical posturing—it’s a warning about how leaders start making decisions when “polished output” becomes a proxy for understanding.
Cognitive debt: when convenience becomes a tax on your executive function
The episode introduces a concept it calls cognitive debt, described as something that shows up not only in behavior but in neurological measures—specifically citing an MIT experiment using EEG brain scans while participants tackled complex writing/strategy tasks.
The claim (as described in the episode) is blunt: the AI-assisted group showed weaker neural activity—less engagement in regions tied to attention, working memory, and executive function—while the non-AI group did the full “effort payment” themselves.
Then comes the part executives should actually fear: when AI was removed, participants struggled to recall their own arguments and access the deeper memory networks needed for independent thinking; their brains had adapted to outsourcing.
The episode translates that into an organizational risk: imagine analysts who rely on AI summaries for complex standards or technical domains—what happens when the model makes a subtle error, or the situation demands a contrarian insight the model can’t produce? You may no longer have the “neural infrastructure” left to spot the mistake.
The psychology: AI as a System 1 machine (and your addiction to certainty)
The playbook leans hard into behavioral science: Kahneman’s System 1 vs System 2 framing—fast/effortless intuition versus slow/deliberate reasoning—and labels AI as the “ultimate System 1 facilitator.” It gives instant answers and lets you short-circuit the productive struggle where real insight forms.
This is where the episode drops a Greene-style provocation: “The need for certainty is the greatest disease the mind faces.”In other words: the AI doesn’t just give you information—it gives you a hit of certainty, and certainty is the drug that kills skepticism.
The episode also references a Harvard Business Review study (as described in the conversation) where executives using generative AI for market forecasts became measurably over-optimistic—absorbing the machine’s confidence as their own—while a control group forced into debate and peer review produced more accurate judgments.
The “algorithmic hive mind”: when your whole industry converges into the same mistakes
The risk scales. The episode names it: the algorithmic hive mind—not just individual laziness, but organizational homogenization. If every company uses the same foundational models trained on the same data and optimized for the same metrics, strategic edge “evaporates.”
You get convergence, shared blind spots, and “optimized average performance”—and that’s exactly when you become fragile: the moment you need a truly different strategy, you realize your thinking has been homogenized by the tool.
The episode uses the 2010 flash crash as the illustrative analogy: algorithmic homogeneity + feedback loops + speed = tiny errors amplified into systemic chaos, only stopped when humans hit circuit breakers.The point isn’t finance trivia. It’s the structural warning: when everyone’s automation aligns, it can amplify errors faster than humans can react.
The executive move: institutionalize cognitive sovereignty (don’t “hope” for discipline)
The episode’s most practical shift comes late: stop treating this as personal productivity hygiene and treat it as governance.
It proposes moving AI oversight out of “IT” and into core strategy, potentially via an oversight body—a “cognitive sovereignty officer or counsel”—tasked with auditing AI use, assessing cognitive debt, and flagging over-reliance before it becomes a crisis.
Then it gets concrete: structural mandates like mandatory human approval for high-risk decisions (pricing changes over a threshold, AI-suggested firings reviewed by HR/legal), described as “circuit breakers” that prevent automated mistakes from spiraling.
And finally: stress test your AI like banks stress test financial models—against scenarios it hasn’t seen—so you confront limitations while still using the tool aggressively.
Culture: reward the dissenter, or your org walks off a cliff politely
One of the sharper cultural notes: people who question AI outputs can face a competence penalty—seen as “not trusting the tech.” Leadership has to shatter that dynamic and explicitly reward the person who challenges the machine.
The episode also highlights a trust problem: “a third of employees actively hide their use of AI,” driven by stigma and fear of looking replaceable—creating a strategic weakness because best practices and flaw-spotting don’t circulate.
In a Greene lens: secrecy is not “edgy.” It’s organizational self-sabotage when it prevents shared learning and accountability.
The closing provocation: competence becomes cheap; wisdom becomes the only edge
The episode ends with the thesis you probably want tattooed on your operating system:
Most competitors will become faster, louder, and more confident with AI—but few will become wiser. When models are ubiquitous, competence becomes a commodity; the only non-replicable asset left is wisdom and contrarian judgment.
And that’s the episode in one sentence: AI can optimize—but it can’t replace wisdom, because wisdom is governance over your own mind.
From the publisher's feed