Video yükleniyor...
Video Yüklenemedi
Every product change risks leaving your docs behind. Here’s how our CX team uses Loops to keep them up to date.
22,739 görüntüleme • 2 ay önce •via X (Twitter)
8 Yorum

Learn more and create your own loop:

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

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

Linear has public facing docs?

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:

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

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.

It’s time to discover and transform linear folks This ain’t gonna work for long
Benzer Videolar
Sensitive content
Remember that Mikan doesn't have giant pockets to keep her clothes in, so be careful and always remember where you left them Leaving clothes behind have it's risks...
Exhibitionism Club! 🔞
98,328 görüntüleme • 3 yıl önce

