The Problem

I have cable and Starlink. Cable is OK-ish but occasionally goes down. Starlink is my backup. I wanted automatic failover without buying expensive hardware or running complex software.

The Solution

A simple bash script that:

• Checks if primary connection is healthy every 3 seconds
• Switches to backup after 3 consecutive failures
• Switches back when primary is stable again
• Prevents flapping between connections

Setup (5 minutes)

1. Find your network interfaces

ip link show  # Find your interface names

2. Create the failover script

Save this to /usr/local/bin/netfailover.sh:

#!/usr/bin/env bash
set -euo pipefail

# Configuration - CHANGE THESE!
PRIMARY_IF="eth0"           # Your primary ISP interface
BACKUP_IF="wlan0"          # Your backup ISP interface
PRIMARY_NAME="Primary"      # Display name
BACKUP_NAME="Backup"       # Display name

# Tuning
OK_THRESHOLD=3             # Checks before switching back
FAIL_THRESHOLD=3           # Failures before switching
SLEEP_SECS=3              # Check interval

require_root(){ [[ $EUID -eq 0 ]] || { echo "Run with sudo"; exit 1; }; }
log(){ logger -t netfailover "$1"; echo "[$(date '+%Y-%m-%d %H:%M:%S')] $1"; }
gw(){ nmcli -g IP4.GATEWAY device show "$1" 2>/dev/null || true; }
setdef(){
  local ifc=$1 gw=$2
  [[ -n "$gw" ]] && ip route replace default via "$gw" dev "$ifc" && return 0
  return 1
}

healthy(){
  local ok=0
  # Test multiple endpoints to avoid false positives
  for dst in 1.1.1.1 8.8.8.8 9.9.9.9; do
    ping -I "$PRIMARY_IF" -c 1 -W 1 "$dst" >/dev/null 2>&1 && ok=$((ok+1))
  done
  [[ $ok -ge 2 ]]  # Need 2/3 responding
}

# Main loop
require_root
cur_primary=1; fail=0; ok=0

log "Starting failover monitor ($PRIMARY_NAME ↔ $BACKUP_NAME)"

while true; do
  PGW=$(gw "$PRIMARY_IF")
  BGW=$(gw "$BACKUP_IF")

  if healthy; then
    ok=$((ok+1)); fail=0
    if (( cur_primary==0 && ok>=OK_THRESHOLD )); then
      log "✓ $PRIMARY_NAME healthy → switching back"
      setdef "$PRIMARY_IF" "$PGW" && cur_primary=1
      ok=0
    fi
  else
    fail=$((fail+1)); ok=0
    if (( cur_primary==1 && fail>=FAIL_THRESHOLD )); then
      log "✗ $PRIMARY_NAME failed → switching to $BACKUP_NAME"
      setdef "$BACKUP_IF" "$BGW" && cur_primary=0
      fail=0
    fi
  fi

  sleep "$SLEEP_SECS"
done

3. Create the systemd service

Save this to /etc/systemd/system/netfailover.service:

[Unit]
Description=Network Failover Service
After=network-online.target NetworkManager-wait-online.service
Wants=network-online.target NetworkManager-wait-online.service

[Service]
Type=simple
ExecStartPre=/bin/sleep 8
ExecStart=/usr/local/bin/netfailover.sh
Restart=always
RestartSec=2
StandardOutput=journal
StandardError=journal

[Install]
WantedBy=multi-user.target

4. Enable and start

sudo chmod +x /usr/local/bin/netfailover.sh
sudo systemctl daemon-reload
sudo systemctl enable netfailover.service
sudo systemctl start netfailover.service

5. Check it’s working

# Watch the logs
sudo journalctl -u netfailover -f

# Test failover (unplug primary cable or disable interface)
sudo ip link set eth0 down  # Wait ~10 seconds
sudo ip link set eth0 up    # Should switch back after ~10 seconds

How It Works

1. Health checks: Pings 3 public DNS servers through the primary interface
2. Smart thresholds: Requires 3 consecutive failures before switching (prevents false positives)
3. Stable switching: Waits for 3 successful checks before switching back (prevents flapping)
4. Route manipulation: Uses Linux’s default route to control which ISP handles traffic

Why This Approach?

• No dependencies: Just bash, ping, and ip route
• Simple: ~50 lines of code you can understand and modify
• Battle-tested: Based on traditional network monitoring patterns
• Fast: Detects failures in ~9 seconds, recovers in ~9 seconds

Gotchas

• Both connections need to be up and have DHCP leases
• Existing connections may drop during switchover
• DNS might need a flush after switching: systemd-resolve --flush-caches

Monitoring

Check which connection is active:

ip route | grep default

View failover logs:

sudo journalctl -u netfailover --since "1 hour ago"

That’s it. No BGP, no VRRP, no expensive hardware. Just a simple script that keeps me online.

Tested on Ubuntu 22.04/24.04 with cable + starlink, and dual WAN setups. Should work on any Linux with NetworkManager and systemd.

But here’s what changes when you step into leadership: your losses become public property. When you’re an individual contributor, you can fail quietly, learn privately, move on. That bug in your code? Fix it before anyone notices. That presentation that bombed? Iterate for next time. Your failures are yours to manage.

