Welcome "Inside the Silicon Machine"!

As complexity grows, the interface becomes the system

Hi! I’m very excited to be starting a new substack titled “Inside the Silicon Machine”!

My writing focus is simple: how the chip world really works — from technology to psychology, and interfaces in between.

I’m an analog/mixed-signal engineer who’s worked across design, applications, and validation, and I’m especially interested in the technical interfaces where chips succeed or fail - and the human systems that shape those outcomes.

Why “Inside the Silicon machine?”

There’s no shortage of sophisticated technical content out there on semiconductors: deep dives on architectures, memory systems, scaling limits, and performance claims. I genuinely love this stuff. Semiconductors are arguably the most advanced industrial ecosystem on the planet, and learning the sub-specialties is part of the fun.

But as chips become more sophisticated and more interdependent, complexity gets broken into more sub-specialties. New disciplines emerge specifically to manage and verify interdependent behavior — from verification at the chip level to SI/PI at the board level — and that creates more interfaces.

So we interface through requirements, specs, reviews, tickets, and organizational structure.

And as the number of interfaces grows, it becomes easier for teams to lose context about what other groups are optimizing for. I’ve seen that gap show up across several dimensions:

• Business vs Engineering

• Chip vs Package/Board vs System vs Software

• Research exploration vs Commercial execution

• Pre and Post-silicon specialties within the same design cycle

The Missing Layer: People, Incentives, and Culture

Chips are ultimately designed by really smart humans— often with MS/PhDs — but humans are still subject to incentives, bias, emotion, risk perception, and social dynamics.

A lot of useful knowledge about incentives, organizations, decision-making, and culture is widely developed in academia, business ecosystems, and other industries — but it isn’t commonly translated into everyday engineering language.

Many successful technology leaders seem to follow a pattern: they learn the technology deeply, then layer in “just enough” organizational and business understanding to scale execution.

That’s the bridge I want to build here — and ideally, it will foster better cross-functional empathy along the way.

Why I’m Qualified

I’ve had an unusual chance to see across multiple layers of the chip ecosystem:

• Analog/mixed-signal engineering with real exposure to applications + validation

• Experience seeing both R&D exploration and commercial execution

• Work across defense, R&D, and commercial semiconductor contexts

• A long-standing interest in leadership, organizational behavior, and psychology

• Practice simplifying complex topics into clear, first-principles explanations (including TA experience across software, analog, and digital material)

What you can expect

My goal is to bridge engineering and the business/organizational layer in two ways:

• Keep the bridge to real technical innovation: the underlying technical ideas that become products people can ship and scale.

• Offer working frameworks for the organizational layer: how incentives, decision-making, and execution structures shape engineering outcomes upstream.

Most of my posts will fall under the following categories:

• The Technological Side: high-level explainers on analog/mixed-signal/RF fundamentals and system interfaces (without getting lost in specialist weeds).

• The Business side: strategy, innovation, organizations, and execution as they relate to engineering reality

• The Psychological side: incentives, culture, communication

• Occasional adjacent deep dives, for example, how Taiwan’s historical factors shaped key parts of today’s supply chain (including TSMC and Foxconn)

• Conference notes: ISSCC and DesignCon — where research and system integration interfaces are especially visible

Books, thinkers, and experiences I’ll draw from (among others)

• Technology: Analog Integrated Circuit Design (Carusone), Analog to Digital Converters (Pelgrom), Power Management Integrated Circuits (Wicht), RF Microelectronics (Razavi)

• Incentives & Economics: Basic Economics (Sowell)

• Organizational Leadership: Turn the Ship Around! (Marquet), Reframing Organizations (Bolman & Deal)

• Innovation: The Innovator’s Dilemma (Christensen), Loonshots (Bahcall)

• Strategy: Good Strategy/Bad Strategy (Rumelt)

• Culture: Quiet (Susan Cain), Hofstede’s Cultural Dimensions Theory, plus lessons from travel across Europe and Asia

• Fiction (as mental models): Foundation, Hyperion, Ender’s Game (themes that still map to modern systems)

Who should Read this:

This is for people who live at the interfaces in the semiconductor ecosystem — and it’s broadly applicable to any sophisticated, cross-functional product.

If you touch any of these handoffs, you’ll likely get value from building a clearer mental model of the other side:

• Marketing / product: translating customer needs into requirements

• Program/project management: coordinating execution and tradeoffs

• Systems / architecture: turning requirements into budgets and constraints

• Design: implementing blocks and closing performance, power, and area

• Applications / FAEs: mapping customer use cases to product behavior

• Validation: finding where reality breaks assumptions

• Test / manufacturing: turning “works in the lab” into “works at scale”

Takeaway

This is an ambitious writing project. I won’t follow the plan perfectly, and I’ll sometimes explore “random” adjacent topics that I think will connect later.

I also don’t promise to always be right. Some topics are complex, and I’ll inevitably make mistakes — especially when I’m stretching into areas above my head. I’m open to feedback, corrections, and thoughtful disagreement.

-