Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
ACM RecSys 2012: Recommender Systems, Today
Search
Data Science London
October 10, 2012
Technology
1.9k
2
Share
ACM RecSys 2012: Recommender Systems, Today
Neal Lathia @Cambridge_Uni talk at @ds_dln #strataconf 02/10/12
Data Science London
October 10, 2012
More Decks by Data Science London
See All by Data Science London
Semi-Supervised Anomaly Detection
datasciencelondon
0
1.1k
Hacking the Rail: Ingesting, analysing & visualising realtime streaming data
datasciencelondon
1
47k
Stateful Data-Parallel Processing
datasciencelondon
0
47k
Semantic web warmed up: Ontologies for the IoT
datasciencelondon
0
140
IoT data ingestion pipelines and Clojure transducers
datasciencelondon
0
290
TrendCalculus: A data science for trends
datasciencelondon
1
48k
Data Science in Mobile Health
datasciencelondon
1
8.4k
Large-scale Recommender Systems on Just a PC (with GraphChi)
datasciencelondon
1
17k
Taming Graph Dynamics at Scale
datasciencelondon
0
8.2k
Other Decks in Technology
See All in Technology
そのSLO 99.9%、本当に必要ですか? 〜優先度付きSLOによる責任共有の設計思想〜 / Is that 99.9% SLO really necessary? Design philosophy of shared responsibility through prioritized SLOs
vtryo
0
600
Sociotechnical Architecture Reviews: Understanding Teams, not just Artefacts
ewolff
1
170
AI時代の品質はテストプロセスの作り直し #scrumniigata
kyonmm
PRO
4
1.5k
フロントエンドの相手が変わった - AIが加わったWebの新しいインターフェース設計
azukiazusa1
33
11k
クラウドネイティブ DB はいかにして制約を 克服したか? 〜進化歴史から紐解く、スケーラブルアーキテクチャ設計指針〜
hacomono
PRO
6
920
Oracle AI Database@Google Cloud:サービス概要のご紹介
oracle4engineer
PRO
6
1.4k
アプリブロック機能のつくりかたと、AIとHTMLの不合理な相性の良さについて
kumamotone
1
250
Claude Code / Codex / Kiro に AWS 権限を 渡すとき、何を設計すべきか
k_adachi_01
5
1.2k
新卒エンジニア研修、ハンズオンの設計における課題と実践知/ #tachikawaany
nishiuma
2
140
サイボウズ、プラットフォームエンジニアリング始めるってよ ― プラットフォームチームの事業貢献と組織アラインメントの強化
ueokande
0
100
雑談は、センサーだった
bitkey
PRO
2
230
Oracle Cloud Infrastructure presents managed, serverless MCP Servers for Oracle AI Database
thatjeffsmith
0
240
Featured
See All Featured
The Spectacular Lies of Maps
axbom
PRO
1
740
We Are The Robots
honzajavorek
0
220
エンジニアに許された特別な時間の終わり
watany
106
240k
Docker and Python
trallard
47
3.8k
The agentic SEO stack - context over prompts
schlessera
0
770
Testing 201, or: Great Expectations
jmmastey
46
8.1k
Scaling GitHub
holman
464
140k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
122
21k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.6k
Balancing Empowerment & Direction
lara
6
1.1k
How to Align SEO within the Product Triangle To Get Buy-In & Support - #RIMC
aleyda
2
1.5k
Agile that works and the tools we love
rasmusluckow
331
21k
Transcript
acm recsys 2012: recommender systems, today @neal_lathia
warning: daunting task lookout for twitter handles
why #recsys? information overload mailing lists; usenet news (1992) see:
@jkonstan, @presnick
why #recsys? information overload filter failure movies; books; music (~1995)
why #recsys? information overload filter failure creating value advertising; engagement;
connection (today)
@dtunkelang
(1) collaborative “based on the premise that people looking for
information should be able to make use of what others have already found and evaluated” (maltz & ehrlick)
(2) query-less “in September 2010 Schmidt said that one day
the combination of cloud computing and mobile phones would allow Google to pass on information to users without them even typing in search queries”
(3) discovery engines “we are leaving the age of information
and entering the age of recommendation” (anderson)
None
None
input: ratings, clicks, views users → items process: SVD, kNN,
RBM, etc. f(user, item) → prediction ~ rating output: prediction-ranked recommendations measure: |prediction – rating| (prediction – rating)2
traditional problems accuracy, scalability, distributed computation, similarity, cold-start, … (don't
reinvent the wheel)
acm recsys 2012: 5 open problems
problem 1: predictions temporality, multiple co-occurring objectives: diversity, novelty, freshness,
serendipity, explainability
None
problem 2: algorithms more algorithms vs. more data vs. more
rating effort
what is your algorithm doing? f(user, item) → R f(user,
item 1 , item 2 ) → R f(user, [item 1 ...item n ]) → R e.g., @alexk_z @abellogin
problem 3: users + ratings signals, context, groups, intents, interfaces
@xamat
problem 4: items lifestyle, behaviours, decisions, processes, software development
@presnick
problem 5: measurement ranking metrics vs. usability testing vs. A/B
testing
Online Controlled Experiments: Introduction, Learnings, and Humbling Statistics http://www.exp-platform.com/Pages/2012RecSys.aspx
3 key lessons
lesson 1: #recsys is an ensemble ...of disciplines statistics, machine
learning, human-computer interaction, social network analysis, psychology
lesson 2: return to the domain user effort, generative models,
cost of a freakommendation, value you seek to create
@plamere
lesson 3: join the #recsys community learn, build, research, deploy:
@MyMediaLite, @LensKitRS @zenogantner, @elehack contribute, read: #recsyswiki, @alansaid
recommender systems, today @neal_lathia