Who owns and manage product documentation in your OSS / dev tool startup?

• dozer

  20 1,446 9.7 Rust

  Dozer is a real-time data movement tool that leverages CDC from various sources and moves data into various sinks. (by getdozer)

  

Hi HN,

I'm Matteo and co-founder of Dozer (https://github.com/getdozer/dozer), a backend tool for building data products. Over the past few months we have done good progress with the product development but our documentation needs a lot of work. Myself, my co-founder and the entire team are juggling among many activities, and one of them is producing good documentation, and that is the part where we are bit struggling.

We have tried to hire a couple of tech writers but it's really not working out as we wanted. Our product is a dev product, and it is very hard to find tech writers who have that depth to think what a developer need. At the same time, asking the dev team to write documentation produces low quality docs (obviously devs prefer to write code and they just to go back to that as fast they can).

The result is that I end up writing most of documentation or refactoring the entire content produced by tech writer. But this approach will not scale.

How do you guys solved it? I'm curios to know about the approach of other startups.

Thanks

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project