thoughtbot Build Phase #52
Error handling
Api client
lots of duplication
duplication in test
dci
mvc
error handling
alert user
networking layer
password
if they dont have network connectivity
api client
glue layer
model factory
parse json
transform
outside 200 range
lot of duplication
request
parase json
handle erors
any time succesa block
completion block
refactoring
duplication in test as well
perform request with passing block
deleted 25 tests
much nicer
endpoint specific category
comments
authentication
api client category
clear place
specific place
way we ended up
id object
casted
ns array
little clarity
request succeed
view layer
view model layer
wrong user name
bad request
success block
functional difference
post notification
ns error
stack in application view controller
everything contain
error notification
transformer class
ui alert view
surver has to provide
long process
exactly map error
match up error status code
outside of http
error 37
additional information
build phase twitter
what github do
makes most sense
implement our end
get back message
little work
iteratively
messaging specific places
focus messaging
as clear as possible
server side
server send back
lot more sense
change copy
send up request header
rails easily
localize error message
back down
more powerful
localize
3 error cases
generic
json parsing
reachability
modify header
straight forward
locale
more often
bottom
view controller stack
tell application view controller
child view
status bar
mvvm
persistence
coredata stack
biggest thing
validating assumptions
little experience
validated
snag
work to do
networking
sticking point
using more protocol
view model
super classes
generic pattern
dci
different from mvc
mvc buckets
objects
role
objective c protocol
concrete type
need
mvc
good beginners cource
coco
wwdc
application architecture
good talk
disappointed
great stuff
pull objects
delegate
separate concern
disappoint
no advanced talk
really disappointed
community
conversation
mvc
breaking concern
ambiguity
what is controller
user controller
constantly
mvc
production scale
deletion
last show
ten times easier
far more robist
magically
were correct
architecture
more complex
fundamentally wrong
mvvm
still this architecture missing
reactive coco
data binding
hungry
