Skip to content
Tech Intuition
thetechintuition.com

Everything you see is a system.

Most systems work for reasons nobody wrote down. I find those reasons, build with them, and explain them until they stop feeling like magic.

Enter the SystemResume
  1. You are here

  2. How I understand systems.

    Meet the engineer

  3. What I build from that understanding.

    See what I build

  4. Making that understanding intuitive for others.

    Enter Tech Intuition

  5. Tech Intuition

    Which raises the next question.

02Identity

Three dimensions. One loop.

Thinking becomes building. Building becomes something worth explaining. Explaining sends me back to thinking.

02

Builder

What I build from that understanding.

Products · Experiments · Production

See what I build →

03The engineering mind

How it thinks.

Not a biography. The rules that hold in every system, whether it is being built, reviewed or explained.

  1. Rule 01

    Understand it before you optimize it.

    Most performance problems are comprehension problems. Draw the system, trace the request, then touch the code.

  2. Rule 02

    Complexity doesn't disappear. It moves.

    Every simplification is a transfer. Know where the cost landed, and who pays it.

  3. Rule 03

    Every abstraction has a cost.

    It hides the detail until the day the detail matters. Know what you are standing on.

  4. Rule 04

    Design for failure, not the happy path.

    Networks partition, queues back up, dependencies lie. Plan for the day it happens, not the day it is demoed.

  5. Rule 05

    If you can't explain the bottleneck, you don't understand it yet.

    Explaining is a debugging tool. It is also why this site exists.

04Selected systems

Problems, not screenshots.

Two systems, and the idea that made each one work.

  1. S-01

    Webstore Separation

    System / Frontend delivery

    Engineering idea

    Decouple the storefront so it ships independently, served as static assets through a CDN and object storage.

    CDNObject storageIndependent deploys
  2. S-02

    Distributed Rate Limiting

    System / API protection

    Engineering idea

    Enforce limits consistently across instances by moving the counters into shared state in Redis.

    RedisShared stateConsistency
All projects
05Tech Intuition

Technology, explained from the inside.

Tech Intuition is the media side of this site: videos, system design and engineering explanations about how real-world technology actually works.

Videos and articles arrive here as they are finished.

06Next

Explore the system.

ResumeEngineerTech Intuition

Or just say hello: contact.