When you’re leading transformation in teams, the physics change entirely. Your failures are watched and dissected, with or without you knowing exactly what is being discussed. They become water cooler conversations and organizational folklore. This isn’t about celebrating failure - that confuses activity with progress. This is about recognizing that losses are inevitable, and how you handle them becomes organizational DNA.

I learned this the hard way with many (many) failed projects and ideas. I make it a point to be public about these failures, laying out to the team where my thinking went wrong, showing the flawed assumptions, owning the disruption it caused.

The response? Team members talk about the trust this approach built.

That’s the paradox. Leaders who can’t admit obvious failures think they’re protecting their authority. They’re actually destroying trust. Everyone can see when something isn’t working. Pretending otherwise doesn’t make you look strong; it makes you look delusional or dishonest. Sometimes both.

There’s this pressure to be “too much” of everything as a leader - too confident, too certain, too polished. But the leaders who own failures publicly are criticized for being “too vulnerable,” “too open.” Here’s the thing: that vulnerability, when paired with actual wins, creates something powerful - proof that falling down isn’t fatal.

The most infuriating leaders aren’t the ones who fail. They’re the ones who fail and then gaslight everyone about it. Who pretend the strategy that clearly didn’t work was actually successful “from a certain point of view.” Who make their teams question reality rather than question their decision.

Kind Versus Nice in Victory and Defeat

This difference between protecting ego and protecting trust brings us to a critical distinction that shapes how we handle both victories and defeats.

Nice leaders celebrate wins loudly and bury losses quietly. They smooth over mistakes, avoid uncomfortable conversations, keep everyone feeling good about themselves. They’re the ones who say “great job everyone” when half the team knows it wasn’t. When failures surface, they blame the team that executed their flawed strategy, the market that didn’t respond to their mistimed launch, anyone but themselves.

Kind leaders do something harder. They celebrate wins generously - giving credit widely and specifically. But they own losses personally and publicly. They say “I made this call, here’s where my thinking was flawed, here’s what we’re learning from it.” When you have power, this admission isn’t weakness - it’s redefining strength. You’re dismantling the myth of infallible leadership, the toxic idea that authority means never being wrong.

This is where privilege enters the equation in ways we don’t talk about enough. Who can afford to take public ownership of failure? Usually those with enough wins banked, enough social capital, enough alternatives if things go sideways. The senior director with a track record can admit failure more safely than the new manager still proving themselves.

This creates an obligation. If you have the safety net to fail publicly, you must model how to fall and get back up. Not for your own growth - for everyone watching who can’t afford to take the same risks.

The arithmetic is actually simple. Your wins create permission to show your losses. Your losses create permission for others to take risks that lead to wins. But if you only show wins, you create a culture where people hide losses until they become catastrophes.

Real kindness in leadership means making people uncomfortable with truth rather than comfortable with fiction. It means telling your team their idea has fatal flaws rather than letting them waste six months on it. It means challenging the senior executive dismissing junior voices, even when that executive writes your performance review. It means using whatever privilege you have to amplify those who can’t speak as safely as you can.

Building Organizations That Can Win Because They Know How to Lose

These individual acts of courage and accountability compound into something larger - they become the foundation of organizational resilience.

The strongest organizations aren’t built by people who never fail. They’re built by people who fail instructively and create cultures that can metabolize failure into fuel. Not the fake “fail fast” culture where people celebrate any failure as learning. That’s just incompetence with better PR. I’m talking about teams that reflexively ask “what did we learn?” because they’ve watched leaders model that question about their own mistakes.

Here’s what I’ve observed: wins create momentum, but how you handle losses creates culture.

Every time you stand up and own a failure, you’re doing several things simultaneously:

• You’re making it safer for someone else to take the risks that lead to wins
• You’re demonstrating that recovery is possible
• You’re showing that learning matters more than looking good
• You’re building a team that can handle reality rather than requiring fantasy

The ratio matters. You need enough wins to have credibility. Nobody wants to follow someone who fails constantly and owns it beautifully - that’s just transparent incompetence. But without visible losses and recovery, you’re not building an organization that can innovate. You’re building a performance theater where everyone pretends nothing ever goes wrong.

Your real community - in leadership and in life - isn’t the people who only see your wins. It’s the ones who’ve watched you fail spectacularly and stick around to ask, “What did we learn?” instead of “I told you so.” The best ones do it with humor, making the medicine go down easier. They’re the ones who, when you’re about to make the same mistake again, remind you of last time and save you from yourself.

These are the people who make organizations antifragile. They’ve seen losses handled with grace and learning, so they’re willing to take bigger swings. They know that failure isn’t career-ending if you own it and learn from it.

Organizations that only know how to win are brittle. When they eventually lose (and they will), they shatter. They look for someone to blame, someone to fire, someone to sacrifice to maintain the illusion of constant success.

Organizations that know how to lose - because they’ve watched leaders do it with accountability and grace - can take bigger risks, fail harder, recover faster, and ultimately win bigger. They don’t waste energy on coverups or blame games. They put that energy into learning and adjusting.

The hardest truth? The most successful leaders I know and respect aren’t those who never failed. They’re the ones who failed instructively, publicly, and then used their recovery to light the path for others. They have impressive win records, but what distinguishes them is how they turned their losses into organizational assets.

Remember:

