Загрузка видео...

Не удалось загрузить видео

На главную

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

Похожие видео