Hacker News Reader

Comment by TheRealDunkirk | Hacker News Reader

Good grief. If the age of YouTube has taught us anything, it's that creating good video of something takes a lot more skill than writing something decent about something. Trying to find the relevant issue in a bunch of unrelated info, within a long writeup, which a user necessarily edits, at least a little, by the nature of writing something out? Pretty easy. Trying to find it in a rambling, 15-minute video? Welp! Good luck, Jira people.

View on HN

The best thing about video is it tethers me to the speed of the content the rambling, 15-minute video content creator mandated; not the speed I can peruse an article.

Also the first person to invent Ctrl+F for video will be a billionaire.

> Also the first person to invent Ctrl+F for video will be a billionaire.

At least YouTube (desktop web) lets you open the (often auto-generated) captions as a transcript on the side.

I don’t use loom, but I remember an interview with someone who had it in their workflow. Isn’t some of Loom’s appeal transcript and video search?

Look let’s you play back the video faster.

Also has captioning, transcripts and summarization.

For when a bug doesn’t seem possible, video remains invaluable.

Not quite Ctrl F, but Loom does use some AI magic to summarize videos and automatically add sections so you can skip to the interesting bits quickly. Only used it once recently, but it perfectly divided my video according to the 3 points I was addressing.

YouTube has transcripts of varying quality, and tools like kagi's universal summarizer can handle videos as well

> Trying to find the relevant issue in a bunch of unrelated info, within a long writeup, which a user necessarily edits, at least a little, by the nature of writing something out? Pretty easy.

This sentiment is one of the reasons why so much documentation is not good.

Writing good, usable, technical documentation is HARD.

I doubt people will record 15 minute videos to report an issue. From my experience people are much better at recording a relevant video vs. describing the issue in our text.

It’s super common and reasonable if it saves days and dozens of emails just to replicate

My experience with enterprise customers is that recording a video is much more effort than typing "the thingy won't foo the bar" ...

That’s mainly because creating and submitting videos is hard with current tools.

The standards are not nearly the same. A team-internal Loom is not intended to be a viral polished social media clip.

Here's a sample scenario from one of my previous jobs: a PR is not getting reviews. After a day I record a three-minute Loom where I walk through the problem and the solution, and post it on the team's channel. A few hours later the PR is approved, without any synchronous work and without me having to spend twenty minutes thinking out and typing out a blog sized post on Slack on the same topic. If anyone ever feels the need to dig out that commit again, the Loom is still accessible.

Loom found a way to solve real problems without more typing or more meetings, and that's why it's been successful. Slack, by the way, has a "record a clip now" feature that I liked even more than Loom for the purpose; but by that point we already standardized on Loom and Loom is better at organizing clips.

I am going to assume that the userbase of Loom doesn't need to pad videos to 10 Minutes because the algorhithm only suggests videos that have enough space for ads, and I've never heard "Make sure to like and subscribe" and "You can edit your privacy settings here. Speaking of Privacy, did you know that your ISP can read all your stuff? Sign up for a free month of BarfVPN using my link" in any of the videos attached to pull requests or bug reports.

Reply on news.ycombinator.com