quattro_4 scribble

scribble 落書き (調べた事をただ落書きする)

thoughtbot Build Phase #59

59: Cognitive Capital | Build Phase

CocoaConf
Seattle
実際行った人に聞いたら会場は空港内だったらしい
Venue / Seattle / CocoaConf 2014: The developer conference for those who think different.
年に何回もあって、会場はいろいろな地域で回っているらしい
3 Tracks
Core speakers give same talk
No recording(ustream)

swiftzのIssueで良く見かける人

fmapとapply
optional value
if let
haskellとの比較、haskellのcompilerでできていること
functorオブジェクト
Functional Swift for dealing with Optional values

voodoo code (おまじない)


cloudy
green
juice
selery
seattle
cocoaconf
first time
three track
150people
cocoaconf boston
5 people
at most 2 track
speaker tour
core speaker give same talk
wasnt good
community
atendee
put stuff after
not necessary
cocoaconf seattle
stupid auto layout tricks
imparative
love to see that
how refactor
uikit team
wwdc
seeing him popup
github threads
repos
he shows up swiftz
asking question
incrediblly smart
maybe genius
functional swift stuff
tony wrote
map bind
json parsing easier cleaner
beacause of way
fmap apply
insanely useful
if let
ugly pattern
clear way
fmap
optional value
pass function
optional
unwrap it
optional none
foo??
empty string
case some value none
switch statement
pattern match in haskell
default case
f fmap
functor
protocol
must implement fmap
type class in haskell
individual protocol
no types
choice
inherit everything
smaller pieces
initializer thing
formatting
string version
optional
multiple
ns url
implicit
objective c
actual option
crashing
printing string
optional
string interpolation
empty string
printing nil
take care
dont wanna print nil nil
fmap
apply
optional function
optional value
return
apply switch optional function
returns
returns none
something
optional functor
here is cool thing
scale
multiple optional
tool string
concatenate slash
parens
close
curried function
just pass host function
url is none
apply
one thing fail
everything fail
safe
type safe
no room error
nice to know
voodoo code
chain these thing together
not returning optional function
fmap return
website format
fmap can always return none
just cascade
one thing return none
propagate through the chain
possible compile
honestly have no idea
haskel compiler can do
how many optional
take so much time
all if let
crazy type safe
fundamental mismatch
absolutely everyday stuff
straight forward
view model
even hours
really felt
run into
felt safe
going back annotation
look at the objective c
compiler
generating swift compatible
cannt figure out
implementation
only has headers
objective c
switch
actual options
complain
implicitly
worst thing ever
reduce runtime error
whole point optional things
having to know
you can
implicitly
function
non optional value
actual option
sdk
basically nothing
notice crashes
access stuff
compiler
right type
prevent
crash
strictly type system
asking for trouble
horrible idea
wrapping option
framework
willingly
blog post
really kind of fun to write
fmap apply
better understanding
weird
one aspect
optional value
functor
haskell
lists in haskell
map is fmap
returns fmap
concept of
fmap something over list
returning new list
same context
fmap with optional
my point is
very nice easy way
concept
fmap really in haskell
prikitive
wakky
writing blog post
defining myself
using myself