What Developing With Ruby Can Teach Us About Developing Ruby
Published on Nov 19, 2015
No Description
MORE DECKS TO EXPLORE
PRESENTATION OUTLINE
...or massively parallel hardware...
Photo by NASA Goddard Space Flight Center
...or control of a massive botnet...
Photo by Patrick Hoesly
they produce words and designs enthusiastically
Photo by Free HDR Photos - www.freestock.ca
but randomly.
Photo by Christina Ann VanMeter
"furu ike ya; kawazu tobikomu; mizu no oto."—basho
Photo by Ben Cooper
"not even wrong"
and works that are...
we could use them to regenerate the works of shakespeare
Photo by rishibando
or philip k dick
Photo by Adam Crowe
or antoni gaudí i cornet
Photo by pasotraspaso
why won't this work?
obviously,
there aren't enough typewriters
but typewriters aren't the point at all.
Untitled Slide
there will always be faster typewriters
and smarter monkeys
Photo by Sean Castor
how do we find shakespeare?
Photo by Natalia Romay
from gaudí?
how do we distinguish cheval(*)...
"that sounds vaguely important"—george carlin
Photo by Stuck in Customs
ferdinand cheval
How do we distinguish the works of
antoni gaudí?
from those of
(a/k/a the "spam vs. ham" problem)
Photo by hermitsmoores
this is the only problem.
recognizing successful output:
so, ruby.
monkeys with typewriters
if you take the red pill, you discover that we're just
"smarter monkeys"
if we ask companies what they need, they reply:
"better typewriters"
if we ask programmers what they need, they reply:
what ruby programmers do?
what do we learn from
social coders
ruby programmers are
conclusion 1:
"society trumps speed and smarts"
ruby should optimize for sharing at scale.
Ruby programmers should optimize for sharing at scale
Photo by thatautguy
our practices flow from tests:
conclusion 2:
"testing trumps typing"
x is more important than y:
Photo by Leo Reynolds
what we learn:
society and testing matter.
