Git Archaeology #10 — Dark Matter: The Invisible Gravity

Source: Dev.to

Introduction

Most of the universe’s mass cannot be observed. The same is true in code universes.

In Chapter 9, I wrote about Origin — the Big Bang and the first commit of code universes.
This time, I write about another force that exists in the universe: an invisible force.

Dark Matter in the Physical Universe

Most of the universe’s mass is said to be dark matter. Yet it cannot be observed—telescopes can’t see it, and there’s no means of direct detection. We are certain dark matter exists because it manifests only as gravity, and gravity is undeniably there. When you calculate a galaxy’s rotation speed, visible matter alone can’t explain it; invisible mass is holding the galaxy together.

Dark Matter in Code Universes

Code universes have dark matter too. It’s the work that doesn’t appear in commits:

• Code review
• Design discussions
• Pair programming
• Dependency cleanup
• Small refactors
• Documentation fixes

These activities are as small as commits—or don’t become commits at all—yet they support the stability of the universe.

Anchors as Dark Matter

Recall the Anchor role defined in Chapter 3. Anchors don’t stand out; neither their Production nor Design scores are exceptional. But without them, the universe would quickly crumble. Anchors are the dark matter of code universes. Just as galaxies can’t rotate without dark matter, teams can’t stay stable without Anchors.

EIS can detect Anchors, but what EIS shows is dark matter’s gravitational effect—not dark matter itself. The real work of an Anchor lies in the parts that don’t appear in code.

• Reviews don’t produce commits, yet a codebase without reviews loses its structure.
• Observation changes the universe: the Observer Effect in physics mirrors how observed code always changes—perhaps being deleted, improved, or spawning new dependencies.
• Thirty minutes in front of a whiteboard can decide a design that shapes thousands of lines of code, yet those minutes aren’t recorded in commits.

Invisible forces determine visible structure. A three‑line rename or a five‑line method extraction may look like “noise” in the commit log, but they are acts of fighting the universe’s entropy. The accumulation of small refactors prevents structural decay.

Limitations of EIS

EIS cannot see dark matter. It is a commit‑based tool and can’t measure work that doesn’t appear in commits:

• Quality of reviews
• Depth of design discussions
• Effect of mentoring
• A team’s psychological safety

These are all dark matter. What EIS shows us is only the “visible part” of the universe—stars and galaxies. Knowing that dark matter exists lets you interpret EIS numbers correctly. An Anchor’s score looks low because most of their work is dark matter. Judging an engineer’s productivity solely by numbers is the same mistake as calculating a galaxy’s mass from visible matter alone.

When using EIS, always be aware of dark matter’s existence. An engineer with a low score might actually be supporting the team’s stability; design decisions that don’t appear in commits might be the core of the structure; the quality of reviews might be lifting the entire team’s Quality scores. Trying to see the invisible is itself an act of observing the universe.

Related Chapters

• Chapter 1: Measuring Engineering Impact from Git History Alone
• Chapter 2: Beyond Individual Scores: Measuring Team Health from Git History
• Chapter 3: Two Paths to Architect: How Engineers Evolve Differently
• Chapter 4: Backend Architects Converge: The Sacred Work of Laying Souls to Rest
• Chapter 5: Timeline: Scores Don’t Lie, and They Capture Hesitation Too
• Chapter 6: Teams Evolve: The Laws of Organization Revealed by Timelines
• Chapter 7: Observing the Universe of Code
• Chapter 8: Engineering Relativity: Why the Same Engineer Gets Different Scores
• Chapter 9: Origin: The Big Bang of Code Universes
• Chapter 10: Dark Matter: The Invisible Gravity (this post)
• Chapter 11: Entropy: The Universe Always Tends Toward Disorder
• Chapter 12: Collapse: Good Architects and Black Hole Engineers
• Chapter 13: Cosmology of Code

Tools

• GitHub: engineering-impact-score — CLI tool, formulas, and methodology all open source.

  brew tap machuz/tap && brew install eis