• Your wins give you permission to show your losses
• Your losses give others permission to take risks
• Public accountability for failure is as, if not more, powerful than any success story
• Choose kind over nice, especially when owning mistakes
• Your privilege to fail safely creates an obligation to fail instructively
• The ratio matters - you need wins, but losses teach culture

Make a decision. Own the results. Build something that can win because it knows how to lose.

Because in the end, organizations aren’t built on the fairy tale of constant success. They’re built on the human reality of falling down, getting up, and being honest about both.

The Weird Stuff That Actually Happens

1. Your Muscles Will Betray You, But You Can Sing Your Lungs Out

Here’s something that completely caught me off guard: After a 3+ hour zone 2 run, I’m not out of breath at all but my muscles are screaming. This feels completely backwards from my normal running experience where I’m usually exhausted both muscle-wise AND gasping for air.

There’s a fascinating physiological reason for this. Zone 2 training keeps your blood lactate levels stable - your body clears lactate as fast as you produce it. You’re working your muscles for hours while your cardiovascular system cruises along, using fat as fuel instead of burning through carbs. Your muscles do serious work accumulating miles, but your heart and lungs are on a leisurely jog.

Normally when you run hard, everything fails together in one spectacular bonfire of exhaustion. With zone 2, your muscles do a slow burn while your cardiovascular system barely breaks a sweat.

2. Why Can’t I Fall Asleep?!

I’ve had a lifetime of great sleep - head-hits-pillow, wake-up-9-hours-later kind of sleep. Then I started these long zone 2 runs and suddenly I’m lying in bed at 2 AM wondering what happened to my superpower.

A key moment came as I browsed The Feed (nutrition shop for athletes) and noticed product lines dedicated to sleep-related nutrition. Why would athletes need help sleeping? Aren’t we supposed to be exhausted?

Marathon-level training can seriously deplete magnesium levels - up to 12% of your daily magnesium lost through sweat alone. Magnesium helps regulate cortisol and promotes deep sleep. Without it, you get the cruel irony of being physically exhausted but neurologically wired.

I’ve started supplementing with magnesium (glycinate, citrate) before bed. Who knew that running for hours could make you too tired to sleep?

3. Just Ran 3 Hours, You Must Be Not Hungry?!

Remember being a kid and your mom saying “you must be hungry after all that running around”? Turns out mom was wrong.

I noticed this during marathons in my younger days, but it’s happening again with long zone 2 runs: I finish a 3+ hour run having burned 1,000+ calories, and food is the last thing on my mind. My stomach feels like it’s hibernating.

As usual, the answer is science - intense or prolonged exercise actually suppresses your “hunger hormone” (ghrelin) and increases appetite-suppressing hormones like peptide YY. Your body essentially shuts down digestion to prioritize blood flow to working muscles, and this effect lingers after you stop running. Evolution probably designed this so our ancestors could hunt for hours without being distracted by hunger, but it means I have to force myself to eat recovery food when every instinct is saying “nah, I’m good.”

The Parts Nobody Mentions

Here are two notes on Zone 2 training which I will mention:

Walking. So. Much. Walking.

Want to feel like a fraud while “running”? Try zone 2 training on trails. Any slight incline and my heart rate monitor starts screaming at me to slow down. So I walk. And pause. And walk some more.

I’ve had to completely recalibrate my ego about what “going for a run” means. Sometimes my Strava looks like I’ve been out for a leisurely hike rather than a training run. But here’s the thing - this is exactly what you’re supposed to do. If you can’t maintain zone 2 while running up that hill, you walk. Period. Your ego will recover faster than your aerobic system will if you keep spiking into zone 3.

You NEED a Real Heart Rate Monitor

Let me save you some frustration: your fitness watch is lying to you about your heart rate, especially during zone 2 training where precision matters.

I use a Polar Verity Sense armband (because I hate chest straps with the fire of a thousand suns), and the difference is shocking. Wrist-based monitors lag, they get confused by arm movement, and they’ll have you thinking you’re in zone 2 when you’re actually cruising in zone 3.

When you’re trying to stay in such a narrow heart rate range for hours at a time, accuracy and responsiveness matter. Bite the bullet and get a proper monitor - armband or chest strap. Your Zone 2 training will thank you.

Bottom Line

Zone 2 training is simultaneously the most boring and most surprising type of running I’ve done. It’s exposed gaps in my fitness (strong heart, apparently weak muscles), created problems I didn’t know existed (who needs help sleeping after running for 3 hours?), and forced me to walk up hills like… like I’m old (I am old).

But here’s the thing - it’s working. My easy pace is getting faster while staying at the same heart rate. I can run for hours without feeling destroyed the next day. Despite all the sleep issues (which I will figure out).

Just don’t expect it to feel like “normal” running. Throw out your conceptions that running is hard. It’s its own weird, slow, surprisingly complex beast. Just prepare to do a lot of walking. Your ego might hate it, but your mitochondria will thank you.

Helpful Resources:

• Phil Maffetone’s MAF Method - The OG of zone 2 training
• Uphill Athlete’s Aerobic Capacity Guide - Great for understanding your zones
• Examine.com’s Magnesium Guide - Everything you need to know about magnesium supplementation
• The Science of Ultra Podcast - Deep dives into endurance physiology

This isn’t a “AI will change everything” post. It’s a distillation of what works for me right now.

Why This Stack Works

