Karim Gaad
I'm a software engineer and startup CTO, and I built BioTrakk because I wanted an honest answer to a simple question: which of the things I do every day actually change how I feel and what my labs say?
I was logging food in one app, sleep in another, supplements in a spreadsheet and blood work in a folder of PDFs — and none of them talked to each other. So I built a tracker you talk to like a person (on Telegram, WhatsApp or the web) that pulls everything into one timeline and runs real statistics on it: correlations with p-values, not vibes, and structured N-of-1 experiments with baselines and honest verdicts, including "inconclusive".
Everything I publish here follows the same rules I built into the product: numbers over adjectives, primary sources cited for every claim, and plain statements about what the evidence does and doesn't show. I'm not a doctor and nothing here is medical advice — I'm an engineer who takes measurement seriously.
Why I got into this
The honest reason is that I did not want to be blind about my own body. I wanted to know what happens when I eat this, skip that, train, drink, or sleep badly. Not what happens to people on average in a study: what happens to me, from my own data rather than from my memory, which flatters me.
"Biohacking" comes with baggage, stacks of supplements and ice baths and people who measure everything and change nothing. That is not what I mean by it. I mean paying attention with numbers, so the numbers can answer back. Sometimes the answer is that nothing is there, and a tool that cannot say so is not worth having.
What I'm testing on myself
One question at a time, each with a baseline period first and the verdict rules written down before I start, so I cannot decide afterwards that a different number was the one I cared about.
- Alcohol. What it does to my sleep, my resting heart rate and my weight trend, or does not do. I have opinions about this and no evidence, which is the best reason to measure it first.
- Glucose. A month with a sensor, to find which of the meals I actually eat move my glucose, and whether the same meal looks different on a day I trained. I'm not diabetic and this is curiosity, not a test result.
- Body recomposition. Losing fat and building muscle at once, which is exactly the thing a scale on its own cannot see. That means choosing a measure that separates the two before I claim anything about either.
- The slow one. Resting heart rate, sleep and blood work over months rather than days, in the same place as the food and the training so they can be crossed. The point is not to be blind: if something drifts, I want to see it early and take it to a doctor, not notice it a year late.
I'm not a neutral witness about my own product, so the honest test is whether I still use it. I've been logging with it since March: most days, not all, including a three-month travel break where I logged nothing and then restarted. When one of these experiments produces a result worth reading, I'll publish it here, with what I wrote before I started sitting next to what actually happened, including the times the answer is that my data cannot tell.