Docs are always the first thing to rot. When engineers leave or switch projects, a ton of context disappears: why decisions were made, what the gotchas are, how to onboard the next person.
I’m exploring a tool that interviews engineers, architects, machinists and other technical staff about their projects instead of asking them to write docs. It would ask structured questions (What tradeoffs did you make? What would you warn the next person about?) and turn the answers into a lightweight, searchable knowledge base. Would this actually solve a pain point for your team, or just become one more thing nobody uses?
Curious to hear if this resonates.
Comments URL: https://news.ycombinator.com/item?id=45459893
Points: 1
# Comments: 0
Source: news.ycombinator.com