A key reason why my blogging stack works is pairing Claude Code with Jekyll and GitHub. Jekyll’s file-based architecture means everything is version-controlled, editable, and transparent. Claude Code can read your existing posts to understand your voice and examine your site structure to suggest improvements. It’s like having a writing partner who also understands git, markdown, and web development.

Want to analyze your content for patterns? It can read through your entire _posts directory. Planning a series of related posts? It can maintain continuity by referencing your existing content.

GitHub integration also allows me to set up workflows where mentioning @claude in issues automatically generates content updates, fixes, or even entire blog posts via pull requests.

The real power emerges when you move past basic “write me a blog post” prompts to sophisticated, multi-layered workflows.

Custom Command Templates: You can create reusable templates in .claude/commands/ that become slash commands. My /blog-post command automatically generates Jekyll blank blog post with proper formatting, suggests relevant tags based on my existing posts, and even includes a basic structure tailored to my writing style. It’s a personal blog post scaffold that learns from my patterns.

Multi-Agent Workflows: Instead of asking Claude to do everything at once, you can deploy specialized subagents. I use one agent focused purely on research and fact-checking, another for initial drafting that understands my voice and technical level, and a third for editing that knows my common weak spots. These agents can work in parallel, dramatically speeding up complex posts.

Session Management Strategy: Use /init, /compact, and /clear strategically. Starting each writing session with /init establishes my blog’s style guide, recent post themes, and current projects. This context persistence means Claude doesn’t just help with individual posts - it understands your blog’s evolution over time.

MCP Integration

This is where things get genuinely transformative. The Model Context Protocol (MCP) ecosystem, particularly tools like Perplexity MCP, turns Claude Code from a writing assistant into a research powerhouse.

With Perplexity MCP installed, I can perform real-time web searches without leaving Claude Code (To be fair, Claude Code can do websearches by itself now). Working on a post about Ethereum staking? I can search for the latest validator metrics, recent protocol updates, or community discussions - all while maintaining the context of my draft. The research becomes integrated rather than scattered across browser tabs and note-taking apps.

But it goes deeper than individual searches. MCP tools can maintain ongoing research threads, automatically fact-check claims against current data, and even suggest related topics based on trending discussions. Your blog posts become more timely, accurate, and comprehensive without the traditional research overhead.

The context-aware aspect is crucial - these aren’t just isolated web searches. Claude Code can correlate new research with your existing posts, identify gaps in your coverage, and suggest natural follow-up topics. Your blog evolves from a collection of individual posts into a coherent knowledge graph.

Beyond Perplexity MCP, other MCP tools are worth exploring:

• Obsidian MCP monitors your vault and indexes metadata into SQLite - perfect for maintaining a searchable research archive. The File System MCP provides enhanced local file operations beyond basic Claude Code capabilities.
• Memory Bank MCP allows Claude Code to maintain awareness of themes and discussions across multiple sessions. No more re-explaining your blog’s focus every time you start writing.
• The official Notion MCP offers full workspace access with OAuth, making it ideal for content calendars and editorial planning. GitHub MCP can automate issue creation for blog ideas and manage content workflows.

My Actual Workflow

Here’s how my typical blog post comes together, step by step:

Step 1: Context Initialization - Every writing session starts with /init, which loads my blog style guide, recent post themes, and any ongoing series. This isn’t just about consistency - it’s about Claude understanding where this post fits in my broader narrative.

Step 2: Research Phase - Using MCP tools, I gather current information, fact-check assumptions, and explore related topics. The key insight: this research happens within the same context where I’m writing, so connections and insights emerge naturally.

Step 3: Multi-Agent Content Creation - My research agent compiles findings and suggests angles. My draft agent takes these insights and creates the initial structure and content, maintaining my voice and technical level. My editing agent reviews for clarity, flow, and consistency with my existing posts.

Step 4: Jekyll Integration - Claude Code handles the technical details - proper front matter formatting, tag suggestions based on content analysis, and even image optimization if needed. It can run prettier, create changelist descriptions, and other geeky commands.

The entire process feels collaborative rather than automated. I’m not just delegating writing to AI - I’m orchestrating a content creation process where AI handles routine tasks while I focus on strategy, voice, and unique insights.

Some tips I learnt along the way:

• Instead of long lists of dos and don’ts, I structure prompts as step-by-step algorithms with decision points. “First, analyze the topic’s technical complexity. If high, include a basics section. Then, check my recent posts for related content and reference appropriately.” This approach produces more reliable results than vague style guidelines.

• I either write a first draft and ask Claude Code to flesh it out more, or I ask Claude Code to do research and write the first draft (remember to use Planning mode!). In any case, I iterate in a separate Vim instance. I’ve learned to expect 3-5 refinement cycles per post, and that’s actually a feature, not a bug. Each iteration can focus on a different aspect - first structure and flow, then technical accuracy, then voice and style. The key is being direct about requirements and expressing urgency clearly when something needs immediate attention.

• Managing session context is an art. Too little context and Claude loses track of your blog’s voice and themes. Too much and responses become slow and unfocused. The sweet spot is maintaining awareness of 5-10 recent posts and your core style guide while using /compact to summarize longer research sessions.

What’s overhyped? The idea that AI can completely replace your editorial judgment. Claude Code excels at research, drafting, and technical formatting, but the strategic decisions about what to write, how to position arguments, and when to publish still require human insight.

May your writing be smooth and impactful.

