thoughtbot Build Phase #64
64: The Realities of Being Batman | Build Phase
batman, joker
singleton
threading
disk access
dependency injection
internal state hard to test
batman
money
martial arts
that strong
specialization
big problem
football carreer
conclision
ashamelessly
catch criminal
cop
joker
idiots
coming
military
not too different
prison
incredibly
normal people
dc universe
precedence
favorite thing
more us cities
wyomi
build world
super power
good job
follow up
queue cache
how to test
disk access
callback
timing
instead of mock
mimics
stub out
tend to
clumsy
concises
have to
network stack
completion block
invocation
pointer
fairy ugly confusing
similar
concrete
same interface
thin wrapper
mutable array
disk access
cache itself
additinal method
fake
another corner
dependency injection
bastly simplify
real world
identical
DI
singleton
threading
disk access
dependency injection
singleton constructor
ivar exist
lazy initialization
not using
passing
anything
declair
appcode
suppose
downside
init method
singleton
just problem
could also
category
weird about
makes me feel
swift
optional mocks
swizzeling
doesnt work
swift strong type
extension
initializer
really like code
stack
pararrel
takes operation
cache
next operation
mutable array
queue
grab
cache
completion
operation
request
network client
completion block
remove operation
execute request
no request left cache stop
check internal array
cache is nil
completion block
very thin class
interface
flash queue
suncronyze
edge case
own internal queue
cache
network vlient
double up
simple boolean
continue
boolean false
flash operation
add request
same queue
fake cache
instanciate
first object
hard thing
complete flash
dont have to worry about time
locking
essentially
hard to test
control
tell it
verify other state
notification
reacheability
very simple
syncronize queue
only care reacheable unreacheable
who cares
not huge deal
get access
add new items
pretty close
really impressed
tested
design
wasnt testing
lower level
one point
execute request
internal state
error set it
internal state
hard to see edge case
flip back
impossible test
now what is this
really hard to test
what if
describe
way
reason
keeps going
exit point
easily
move completion
really clean way
mind blowing
chain reaction
holyshit
internal state hard to test
really did improve
really does
took note
network response
not hooked into app
self contained
generic
look at this
each object so focused
prefixes
notable exception
hook into
super generalize
threading disk access
how do you test
blow my mind
interface out protocol
awesome tradeoff
using protocol
moving object
polymorphism
lot of work
something about writing
give me some class
not gonna happen
cache protocol
fake cache
disk cache
in theory
icloud documents
dropbox
add remove operation
even more transparent with swift
wakky id
dont have to
concrete class
type is protocol
metaphor
could do
hire
a b or c
specific implementer
nice name
prefix request cache
ugly name
descriptive
never had to deal with
queue
this is a request queue
metaphor
really nice
protocols
dont feel like
objective c
coco
delegates
nice way to think about
swift
last project
guarantee
entire network
simplify everything
ironically
stupid counter
literally ten lines of code
simple
simplicity
mock
figure out
stupid counter
dead simple
honestly
really impress
improve my code
specifically
looking for chance
instead of mocking
overuse
trouble
looking forward
normal toolkit
new conference
funswift conference
functional
kickstarter
one day
crazy
free conference
brian
jon galager
living new york
saturday dec 6
brooklin
topics
technical conf
