
Founder @GetDoctave | Paving a documentation happy path
Helsinki, Finland
Joined January 2012
- Tweets401
- Following512
- Followers225
- Likes427
We've been happy users of @TauriApps for well over a year now at @GetDoctave. Really solid.
We've just started building a new text editor/IDE for documentation based on it.
Excited to see the project grow!
Tauri 2.0 Stable. Out now. Read more:
v2.tauri.app/blog/tauri-20/
We're building a brand new editor for technical writing and docs-as-code at @GetDoctave!
We're pushing the boundaries of what an editor for documentation and technical writing professionals could look like.
Interested? Join the waitlist! Link below 👇
Was writing a docstring for a #rustlang function, and the AI autocompleter just decided to straight up roast my code 😐
I had the pleasure of chatting with Manny Silva about his work on VerbaGPT, and how he uses LLMs to cut his time-to-first-draft from 2 days to an incredible 5 minutes
Full conversation on YouTube 👇
youtu.be/fr-t0gMmrFk
Granted @GetDoctave isn't a particularly data-heavy app, I feel like we just crossed some kind of milestone because we had to add a missing database index to address a performance issue.
Resulted in a good 150ms faster page loads for some customers!
My discussion about Markdown and Structured Authoring with @remoquete is out!
We discussed lots of interesting ideas about how to bring structured authoring concepts into a docs-as-code context
Take a look!
youtube.com/watch?v=M5L0xyER…
Had the pleasure of chatting with @remoquete last week about Markdown and Structured Authoring!
We talked about what structured authoring would look like in a docs-as-code, context and ways we could get there.
Tune in Monday next week for the full discussion!
Slack helpfully transcribed a short video I uploaded to the @GetDoctave general channel.
Unfortunately it doesn't seem to understand Finnish very well...

ALT Transcript (auto-generated) Nik at 10:37 AM 0:00 Cord on this computer. 0:02 No, it's only a good recording and that's not emotionally go at the,, ok. 0:08 It's all on, you go to the cloud. 0:10 No, I guess I only have, I got, no, not about the hand. 0:12 I. 0:14 locale locale St io. 0:16 Ah, ok. 0:18 Moda, ma non lo è stata. 0:21 agora uma matéria da Casa não votada na próxima em Molenbeek. 0:26 mil Tratado Leina ここ で 雇っ た まあ もらっ て
Always found @twilio's docs to be world class. This was an interesting read.
TL;DR: they've built a new custom docs platform on Next.JS, use Markdown/MDX for content, and a traditional docs-as-code authoring workflow.
twilio.com/en-us/blog/new-er…
One thing that LLMs cannot seem to get away from is using meaningless words like "streamlining", "elevating", and "synergy".
I'm constantly prompting Claude/ChatGPT to not use corporate jargon, but it sneaks back all the time. Just seems really deeply ingrained 🤷
Your docs are the product.
For some companies, the docs are the biggest touch point that the your user will interact with. Much more important than the copy on your marketing site.
Invest in your docs, hire tech writers, make your users happy.
We're going to be adding multi-repository support at Doctave: letting you use content from multiple Git repositories to construct a single portal. An update to any of the repositories that make up your docs will update your site automatically, all while maintaining consistency
Managing diagrams as text with the rest of your docs 🤌
We've added diagram support powered by @mermaidjs_ 📈
You can now add flowcharts, pie charts, gantt charts and more, defined as text inline inside your Markdown content.
Still think you should think twice about putting an AI in front of your carefully written developer docs.
Your users are not experts in your product. They cannot tell when the LLM is hallucinating and making up features, which it inevitably will (for now at least).








