My favorite three words in science? “I don’t know.” Not as defeat — as a trailhead.
I’ve been sick for years. The doctors have names for some of what’s happening in my body, but not all of it. The honest answer to “what causes your disease?” is still we don’t know. And after the fourth specialist, the sixth round of bloodwork, the third time you hear “everything looks normal” when nothing feels normal — you learn something about the space between questions and answers.
That space is where I live now. Professionally, personally, and scientifically.
The Diagnostic Odyssey Is a Data Problem
When a patient presents with symptoms that don’t fit clean diagnostic categories, the system does what systems do: it routes you to the closest match and moves on. But rare diseases don’t fit clean categories. That’s what makes them rare.
The gap isn’t in the medicine — it’s in the infrastructure. The data exists somewhere: a paper in a journal no one reads, a case study at an institution you’ll never visit, a pattern in a dataset that no one has connected yet. The problem is that these fragments don’t talk to each other. And the patient — the person least equipped to coordinate a research program — becomes the de facto project manager of their own diagnosis.
Not Knowing as a Practice
Feynman once said he could live with doubt and uncertainty and not knowing. I used to think that was about intellectual humility. Now I think it’s about endurance. You have to be willing to hold a question for a long time — years, sometimes — without collapsing it into a convenient answer.
That’s what rare disease patients do every day. We hold questions that the healthcare system has given up on. And the best scientists I’ve worked with do the same thing: they sit with not-knowing long enough for the real pattern to emerge.
Why It Matters for What I Build
Lattice Protocol exists because of this gap. Federated research infrastructure — compute that crosses institutional boundaries, data that moves while preserving privacy, models that improve from every patient encounter — is the engineering response to the diagnostic odyssey.
I don’t know what causes my disease. I may never know. But I can build systems that make the next patient’s path shorter. That’s not optimism — it’s engineering. And it starts with being honest about what we don’t know yet.