Hello world
Why this blog exists, the evidence-first mindset, disclaimers, and what to expect.
This blog is my public lab notebook. I'm aiming for evidence: questions, controlled setups or benchmarks, and honest conclusions about what works where.
Posts reflect my views and my hardware unless I say otherwise.
Read About for background, keys, and how email works here.
Disclaimers
What's here is my opinion, not my employers', clients', or sponsors'. When something overlaps with work I'll still separate personal takes from official positions.
Experiments run on my dime: my hardware, cloud credits I pay for, and code I own unless a note explicitly says I got sponsored GPU time or borrowed gear. When that happens I'll flag it up front.
If you spot a mistake or disagree with an argument, email [email protected]. That's the inbox I actually read for serious replies.
The mantra this site keeps coming back to
I care about answers you can actually stress-test.
When it's realistic I write from something close to the scientific method: nail down the claim, freeze the scenario, compare options with benchmarks or reproducible demos, then say clearly what's better here (not universal slogans). When evidence is thin I'll say so and treat the piece as a notebook entry, not a final verdict.
That's a big part of why I publish: writing forces assumptions, harness design, and failure modes out into the open.
Replication fits in the same picture: document procedures clearly enough that people can rerun them. When calibration matters, redo external papers or older versions of my own notes. Same curve or a different one, both teach you something.
Why bother publishing
Writing keeps me honest. Turning fuzzy intuition into prose pushes me toward clearer assumptions, tighter experiments, and explicit limits.
This site is also external memory. Over a year I ship tons of fragments that never leave local repos or notebooks. Putting some of that in public helps me see what actually moved instead of feeling stuck.
Friends sometimes ask how I think about a topic. Instead of repeating long chats I can send one link that already has trade-offs, failures, or partial wins.
Publishing also lets me stress-test ideas. Some posts back hunches with numbers; others will age badly and deserve updates. Both are useful.
For opinion-heavy posts, keeping a dated version in public helps me stay honest about drift: I can point to what I believed earlier, admit when something aged poorly, show where I changed my mind, and explain why instead of pretending my takes were always consistent.
What you'll find
- ML engineering notes.
- Agentic systems experiments.
- Reverse-engineering curiosity, written responsibly.
- Art-adjacent tangents when they cross tooling.
- Projects I'm working on.
- And maybe more… 😉
Want plain Markdown instead of HTML? Swap .html for
.md on the URL path.
For this note that's /2026/05/01/hello-world.md
(front matter included). Handy if you want to edit offline or paste into an agent.