正在加载视频...

视频加载失败

Every product change risks leaving your docs behind. Here’s how our CX team uses Loops to keep them up to date.

22,739 次观看 • 3 个月前 •via X (Twitter)

8 条评论

Linear 的头像
Linear3 个月前

Learn more and create your own loop:

Manish Baghel 的头像
Manish Baghel3 个月前

why do you need docs if LLMs can document on the spot?

Fiducial.ai 的头像
Fiducial.ai3 个月前

the daily scan plus weekly review is a sensible split. the agent catches drift continuously without turning every small change into an immediate docs edit

JRod 的头像
JRod3 个月前

Linear has public facing docs?

Erik Erelöf 的头像
Erik Erelöf3 个月前

Docs go stale because they're a second artifact kept in sync by hand. Ship the system, then remember to touch the doc. If docs ARE the system map, updating the system updates the doc by definition. Different bet:

Maximiliano Moxarella 的头像
Maximiliano Moxarella3 个月前

docs can never be out of date if you just don't write them in the first place

Jayadeep Reddy 的头像
Jayadeep Reddy3 个月前

Shifting documentation updates to the CX team creates a delayed feedback cycle. Unless the Loops workflow triggers directly from merged engineering code, CX will only discover outdated documentation after users submit support tickets.

Neel Samadder 的头像
Neel Samadder3 个月前

It’s time to discover and transform linear folks This ain’t gonna work for long

相关视频