John Munn – Medium

John Munn

Pinned

John Munn

·

Jul 3, 2025

Causal Inference in Complex Systems. Why Predicting Outcomes Isn’t Enough

Why understanding “why” beats predicting “what” in complex systems.

A 2D digital illustration showing interconnected systems: graphs, arrows, and abstract nodes representing variables, flowing through layered networks and complex patterns, evoking the idea of cause and effect in dynamic systems.

John Munn

·

1d ago

Code Was Always a Liability. AI Is Letting It Grow Faster Than Ever.

What happens when software grows faster than organizational understanding?

Code Was Always a Liability. AI Is Letting It Grow Faster Than Ever.

John Munn

·

May 21

Documents as Code

When Product Specs Stop Guiding Code and Start Generating It

A lone developer sits at a desk between two worlds. On the left, chaotic product and collaboration artifacts float through the darkness: sticky notes, sketches, Slack-like messages, Confluence-style documents, and abandoned diagrams glowing in warm orange and red light. On the right, cool blue folder structures and structured document trees flow into clean code repositories and organized system architecture. Streams of digital energy connect both sides, converging behind the developer to symboli

John Munn

·

May 7

Keep Simple Things Simple. Let Complex Things Earn Their Complexity.

Why most systems get complicated long before they need to

Keep Simple Things Simple. Let Complex Things Earn Their Complexity.

John Munn

·

Apr 30

You’re Solving the Wrong Problems Well

Why strong engineering teams are missing what matters

A neatly organized project roadmap with completed tasks and checkmarks sits above a tangled network of strings and notes representing confusion, misalignment, and disconnected work beneath the surface.

John Munn

·

Apr 22

We Lost a Developer Because of Our Stack

Why system could cost you your best people

A minimalist illustration of a developer standing in a dim workspace, looking out a large window at a city skyline during sunset, with a computer showing code on a desk nearby and soft, muted colors creating a reflective mood.

John Munn

·

Apr 16

Everyone Deserves to Know Where They Stand

Setting clear expectations is a leadership responsibility.

Two colleagues stand in front of a planning board covered with notes, checkmarks, and charts, discussing expectations and progress in a bright office, symbolizing the importance of clear leadership communication and alignment.

John Munn

·

Apr 7

How to Challenge Your Technical Architects So They Actually Grow

Why great architecture leaders stop teaching patterns and start expanding the tradeoffs

A senior engineering leader stands with hands on hips facing a large whiteboard covered in architecture diagrams, service flows, and system dependencies, while several team members watch from a conference table behind them. The scene emphasizes architectural complexity, leadership guidance, and the shift from clean system design to broader organizational thinking.

John Munn

·

Mar 31

How to Measure AI Productivity When the Cost Moves Instead of Disappearing

Why throughput alone lies, where AI quietly moves cost, and how engineering leaders can measure real leverage without creating theater.

Illustration showing AI’s impact on software engineering productivity, connecting workflow speed, code review, developer learning, codebase complexity, and executive ROI decisions through an interconnected futuristic system.

John Munn

·

Mar 24

Your AI Architecture Isn’t Broken. It’s Just Put Together Wrong.

Where engineering leaders get their systems wrong

Your AI Architecture Isn’t Broken. It’s Just Put Together Wrong.

John Munn

John Munn

Engineering leader writing about AI, developer culture, and what actually works in tech leadership. Practical insights with a human edge. www.johnmunn.tech

Following

Help

Status

About

Careers

Press

Blog

Store

Privacy

Rules

Terms

Text to speech