Back to Working Style

Logic Over Emotion

"In God we trust. All others must bring data." — W. Edwards Deming

The Anti-Pattern: "It Feels Right"

In software engineering, gut feelings are often a mask for unexamined bias or lack of rigor. I have seen too many architectures fail because they were built on hype ("resume-driven development") or personal preference rather than objective requirements.

I challenge my teams to show their work. Why this database? Why this framework? What are the trade-offs? If we can't articulate the why with logic and data, we aren't ready to build it.

My Standard of Evidence

  • 1.
    Data > Opinion: Use metrics, benchmarks, and prototypes to validate assumptions.
  • 2.
    First Principles: Break the problem down to its fundamental truths. Does the solution solve the actual problem?
  • 3.
    Objectivity: A critique of your code is not a critique of you. We must be able to discuss technical flaws without emotional defense.

Related Projects