Skip to content
HomeVideos
AllLongsCategoriesPlaylists
BooksBlogsPodcasts
HistoryListsWatch laterLiked videosFollowing

The videos, books, blogs and podcasts Hacker News keeps recommending, all in one place.

VideosBooksBlogsPodcastsAboutPrivacySettings

Data from Hacker News, HackerTube, HackerBooks, HackerBlogs and Open Library. Credits · Not affiliated with Y Combinator.

HomeVideosBooksBlogsPodcasts
Ctrl K

    Listen to Scotty

    Wayne Lee

    3 HN mentions · mentioned in 3 months, 2018–2022

    YouTube

    0:44 · 647K views · Mar 3, 2008

    A one-minute clip of Scotty from Star Trek giving advice to engineers about managing expectations in estimates. It is a comedic bit of workplace wisdom.

    HN uses it as a joking reference in threads on estimation, technical debt and managing expectations.

    Arts, Comedy, Music & FilmFilm & TV clipsSoftware practice, open source & careers
    1. 0:26
      Star Trek - Hello ComputerPhil Jahner361K views • 16 years ago
    2. 2:36
      Star Trek 4: The Voyage Home (7/10) Movie CLIP - The Miracle Worker (1986) HDMovieclips2.6M views • 15 years ago
    3. 3:38
      Margin Call (5/9) Movie CLIP - A Bridge (2011) HDMovieclips1.9M views • 12 years ago
    4. 2:09
      Margin Call Best Quote by Will Emersonchrislaucn3.1M views • 14 years ago
    5. 37:45
      #NoEstimates (Allen Holub)Allen Holub259K views • 11 years ago
    6. 24:00:01
      Star Trek TNG Ambient Engine Noise (Idling for 24 hrs)crysknife0075M views • 15 years ago
    7. 0:34
      Did you see that ludicrous display last night?RandyRandom642K views • 16 years ago
    8. 0:41
      Data uses most secure code ever Star Trek TNG (Blu Ray HD)HD_Picard185K views • 9 years ago
    9. 2:34
      Michael Drives Into A Lake - The Office USThe Office5.5M views • 9 years ago
    10. 1:02:30
      "Agile Methods The Good, the Hype and the Ugly," Bertrand MeyerAssociation for Computing Machinery (ACM)18K views • 11 years ago
    11. 11:46
      James Mickens on JavaScripttablet reader49K views • 11 years ago
    12. 1:09
      D. Scott Williamson, ExpertD. Scott Williamson1.2M views • 12 years ago
    13. 2:01:18
      GET LAMP: The Text Adventure DocumentaryGoogle TechTalks244K views • 15 years ago
    14. 2:29
      Office Space the Bob's Interview Typical Dayghostb136.8M views • 18 years ago
    15. 0:23
      Office Space - "I Have People Skills!"MovieReferences243K views • 14 years ago
    16. 0:13
      McGill @ SimpsonsEfrye666180K views • 16 years ago
    17. 4:17
      Jeeesus WEPT!The KenMik Edit1.4M views • 11 years ago
    18. 1:44
      Let's Enhance HDDuncan Robson879K views • 13 years ago
    19. 0:13
      Star Trek TNG (Peak Performance) Picard Quote - It is possible to commit no mistakes and still lose.Ponyboy137K views • 10 years ago
    20. 3:03
      Moneyball - Firing peopleThe BigTime Group1.2M views • 9 years ago

    3 comments from Hacker News

    1. @JachJul 2018· in “Ask HN: As a CTO, what is your most frustrating problem with technical debt?”

      How are you measuring these things? 1. It's one of my dreams to work at a place using prediction markets for internal estimates. Anything else feels worthless and engineers are incentivized into the "quadruple what you're currently thinking" estimate so they more often meet deadlines -- or try to "under-promise, over-deliver" except management rightly catch on to that one immediately. (As an engineer I still want to be a La Forge and work with other La Forges, even if Scotty[0] sometimes has a point; modeling managers as demanding children has some gaping model gaps.) 2. What I've seen is that many delighters aren't that hard, but they're often treated as "polish" that goes into the p3/p4 priority backlogs and maybe might resurface if a customer ever brings up a desire for that to the product management. What delighters have you seen that weren't shipped because they were too hard? Were they actually too hard, or was it just too much to get them done by some release date alongside all the other stuff so they get shoved to the backlog just the same? 3. Are you measuring bug count based on what customers report or internal bug reports? If internal, even if people aren't gaming this directly, it's still easy to get into a bad cycle where reported bugs get ignored and go unfixed which leads to fewer reported bugs. That might be mistaken for higher quality. 4. Is this one measured from surveys? Obviously not all features are directly customer visible so let's take something concre

      CitesView on HN
    2. @dvtrnMay 2020· in “Back of the envelope estimation hacks”

      My old man spent 30 years working as a mechanical engineer for General Electric in their gas turbine division and used to bring home these sorts of tales similar this with people who reported to him, which subsequently informed him on how he needed to communicate to the manager he reported to on when to expect deliverables. Most memorable from this was watching his reaction while he and I were watching an episode of Star Trek the Next Generation where his exact problem was manifested into reality by his favorite character : this video Nonetheless, I may or may not have employed my dad’s and Scotty’s method now that I have a team reporting up to me, each with their own strengths and weaknesses in delivery. Grooming them has been a genuine pleasure, though.

      AsideView on HN
    3. @ZenstJul 2022· in “Beigels, software, and why you should control queues instead of cycle times”

      Which reminds me of the old engineering trick of saying it will take longer than it does as managing expectations is an art best explained by Scotty - this video

      AsideView on HN