1. Stablecoins have proven that public blockchain rails can handle trillions in transaction volume
2. U.S. regulators are shifting from skepticism to strategic engagement with this technology
3. Major financial institutions are tokenizing real-world assets, with projections reaching $16 trillion by 2030
4. Institutional capital is flowing in through ETFs and corporate treasury allocations
5. Ethereum’s economic model directly links network usage to the value of ETH through staking yields and fee burns
6. Open, permissionless networks have structural advantages over closed systems for global financial infrastructure

The current financial system runs on technology designed in the 1970s. These rails are slow, expensive, and poorly suited for a digital, 24/7 global economy. Public blockchains offer a potential upgrade path - though this transition faces real challenges and isn’t guaranteed.

Stablecoins: The Proof of Concept

Stablecoins have become the first genuine product-market fit for public blockchains at scale. The market has grown to approximately $280 billion¹, processing trillions in annual transaction volume. USDT leads with $167 billion in circulation, while USDC holds $67 billion².

In recent months, USDC alone processed $2.3 trillion in on-chain transfers while USDT handled $1.2 trillion³. These volumes rival traditional payment networks - not because of speculation, but because stablecoins solve real problems. They enable instant cross-border payments, provide dollar access in countries with unstable currencies, and serve as the foundation for DeFi protocols.

Major lending protocols like Aave, which currently manages over $30 billion in deposits⁴, were built on stablecoin infrastructure. This isn’t just crypto trading anymore - it’s functional financial infrastructure that works 24/7 globally.

The success of stablecoins forced regulators to pay attention. What started as a tool for crypto traders has evolved into a global payment rail that policymakers can no longer ignore.

The Regulatory Landscape

A significant shift is underway in how U.S. regulators view blockchain technology. Federal Reserve Governor Christopher Waller captured this change in his August 2025 speech at the Wyoming Blockchain Symposium: “There is nothing scary about this just because it occurs in the decentralized finance or DeFi world - this is simply new technology to transfer objects and record transactions.”⁵

The passage of the GENIUS Act in July 2025 marked the first major U.S. cryptocurrency legislation⁶. This law creates a federal framework for stablecoin issuers, requiring full reserve backing and regular audits. It gives traditional banks, fintech companies, and other institutions a clear path to issue regulated digital dollars.

This isn’t just financial policy - it’s geopolitical strategy. U.S. policymakers increasingly view dollar-denominated stablecoins as a way to maintain and extend the dollar’s global reserve status. As Governor Waller noted, stablecoins have “the potential to maintain and extend the role of the dollar internationally.”⁵

The regulatory clarity provided by the GENIUS Act removes the primary barrier that kept institutions on the sidelines. Combined with the Fed’s more supportive stance, this creates conditions for broader adoption.

Real-World Asset Tokenization

If stablecoins proved the concept, tokenized real-world assets (RWAs) represent the next wave. Financial institutions are actively moving traditional assets onto public blockchains, with Ethereum emerging as the primary platform.

BlackRock’s BUIDL fund, a tokenized money market fund on Ethereum, has grown to over $500 million since launching in March 2024⁷. Franklin Templeton’s FOBXX fund manages approximately $400-780 million across multiple blockchains⁸. Other examples include:

• Ondo Finance’s tokenized Treasury products (OUSG, USDY) with over $248 million on Solana alone⁹
• J.P. Morgan’s tokenized asset-backed securities
• Multiple corporate debt and private credit tokenization initiatives

The total market for tokenized RWAs (excluding stablecoins) has reached approximately $26-27 billion¹⁰. Boston Consulting Group projects this could grow to $16.1 trillion by 2030 - roughly 10% of global GDP¹¹. Even their conservative estimate represents a 50x increase from today’s levels.

The economics driving this shift are straightforward. Tokenization enables 24/7 settlement instead of T+2, reduces operational costs, allows fractional ownership of previously illiquid assets, and creates a transparent, immutable record of ownership. For a large bank, these efficiencies could save hundreds of millions annually.

By choosing Ethereum for products like BUIDL, institutions are making a bet on which infrastructure will matter. Each deployment strengthens Ethereum’s network effects and makes it more likely to become the default settlement layer.

Valuing a Global Settlement Layer

If Ethereum becomes critical financial infrastructure, traditional valuation models become inadequate. The question becomes: what is a global, programmable settlement layer worth?

For context, the combined market capitalization of NYSE and Nasdaq exceeds $53 trillion. SWIFT facilitates over $5 trillion in daily transaction value¹². Ethereum, which combines functions of an asset ledger, settlement network, and messaging layer, currently has a market cap of approximately $450 billion.

The more relevant metric might be Total Value Secured (TVS) - the sum of all assets trusting the chain’s security. Ethereum’s DeFi ecosystem alone holds approximately $90-95 billion in total value locked, representing about 60% of all DeFi activity¹³. As tokenized RWAs grow into the trillions, the network securing them must be valuable enough to deter attacks.

Ethereum’s economic design creates direct links between usage and value. The Proof-of-Stake mechanism allows ETH holders to earn yields (currently around 3%) by staking. EIP-1559 burns a portion of every transaction fee, creating deflationary pressure as usage increases. These mechanisms mean increased network activity translates directly into value accrual for ETH holders.

Why Open Networks Have Structural Advantages

