Tag: #speech-journal

The course is generating more ideas than I can work through — and it's déjà vu: this is exactly what I built Referity for. The product didn't take off, but the habit of talking into the journal stayed.

The Referity race is logged in the voice journal day by day, but the final isn't: fifth place, a jury question we couldn't answer, and a debrief with the organizer. Wrapping it up — and why the next run will be different.

Hung the pull-up bar, finally sorted the car for €916, cleaned out the closets, said goodbye to the €500-a-month coach — and for the first time in a long while I feel energy coming back.

Seventeen minutes into the voice journal about being torn between projects, doomscrolling Instagram, and hunting for a magic solution that was with me the whole time.

The last accelerator session before the final landed on a day when the whole team was away. We canceled even the online option — and then five days of fishing in the fjords did what no weekend ever had.

The structure frontend built in a day, a plan for a rough MVP by the end of the week — and a paid Max subscription to Claude as an investment in development pace.

The deploy is on fire two hours before the presentation, the voice agent lands fifteen minutes before it — and in the evening, out of nineteen teams they name ten, and one of them is ours. All of it on my birthday.

Ran local models on my Mac: embeddings as good as the cloud ones, Mistral extracts tasks from notes. Privacy is turning from a pretty word in the pitch into a feature we can actually build.

In the morning — a new name and the Referity.ai domain with a redirect from the old Speech Journal; in the evening — the first offline presentation at the accelerator. A B grade: one thought slipped my mind and the ending got crumpled.

An email from Startbahn27: we're in the accelerator. Ahead — a kick-off and the first presentation, and that same evening a friend asked to join the team — and I wasn't sure at first whether to be happy about it.

After submitting the application I couldn't stop: three more hours — and the app became an installable PWA, in the afternoon my wife saw it, in the evening — friends. Plus the first survival tests for the recording.

A two-day sprint: the bot turned into a standalone web app with a demo mode — while submitting the accelerator application itself took fifteen minutes and ended with a beer.

Invited a friend into the project — and he caught fire even more than me. We sat down to prepare the accelerator application and recorded the whole brainstorm straight into the journal: target audience, integrations, and the biggest problem — the input interface.

Came to a coworking space to get some work done — walked into a student project pitch session, met a professor, pitched my voice journal in German for the first time, and left with the contacts of a local accelerator.

The voice journal is three weeks old: the habit of narrating my day has stuck, my friends got a ten-minute video, and for the first time I'm recording my year-in-review by voice — into the journal itself.

A holiday week in stolen moments: semantic search via embeddings, a date filter, a chat that links back to the source notes. How the voice journal works inside — and why it's time to stop improving it.

Two sleepless nights — and my Telegram bot now takes voice notes, stores the files, and transcribes them into text. Why I need this at all — I recorded straight into it.