Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
NYPL Labs @ Wiki ♡ Maps 2015
Search
Mauricio Giraldo
February 05, 2015
Technology
960
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
NYPL Labs @ Wiki ♡ Maps 2015
NYPL Labs @ Wiki ♡ Maps 2015
Helsinki, Finland, February 5, 2015
Mauricio Giraldo
February 05, 2015
More Decks by Mauricio Giraldo
See All by Mauricio Giraldo
Aereo: An experimental bird’s eye view of the digital collections from the State Library of New South Wales
mgiraldo
0
390
From food to buildings and beyond: what happens when a library opens its digital collections to human-computer collaboration
mgiraldo
2
230
Aprendizajes de trabajo en bibliotecas digitales
mgiraldo
0
180
building inspector
mgiraldo
0
120
Talk at the NYU ITP Data Art class / Spring 2017
mgiraldo
0
200
Humanidades Digitales en los laboratorios de la Biblioteca Pública de New York
mgiraldo
0
130
FOSS4G Nara/Tokyo
mgiraldo
0
2.1k
Human-Computer Collaboration at NYPL Labs
mgiraldo
2
510
NYPL Labs @ Eyeo Festival 2015
mgiraldo
1
800
Other Decks in Technology
See All in Technology
Slack上でインフラをトラブルシュートする! Agentic Platform Engineeringの第一歩
teru0x1
5
1.8k
Claude Codeを「使うほど育つ」AI秘書にするノウハウ
minorun365
PRO
31
27k
Goodbye ShellScript, Hello File-based App
shunsock
0
170
10Xに技術的負債をもたらした「2つの境界の歪み」その構造と解消への営み
10xinc
0
2.1k
技術的負債から考える、AI時代のエンジニアリング投資 — ビズリーチの技術的負債と向き合った経験から、変更し続けられるソフトウェアを考える/ technical-debt-con2026
visional_engineering_and_design
4
3.2k
え、こんなに早く改修できるの?──新人エンジニアとスクラムマスターの2人が語る、AI×アジャイル開発の現場
ysasago
2
440
AI de Idea
kawaguti
PRO
2
120
HHKBエバンジェリストになる方法
941
0
110
What the customer really needed
kawaguti
PRO
3
210
顧客に向き合う開発組織へ。リアーキテクチャとフィーチャーチーム化で挑む組織改革
safie
0
2.1k
研究開発部の紹介 / Sansan R&D Profile
sansan33
PRO
5
25k
山手線を徒歩で一周してわかった、 位置情報アプリは「足」が最強のデバッガー
hinakko
0
160
Featured
See All Featured
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
230
23k
How to Build an AI Search Optimization Roadmap - Criteria and Steps to Take #SEOIRL
aleyda
1
2.2k
Intergalactic Javascript Robots from Outer Space
tanoku
273
27k
It's Worth the Effort
3n
188
29k
Agile Actions for Facilitating Distributed Teams - ADO2019
mkilby
0
280
Technical Leadership for Architectural Decision Making
baasie
3
570
Speed Design
sergeychernyshev
33
2.1k
Exploring anti-patterns in Rails
aemeredith
4
510
Navigating Team Friction
lara
192
16k
Accessibility Awareness
sabderemane
1
210
AI: The stuff that nobody shows you
jnunemaker
PRO
10
1k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
32
3k
Transcript
mauricio giraldo arteaga @mgiraldo nypl labs a few things we’ve
learned so far wiki ♥ maps , helsinki, february 2015
hei
my name is mauricio
None
None
NYPL Labs
None
None
None
we’ve been at it for 3+ years
a few things we’ve learned so far
disclaimer
a few things we’ve i’ve learned so far
four things
practical
1
start with a prototype
None
None
None
None
None
None
None
menus.nypl.org
200k dishes in 13k menus
made the case for NYPL Labs
it started with a prototype
None
None
None
None
None
None
None
None
“wouldn’t it be cool if…?”
None
None
None
A FEW DAYS later…
None
None
distill the task to its critical components
prototypes help determine viability
prototypes help communicate the idea
–@mikeindustries “a prototype is worth a thousand meetings”
None
None
“great! it’s just polish now, right?”
2
“polish” takes (a lot of) time
None
None
3 months later…* *REAL NUMBER
None
None
stereo.nypl.org
None
None
None
still, three months is not that long when you’re used
to year-long projects
…and polish is good
LATER that day at 1:00AM…
None
None
so far 47,000 images created
another “smaller” example
None
None
None
None
None
None
took about 2 weeks
spacetime.nypl.org
A FEW HOURS later…
None
a good problem to have?
also, polish can wait
None
None
could use a redesign
None
None
None
1.1 million more dishes and that’s even though we’re not
scanning menus as often
curatingmenus.org by @katie_rawson and @trevormunoz
@_BadTaste_ by @bibliotechy
polish works
“polish” is design
…but it takes time
“ok… so i just factor this in my planning”
3
everything takes longer than anticipated
people are bad at making estimates* *S. Grimstada, M. Jørgensena,
2007; I. Newby-Clark, M. Ross, R. Buehler, D. Koehler, D. Griffin, 2007; V. Mahnič, T. Hovelja, 2012; and more…
(yeah, even in “agile development”)
people cannot estimate what they have not done
–@jasonfried “planning is guessing”
legacy website redesign ca. 2005
None
None
None
“let’s take 90 days to redesign this”
(huge red flag)
there are always surprises usually not the good kind of
surprises
None
None
None
None
“we have to have this feature”
18 months later…
None
None
None
None
None
None
None
None
digitalcollections.nypl.org
start with a scope or a deadline
…but not both
don’t take too long
–@schuyler “if you're proud of your code you waited too
long to ship it”
…but take as long as it needs
…and prepare for surprises
4
hackathons are starting points
None
None
year
street names year
use type street names year
use type street names name year
material use type street names name year
material use type street names name class year
material use type street names address name class year
material use type street names address floors name class year
material use type street names address floors name class year
skylights
material use type street names address floors name class year
skylights backyards
material use type street names address floors name class geo
location year skylights backyards
footprint material use type street names address floors name class
geo location year skylights backyards
footprint material use type street names address floors name class
geo location year skylights backyards
None
“wouldn’t it be cool if…?”
None
None
can we automate this?
None
None
None
None
None
None
None
None
None
FIVE WEEKS later…
None
github.com/NYPL/map-vectorizer
None
None
~80k building footprints in a day instead of years
None
this resulted in a new question
“is the output any good?”
…so we did a prototype
None
None
None
None
buildinginspector.nypl.org
2 MONTHS later…
None
None
None
None
84%: YES 7%: FIX or about 91% good enough
we ♥ our contributors
we ♥ our contributors
…so we did more prototypes!
None
None
1 million classifications so far! ~18 months since launch
None
None
None
None
…and it all started in a hackathon
recap
None
start with a prototype
start with a prototype polish takes time
start with a prototype polish takes time everything takes longer
than anticipated
start with a prototype polish takes time everything takes longer
than anticipated hackathons are starting points
thank you ♥ images from: NYPL digital collections - Wikimedia
Commons - Flickr user wallyg - Giphy - John Resig - Peter Leonard mauricio giraldo arteaga @mgiraldo nypl labs