For global financial infrastructure, neutrality matters more than control. Private blockchains face an inherent trust problem - would Goldman Sachs build critical infrastructure on a J.P. Morgan-controlled network? Would any country trust another’s centralized system?

Public blockchains solve this through credible neutrality. The rules are transparent, enforced by code, and can’t be arbitrarily changed. This creates a level playing field that encourages long-term investment and development.

The real advantage is composability. Assets on Ethereum can be combined and recombined permissionlessly, like open-source code. This enables exponential innovation that closed systems can’t match. While private networks innovate linearly and top-down, Ethereum evolves exponentially and bottom-up.

Institutional Capital Flows

The theoretical case is being validated by capital flows. Prominent investors including Peter Thiel’s Founders Fund are making what the WSJ describes as a “broad play on Ethereum,” taking stakes in companies that accumulate ETH on their balance sheets¹⁴.

Corporate treasuries have purchased 1.26 million ETH in recent months - 1% of circulating supply - with Standard Chartered projecting they could eventually hold 10%¹⁵. These firms are following the MicroStrategy playbook, using equity markets to accumulate crypto assets as primary reserves.

U.S. spot Ethereum ETFs have attracted over $9 billion since launching¹⁶. Unlike previous crypto cycles, this represents long-term strategic allocation rather than speculation.

These flows are creating supply dynamics worth watching. Between ETF purchases, corporate accumulation, and staking (which locks up ETH), an increasing percentage of supply is becoming illiquid. When this meets growing demand from RWA settlement, basic economics suggests significant price appreciation.

Risks and Challenges

This thesis faces real risks that could derail or delay it:

Competition: Other blockchains like Solana are growing rapidly. While Ethereum dominates with 60% of DeFi activity, this could change. Network effects are powerful but not insurmountable.

Technical limitations: Ethereum still faces scalability challenges. While Layer 2 solutions help, the base layer processes only 15-30 transactions per second. Major institutional adoption will require continued technical improvements.

Regulatory reversal: While current momentum is positive, political changes could shift regulatory stance. The framework remains incomplete, particularly around DeFi protocols and cross-border transactions.

Security concerns: Smart contract bugs and hacks remain common. A major security failure could damage institutional confidence. The technology is still maturing.

Macro factors: Rising interest rates or a broader market downturn could reduce appetite for digital assets. Correlation with traditional markets has increased.

Adoption friction: Despite improvements, blockchain technology remains complex for average users. Institutional adoption doesn’t guarantee retail follow-through.

Conclusion

The convergence of proven stablecoin utility, regulatory clarity, institutional adoption, and technical maturation suggests Ethereum could become foundational financial infrastructure. This isn’t certain - technology transitions are messy and incumbents don’t give up easily.

But the direction seems clear. Major financial institutions are building on Ethereum. Regulators are creating frameworks rather than barriers. The technology, while imperfect, works well enough for trillion-dollar transaction volumes.

If this thesis plays out, we’re watching the early stages of a fundamental rewiring of global finance. The pipes are being laid now, even if the full transition takes decades. Ethereum’s position as the primary settlement layer for this new system would make it extraordinarily valuable - though predicting exact valuations or timelines would be speculation.

The question isn’t whether blockchain technology will impact finance - that’s already happening. The question is which infrastructure wins and how completely the transition occurs. Ethereum has the lead, but the race is far from over.

Maybe. But here’s what actually limited my career: spending years saying yes to everything that looked like “career growth” while my actual work - the creative stuff that energized me - and family time happened in stolen moments late at night (or even late night weekends!)

Then I realized that I was living someone else’s definition of success. The “visibility projects”, the various committees I joined, the OKRs planning meetings that went nowhere. Meanwhile, I was exhausted and clearly not thriving, even burning out on multiple occasions as I’ve shared in previous posts.

I now have three simple rules:

1. If it consistently drains me, I stop
2. If I’m doing it to impress someone, I question it
3. If it doesn’t get calendar time, it doesn’t exist

That last one might be interesting. Values without calendar blocks are just motivational poster material. Now my “focus” blocks are as real and important as meetings to execute on projects. My Friday afternoon mentoring sessions? Non-negotiable.

Aligning with your values isn’t just about finding yourself - it’s about being disciplined enough to follow through. This is why scheduling yourself matters. When you treat your real priorities like actual appointments, something shifts. The gap between who you want to be and who you are starts closing.

Try this for yourself: Block one hour for something you claim matters but never “have time” for. Guard it like a critical meeting with your VP. Because it is.

Now if you’ll excuse me, it’s dinner time with the family…

Growing up in Asia, I was culturally nudged to blend in, wait for permission, and never appear too pushy. Yet every breakthrough I’ve witnessed came from someone willing to risk being called “weird” or “self-centered.” Thankfully I was always never good at listening. :-)

The fear of judgment keeps us playing small. We soften our messages, downplay our achievements, and wait for the perfect moment that never comes. Meanwhile, those who succeed aren’t waiting - they’re being authentically themselves, even when it makes others uncomfortable.

Real impact means advocating boldly for yourself and your team. It means asking the “obvious” question everyone else is too nervous to voice. It means choosing messy action over polished inaction, because perfection is indeed the enemy of the good or the inaction.

Yes, setting firm boundaries will make some people call you difficult. Being driven will get you labeled as pushy or unreasonable. But here’s what I’ve learned: The same people who judge you today will praise your vision once you succeed. Stay humble through it all.

