Enrique Rubio builds and maintains CompatSense — the compatibility engine, the dataset, and the editorial content on this site.
Background
Enrique works with data and infrastructure systems, automation, and AI-assisted technical workflows. CompatSense grew out of a specific, recurring problem: display connectivity specs (DisplayPort, HDMI, USB-C, Thunderbolt) are scattered across manufacturer PDFs, standards documents, and forum threads, with no single place that shows its work. Building a system that tracks where every figure comes from — rather than restating specs from memory — is the actual work behind this site.
What’s covered on CompatSense
- The Compatibility Checker — whether a dock and monitor connection can deliver a given display mode.
- The Display Bandwidth Calculator — the real bandwidth a display mode requires.
- Guides and troubleshooting content on DisplayPort, HDMI, USB-C, Thunderbolt, DSC, and the bandwidth math connecting them.
How research and review work here
Technical research on this site — finding primary sources, organizing evidence, drafting explanations — may be assisted by AI tools. It is not autonomous: every piece is reviewed before publication, and no page is generated or published in bulk. Critical technical claims (bandwidth figures, protocol behavior, verified device specifications) are checked against cited manufacturer, standards-body, or technical sources before publication, not restated from memory. Where the evidence available isn’t sufficient to support a claim confidently, the content says so explicitly — the same discipline the compatibility engine itself follows.
No physical hardware testing is claimed on this site unless explicitly stated as such. See Methodology for how the compatibility engine itself sources and verifies specifications, and Sources & Corrections for the source and editorial policy.
Corrections
If something on this site is factually wrong, it gets corrected. An article’s “Last reviewed” date changes when its claims and sources are re-checked, and material corrections are recorded in the corrections log on Sources & Corrections, which also explains how to report an error.