4 ms·

47min video. Presented slowly, very little of the info is about "difficult conversations". It's largely about giving presentations. A written summary of key poi

47min video. Presented slowly, very little of the info is about "difficult conversations". It's largely about giving presentations. A written summary of key points would be helpful.

Jugurtha 7y ago
I watch videos that don't have slides at 16x using Video Speed Controller extension[0]. A 47 minute video becomes a 3 minute video I can go through and judge information density, slides quality, topics addressed, depth of said topics, whether there's a topic that matters to me that's addressed there. Then I decide if I'm going to watch the thing, which I note using Taskwarrior with a +watch tag, a link to the video, a description on what it's about. Then I watch it and take some notes, augment some issues with the information acquired or references, etc. I don't really do this with great quality speakers I'm familiar with, as I'm sure I will learn things. [0]: https://github.com/igrigorik/videospeed https://github.com/igrigorik/videospeed
- sarakayakomzin 7y ago
  this sure sounds like a lot of work compared to clicking on a few random points of the video and making a determination from there.
- wcarss 7y ago
  Do you keep any notes or record of the good talks/speakers online? It sounds like it would be valuable!
  - Jugurtha 7y ago
    Sort of. Since all I think about in my waking hours is product, company, roadmap, and vision, my notes are very specific to these issues and goals and simply have become the company's knowledge base. The notes for the talks are practically non existent and are just a subset, and a few lines at most.. Other notes are about strategy, handbook to be able to operate the company from paying taxes to hiring, onboarding, and firing to how to write issues and commit messages, to tools we use or could use, to features and roadmap, to the experience from soup to nuts of different stakeholders, to the induced demand and workers influx it hopefully will cause, to what the company should focus on for the next two months to become what it will in the next five to ten years with nth order effects. Different x maginification from the bug fix to the economic consequences on countries with poor connectivity, and how closing an issue relating to compressing static files moves us a hair. Success is the team not missing a beat if I disappear, because everything would be in place for continuity and growth and slashing cumulative lifetimes of suck. I've always had a proclivity for writing, but there are other reasons I'm doing it that much and want to do it more. Some hard transitions and developments that almost killed the company, and we turned it around with some hard learned lessons and the earned "wisdom" not to have it happen again.

47min video. Presented slowly, very little of the info is about "difficult conversations". It's largely about giving presentations. A written summary of key points would be helpful.

Jugurtha 7y ago

I watch videos that don't have slides at 16x using Video Speed Controller extension[0]. A 47 minute video becomes a 3 minute video I can go through and judge information density, slides quality, topics addressed, depth of said topics, whether there's a topic that matters to me that's addressed there. Then I decide if I'm going to watch the thing, which I note using Taskwarrior with a +watch tag, a link to the video, a description on what it's about. Then I watch it and take some notes, augment some issues with the information acquired or references, etc. I don't really do this with great quality speakers I'm familiar with, as I'm sure I will learn things. [0]: https://github.com/igrigorik/videospeed https://github.com/igrigorik/videospeed

sarakayakomzin 7y ago
this sure sounds like a lot of work compared to clicking on a few random points of the video and making a determination from there.
wcarss 7y ago
Do you keep any notes or record of the good talks/speakers online? It sounds like it would be valuable!
- Jugurtha 7y ago
  Sort of. Since all I think about in my waking hours is product, company, roadmap, and vision, my notes are very specific to these issues and goals and simply have become the company's knowledge base. The notes for the talks are practically non existent and are just a subset, and a few lines at most.. Other notes are about strategy, handbook to be able to operate the company from paying taxes to hiring, onboarding, and firing to how to write issues and commit messages, to tools we use or could use, to features and roadmap, to the experience from soup to nuts of different stakeholders, to the induced demand and workers influx it hopefully will cause, to what the company should focus on for the next two months to become what it will in the next five to ten years with nth order effects. Different x maginification from the bug fix to the economic consequences on countries with poor connectivity, and how closing an issue relating to compressing static files moves us a hair. Success is the team not missing a beat if I disappear, because everything would be in place for continuity and growth and slashing cumulative lifetimes of suck. I've always had a proclivity for writing, but there are other reasons I'm doing it that much and want to do it more. Some hard transitions and developments that almost killed the company, and we turned it around with some hard learned lessons and the earned "wisdom" not to have it happen again.