Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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

22,739 Aufrufe • vor 3 Monaten •via X (Twitter)

8 Kommentare

Profilbild von Linear
Linearvor 3 Monaten

Learn more and create your own loop:

Profilbild von Manish Baghel
Manish Baghelvor 3 Monaten

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

Profilbild von Fiducial.ai
Fiducial.aivor 3 Monaten

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

Profilbild von JRod
JRodvor 3 Monaten

Linear has public facing docs?

Profilbild von Erik Erelöf
Erik Erelöfvor 3 Monaten

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:

Profilbild von Maximiliano Moxarella
Maximiliano Moxarellavor 3 Monaten

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

Profilbild von Jayadeep Reddy
Jayadeep Reddyvor 3 Monaten

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.

Profilbild von Neel Samadder
Neel Samaddervor 3 Monaten

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

Ähnliche Videos