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
2
1.9k
ACM RecSys 2012: Recommender Systems, Today
Neal Lathia @Cambridge_Uni talk at @ds_dln #strataconf 02/10/12
Data Science London
October 10, 2012
Tweet
Share
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
130
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.3k
Large-scale Recommender Systems on Just a PC (with GraphChi)
datasciencelondon
1
17k
Taming Graph Dynamics at Scale
datasciencelondon
0
8.1k
Other Decks in Technology
See All in Technology
10Xにおける品質保証活動の全体像と改善 #no_more_wait_for_test
nihonbuson
PRO
2
290
AzureでのIaC - Bicep? Terraform? それ早く言ってよ会議
torumakabe
1
560
登壇駆動学習のすすめ — CfPのネタの見つけ方と書くときに意識していること
bicstone
3
110
Digitization部 紹介資料
sansan33
PRO
1
6.8k
We Built for Predictability; The Workloads Didn’t Care
stahnma
0
140
Embedded SREの終わりを設計する 「なんとなく」から計画的な自立支援へ
sansantech
PRO
3
2.5k
Azure Durable Functions で作った NL2SQL Agent の精度向上に取り組んだ話/jat08
thara0402
0
190
2026年、サーバーレスの現在地 -「制約と戦う技術」から「当たり前の実行基盤」へ- /serverless2026
slsops
2
250
予期せぬコストの急増を障害のように扱う――「コスト版ポストモーテム」の導入とその後の改善
muziyoshiz
1
1.9k
SREじゃなかった僕らがenablingを通じて「SRE実践者」になるまでのリアル / SRE Kaigi 2026
aeonpeople
6
2.4k
Greatest Disaster Hits in Web Performance
guaca
0
250
[CV勉強会@関東 World Model 読み会] Orbis: Overcoming Challenges of Long-Horizon Prediction in Driving World Models (Mousakhan+, NeurIPS 2025)
abemii
0
140
Featured
See All Featured
Crafting Experiences
bethany
1
49
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.4k
jQuery: Nuts, Bolts and Bling
dougneiner
65
8.4k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
141
34k
Practical Orchestrator
shlominoach
191
11k
Raft: Consensus for Rubyists
vanstee
141
7.3k
A Guide to Academic Writing Using Generative AI - A Workshop
ks91
PRO
0
210
Making the Leap to Tech Lead
cromwellryan
135
9.7k
Marketing Yourself as an Engineer | Alaka | Gurzu
gurzu
0
130
Ruling the World: When Life Gets Gamed
codingconduct
0
140
Discover your Explorer Soul
emna__ayadi
2
1.1k
Noah Learner - AI + Me: how we built a GSC Bulk Export data pipeline
techseoconnect
PRO
0
110
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