Someone has to jump in first.
Production AI, self-hosted infrastructure, thin-process teams — I test the water and write down what's actually in it. No hype, no courses, and every claim comes with a receipt.
Numbers I can defend in an interview.
Advice is cheap; logs aren't. Everything below is labeled the way I'd say it across a table — what I built with my own hands, and what was built to my spec.
Recent dives.
Three desks, one notebook.
Player-coach, by conviction.
I'm Kavi — a product executive in Helsinki. I've built an integrations business from zero, moved a company off the cloud onto infrastructure I help operate, and run a 20-person org that delivers like a much bigger one. I still build with my own hands, and I label the difference: hands-built vs. built-to-my-spec.
This notebook is where I write down what the water was actually like — before the hype, after the incident, with the numbers attached where I'm allowed.
helsinki · english / sinhala / 日本語 (learning) · full story →
why "first penguin"?
The colony waits at the edge of the ice. Nobody knows if there's a leopard seal down there. Someone has to jump first — and then everyone knows.
It's an old idea (Randy Pausch gave awards for it) and my job description in practice: jump first, surface, report honestly. The classic telling stops at the jump; this notebook is the part where the penguin comes back with notes.
The bear reviews each dive from the shore. Different methods, same expedition.