thoughtbot Build Phase #51
Waiting For the Beer Endorsements
Upcase.com
Uber
cheaper, safe
ZeroPush - Simple Apple Push Notifications for Developers
自分でやると3日かかるが、5分でできる
ns baby sitter
ns george michael
upcase com
tdd
mvvm
enthusiastic answer
no longer allow to go out
commutter train
not gonna drink
uber cheaper
downtown boston
16 dollars
9 dollars
dont have to walk
25%off
boston thing
taxi
ticket
have to schedule cab
friday night
cabs everywhere
lunch time
nothing better than
getting up
safest
cheapest
win win
not drive drink
push notification
swap proxy
invoice
3 days
creepy weird
replace
app delegate
proxy object
double delegate proxy
automatic
super invasive
dont mess app delegate
prefix make sense
conflicting
setup process
expect to happen
freaking method
api key
token data back
nice little decoding
string from token data
nice
5min vs 3days
painless to install
easier to test
controling behavior
better experience
requirement
android push
heroku add on
click
upload certs done
protocol
ios community
obj c community
briefly
end of last week
concrete
inheritance
foundation
uikit
protocol base
super flexible
subclass
delegate
system expect
transition
not just delegate
transition coordinator
everything good
two things last week
organization
client perspective
do have
author protocol
feature
avator
agency
current user profile
edit your profile
commit
mutating
current user
core data
edit profile
care about authors
duplicating
embedding
container vc
spray it
button to edit
child vc
normal profile
id author
content provider
not in code yet
challenge
duplication
basic view controller
because
update
fetch that
property
update themself
implement
api client
user profile
current user
representation
organization
i see
different end point
network action
condition
class change
what we really need
what kind object
tony doing swift
more generic
simplified
fetch author
completion
endpoint
kind of thing
creating more protocol
fetchable
deletable
updatable
most duplication
common action
user know api endpoint
api standpoint
super nice
lose type safety
generic
returned type
endpoint
type return
networking
good type support
specific methods
returned
most constraint by language
swift
function
not actually getting
does feel nicer
what is gonna be returned
safety
bigger problem
refactoring
duplication
completion block
duplicated block
adding error handling
put in
crazy
refactoring
side effect
type
default block
standarize
block
different
model object
boolean
nothing
void blocks
ignore
explicitly
refactor
stub out
typing block manually
memory
definition
type def
bad access
forcing block
wromg type
higher level protocol
server object
why not just subclass
not ok with superclass
cleaner
could do thing
fetcheable
updatable
define
remote object
nicer
inheritance without actual implementation
making change harder
move concept
all of a sudden
bunch
bug in this specific subclass
base class
end up
swithing
possible subclass
top of method
bottom
another
big issue
have to internal private
be part of implementation
subclass have to know
internal
post read write
actively
subclass
feel like
redeclairing
coupling yourself
internal
impossible
based only on public interface
cant see it
horrible hacks
compatibility
every release
twitter
dont know coco
foundation
design
mac app
used be currently is
actively
swizzeling
undo
broke
undoing
specific application
who swizzle this
ns baby sitter
ns george michael
jumping back
happens a lot
baggage
weird
interface
implement
completely lost
baggage
legacy
re implement
if there is diplication
probably object you can extract
transform
specific class
takes name
accidentally open skype
slack