Our biggest regrets won’t be the risks we took - they’ll be the moments we chose comfort over courage. The times we had something valuable to contribute but stayed quiet. The opportunities we let pass while we were still “preparing.”

Your unique perspective isn’t something to hide. It’s the very thing that will set you apart.

So remember:

• Be authentic, even if people find you odd - embrace the odd
• Prioritize action over perfection
• Advocate boldly for yourself and your team
• Be driven, curious, and firm
• Learn to be persuasive (even if you don’t know how yet - it’s the most impactful skill you’ll ever develop)
• Be the person to lead the change

Picture this: you’re a Microsoft Distinguished Engineer (L70) pulling in $2.7M a year. You’ve hit the IC summit. You dutifully max every tax shelter, funnel the rest into index funds, and - just as Deedy Das’ comp slide predicts - retire 30 years later with $13M.

This is supposed to be the pinnacle of the “known” path to wealth. The safe, guaranteed route that every FAANG engineer aspires to.

Now I’m not so sure about this path. I believe FAANG Engineers and other high-wage earners can do better.

The Bogleheads Gospel at Work

Having spent many years in FAANG, I watched the same financial planning playbook repeat across internal forums and water cooler chat: max your 401(k), dump everything else into broad index funds, mega backdoor Roth, max out the HSA. The messaging was consistent - save 30% of your high six-figure or seven-figure income and you’ll hit $10M eventually. It’s the safe, responsible path.

This conventional wisdom dominated my work circles. When RSUs hit like clockwork every month or quarter, the advice was always the same: diversify immediately into VTSAX. Anyone suggesting individual stocks or angel investing was met with links to that one study about how 90% of day traders lose money.

But here’s what bothered me: we were all brilliant engineers solving complex problems at work, yet we’d outsource our entire financial future to Vanguard and follow the Bogleheads philosophy religiously. The mindset became “take your bets at work, don’t risk the golden goose.”

Two Views, One Message

Before we dive into numbers, notice the hidden premise both camps share: it’s not how much you earn, it’s what you own. One path treats salary as an endgame; the other treats it as rocket fuel. The difference sounds philosophical, but the outcomes can be material.

W-2 income - even seven figures - has a ceiling. Equity ownership breaks through it.

Rough equivalents to Microsoft L70 (“Distinguished Engineer”)

Translation for the ladder-climbers: Deedy’s $13M projection assumes you’ll scale a summit 99%+ of engineers will never reach - and even if you do, the view isn’t quite as panoramic as you’d hoped. See levels.fyi

(Amazon’s IC ladder caps at L10, though some orgs use L11 “Principal DE”; Apple’s ICT7 sometimes overlaps principal-level work.)

Why $2.7M/Year Still Isn’t Enough

W2 Tax Drag: Even in a bull market, the government is your biggest “co-founder.” Federal, FICA, and California state taxes shave off ~50¢ of every dollar before you ever hit Buy. And if California’s proposed 14.63% top bracket passes? Sharpen the blade.

Time-for-Money Trap: Your comp pauses when you take a sabbatical. Your roommate’s SaaS revenue or equity in a company doesn’t. The higher your salary, the scarier it feels to unplug - so you rarely do. I watched peers who could easily chubbyFIRE or leanFIRE stay chained to their desks because they couldn’t quite hit fatFIRE on index funds alone.

The Diversification Paradox: Your FAANG colleagues preach “don’t concentrate,” yet the richest people did exactly that - then diversified. Think Bezos keeping 90% Amazon until the yacht was paid for.

Bottom line: A supersized paycheck is defensive wealth. Ownership is offensive wealth. You need both, but only one can win a championship.

The Selection Bias Problem

There’s probably selection bias at play here - the types who join and stay at FAANG already chose the “safe” path. We’re the ones who picked the stable job over the startup, the guaranteed comp over equity lottery tickets. Plus, when you’re working 60+ hours chasing that next promo, there’s barely mental energy left to research asymmetric bets.

But that’s exactly the trap. We optimize for the wrong thing - maximizing W-2 income instead of maximizing ownership potential.

Two Kinds of “Rich”

We toss “rich” around like it’s binary, but lived experience says otherwise.

The Comfortably Rich ($1-10M)

• Dual-income professionals, 20+ years in tech
• 70%+ in index funds
• Nice house, Premium Economy flights
• Still fret over college tuition & healthcare

The Transformational Rich ($10M+)
When you hit eight figures, what you own shifts radically - per Financial Samurai’s reader surveys:

*Public-stock slices often include concentrated founder shares - not a three-fund portfolio.

Index funds preserve wealth; concentrated equity creates it. Nick Maggiulli’s “Wealth Ladder” framework puts this in stark perspective. He defines wealth in six levels, each a 10x jump from the last. Level 4 ($1M-$10M) gives you “travel freedom” - you can vacation wherever you want. Level 5 ($10M-$100M) provides “house freedom” - your dream home becomes possible without impacting your finances.

Here’s the uncomfortable truth: even if you hit that Microsoft L70 comp and save religiously for 30 years, you’ll likely land squarely in Level 5 but just barely - most will end up in Level 4. The traditional FAANG-and-index-funds path has a ceiling, and that ceiling sits below Level 5.

