talk · HACKER NEWS RECOMMENDATION
Mountain West Ruby 2012 Capability vs. Suitability by Gary Bernhardt
Confreaks · 2 HN recommenders · 2 recommendation months
Recommended by 2 Hacker News commenters across 2 months (2015–2023).
SignalTube analysis
Among 146 other talk videos tagged Software architecture & design, the mean is 4.2 distinct HN recommenders. This video has 2 distinct HN recommenders, below that mean. Recommendations span 2 distinct months; the peer average is 4.3 months. This is a data-derived comparison, not a human review or quality rating.
50% of its 4 labeled comments are marked as recommendations or strong recommendations. HN mention years are 2015–2023; those years describe discussion history, not upload date. Its verified runtime is 19 minutes 44 seconds. YouTube lists its publication date as 2012-06-05.
- Channel / speaker
- Confreaks
- Verified runtime
- 19m 44s
- YouTube upload date
- 2012-06-05
- Hacker News mention years
- 2015–2023
SAME TOPIC AND FORMAT
Compare with related videos
The comparison cohort uses other talk videos in Software architecture & design. “Shared recommenders” counts HN users who recommended both videos in the source graph.
| Video | HN recommenders | Recommendation months | Positive label share | Shared recommenders | Runtime | Upload date |
|---|---|---|---|---|---|---|
| Mountain West Ruby 2012 Capability vs. Suitability by Gary BernhardtCurrent video | 2 | 2 | 50% | — | 19m 44s | 2012-06-05 |
| RailsConf 2014 - All the Little Things by Sandi Metztalk · Confreaks | 15 | 15 | 75% | No recorded overlap | 38m 47s | 2014-05-21 |
| "Simple Made Easy" - Rich Hickey (2011)talk · Strange Loop Conference | 14 | 14 | 70% | No recorded overlap | 61m 39s | 2021-09-02 |
| How To Design A Good API and Why it Matterstalk · Google TechTalks | 12 | 12 | 93% | No recorded overlap | 60m 19s | 2007-10-09 |
THREE SOURCE-BASED CONTEXT POINTS
Why Hacker News recommends it
Each note combines the dataset’s stance label and short rationale; comment bodies are not reproduced. Open the HN source for the original discussion.
The archive classifies this as a recommendation in “Ask HN: Enabling” vs. “Restricting” in Programming”. Its short rationale: 2012 talk on enabling versus restricting technologies.
The archive classifies this as a contextual reference in “Absence of certain features in IRC considered a feature”. Its short rationale: Capability versus suitability model applied to IRC.
The archive classifies this as a contextual reference in “Create your own dysfunctional single-page app”. Its short rationale: Framework for viewing languages as capable or suitable.