To break into Level 5 and beyond requires something different - concentrated ownership that can compound beyond what any salary, no matter how astronomical, can deliver. The gap between Level 4 and Level 5 isn’t bridged by saving another 10% or getting one more promotion. It’s bridged by ownership.

My Asymmetric Wealth Playbook (The 90/10 Rule). Here’s the framework I wish someone had shown me earlier: if you’re earning FAANG-level comp, you can easily save your 30% for that “guaranteed” retirement AND still have serious capital left over for asymmetric bets.

The 90/10 Split:

• 90% goes to the traditional path (401k, index funds, mega backdoor Roth)
• 10% of gross income goes to asymmetric bets

At senior levels, that 10% could be $200K+ annually. Write $25K checks for angel investments, small rentals, or side projects. Over 30 years, that’s 80-100 bets. Even if all but one goes to zero and the last one goes 100x, that winner pays for everything. This is literally the VC model - power law returns where one unicorn makes the entire portfolio.

The Three Phases:

1. Fuel the Rocket - Keep W-2 cash flowing; save 30-60%. Think of this as stacking solid rocket boosters.

2. Light the Booster - Direct that 10% into asymmetric bets while salary covers the downside: angel checks, small rentals, nights-and-weekends SaaS.

3. Stabilize the Orbit - When something hits, harvest gains (QSBS, 1031 exchanges), then add index funds for wealth preservation so market swings don’t rip your solar panels off.

If every bet zeros, fine - I’m still on pace for $13M at 60. If even one wins, I punch through the income ceiling that salary alone could never breach.

Real-World Patterns (Financial Samurai Readers)

Here are a few real-life examples shared by readers in the Financial Samurai community:

Common thread: They kept the day job until upside was real. Salary was a risk-buffer, not the prize.

The Psychology of Swinging Big

The hard part isn’t finding opportunities - it’s rewiring a high-earning brain conditioned to equate stability with virtue. When RSUs hit like clockwork, risk looks irresponsible. But:

• Getting laid off at 55 with golden handcuffs? Also irresponsible.
• Missing the window to exercise creativity (and mistakes) while energy is high? Same.
• Outsourcing your richest years to Vanguard and hoping the Bogleheads were right? You get the idea.

Caveat: Asymmetry isn’t YOLO. It’s capped-downside, uncapped-upside. If a single busted deal torpedoes your retirement, you bet wrong. The beauty of the 90/10 split is that your downside is truly capped - worst case, you still retire with $10M+ from your index funds.

Bottom Line

Index funds preserve wealth; concentrated equity creates it.

A FAANG paycheck is rare rocket fuel - but only if you pour some of it into rockets you actually own. Otherwise you’re just leasing horsepower and calling it freedom.

The conventional Bogleheads wisdom isn’t wrong - it’s just incomplete. Yes, max that 401(k). Yes, build that index fund foundation. But once the defensive lines are drawn, ask yourself:

What slice of my future is still on offense?

The answer - not your salary - will decide whether you retire comfortable or transformational.

The truth? I never bought into the idea that being professional meant being serious. In fact, when I joined Google years ago, it was practically encouraged to be not serious. So I never developed the mindset where we abandon laughter to appear mature. Meanwhile, I was the one stacking bottles at my desk or providing constant quips in meetings.

Over time I have realized that my “unprofessional” approach is actually strategic. Here’s proof which I got via Google’s new AI Mode - When we laugh together, our brains release dopamine and oxytocin - the same chemicals that enhance problem-solving and build trust.

That joke before a meeting? I’m helping everyone’s brains shift into creative problem-solving mode. Those spontaneous tea times? They build trust through tiny, consistent connections - building connections slowly over time. Interesting how what I did naturally might actually be a “strategic workplace culture activity” (that’s going into my performance review writeup).

My philosophy is to create fun and not to force funny (because I would fail anyway). When your workplace becomes somewhere people want to be, laughter follows naturally.

Here’s a challenge for you at work: Practice “Yes, and…” thinking. Accept reality (yes, this deadline is tight) AND find opportunity (this is our chance to change our product direction) AND YET we can do it with levity (“Great, more material for my next stand-up!”)

Now if you’ll excuse me, I’m going to brew some earl grey tea… ☕

We’ve created a world where every moment needs to be monetized, optimized, or leveraged for future gain. Even our hobbies are hyperoptimized now.

But here’s what I’m learning: The most valuable things in life resist commodification.

• That hour spent watching birds in your backyard? Not wasted.
• Hiking for the scenery? Not wasted.
• Meditating through the morning? Not wasted.

When we only engage with what has “clear value,” we lose context. We mistake being busy for being meaningful.

The real radical act might be refusing to optimize every experience. Sometimes the most productive thing you can do is sit still and notice what’s actually around you.

Your attention is not a resource to be strip-mined. It’s how you experience being alive.

Here’s how I’m reclaiming mine:

• Notice when I’m being baited by clickbait or outrage - then choose to scroll past (hopefully not this post though? 😂)
• Learn the names of trees and birds in my neighborhood
• Strike up conversations with neighbors without an agenda
• Challenge myself when I feel guilty for “unproductive” time

Maybe it’s time we stopped asking “What’s the ROI?” and started asking “What makes me feel connected to the world?”

Maybe I’m becoming the old man yelling at clouds. But sometimes the clouds need yelling at. 🤣