thoughtbot Build Phase #50

The One Where They Do The 50th Show

MVVM
ActionSheet transport mechanism

KVO
responder change

easiest code is always best code

movie - Airplane and Zero Hour Mashup - YouTube

---

upcase com
skype
not feeling well
didnt eat coffee
never think about it
have a foot
not body
good point
1 year anniversary no
last month
second episode
buildpack
heroku
whats up
nothing
had good week
product
literally nothing
good job
incredibly simple
final iteration
close to
too much magic
view model
communication
conversation
post
comment
detail
mvvm
individual cells
detail view
another table view
deletion
not using swipe
button
hidden logic
different configuration
tap delete
collection post
send responder change
message
back to view controller
delegate
controller
view model
tap happen
back to view controller
actual request
pass completion block
crap
whole thing one feature
decorate model
hopping
animating
kvo count
lot of headach
more confusing
three big issue
work for deletion
need to delete comment
view controller stack
no idea
weird
propagating
literally removing
gets released
in json
persisting deletion
action sheet
view controller
third thing
expandability
duplicate all logic
type checking
why started refactoring
two architecture
execution
slightly different
ended up
index path
delete yourself
moving from the cell
animating
how move
deleted boolean
kvo friendly
mark it as deleted
complicated
concept
most complicated
new system
moving from
less complext
still complex
test
partially safe
acceptance test
bunch of unit test
individual object
stability
problem glue layer
numbers of bugs
integration test
new architecture
no provide color
not removing system
low level
post view controller
moving
deleting
detail view model
split
move logic post detail view model
ask for
ui alert view
didnt realize
knows about post
deletion
action sheet
transportation mechanism
self window
show category
shared application
will work
weird presenting
complexity
action sheet popups
network request
boolean post
deletion
propagated
inside cell
kvo deleted
responder change
main table view get message
complicated
magicky
responder
index path
post cell view
persistence layer
in memory
propagate
fetch
talk myself
understand
little weird
didnt care about
amazingly simple
super shady code
tags
no view model
dead simple
easiest code is always best code
untestable
github
deletions all of a sudden
need to make
no changes
post detail screen
pop view controller
view will appear
cell deletion
same architecture
post cell view model layer
propagate
same action sheet
conform
content protocol
delete post
delete comment
single model action sheet
so much coupling
view very similar
initial thought
reuse
subtlely different
havent taken advantage of
largely speaking
behavior
swift code come through
json parsing
protocol
global function
idea moving away
standalone method
common action
functional approach
container object
global contain
collection
wired
much more flexible
implement
collection
array dictionary
most interesting
model object
very basic
same operation
unflag
six methods
extend idea
actionable content
pass in
config object
know endpoint
type issue
swift generic
wakky
same signiture
all those method same
private helper method
ignore json
check if error
tied to post or comment
argument
dont want to know view model level
how to make request
networking lauer
actual network layer
create json
multiple layer
tiny
network client
api client namespace
server
create post
hands back another post
ugly wrong
callback
moving to protocol
gets weird
passing endpoint
post/comments
handled
comsistent api
http protocol
deleting
updating
happy with
chad pytel
complaining
codebase written
assumption right
true tdd
backwards
dont have a test
almost there
feels awesome
good about mvvm
bunch of benefit
little more cumbersome
10000lines of code
production
250line
should start refactor
still classes
one view model huge
post detail
controller also huge
testable object
unspoken rule
600test
unit test
no class
network activity
50lines
massive
huge
frustration
because of mvvm
periminary test side project
complexity
how do we deal with that
fully
best way
tdd the other day
great way describing
new language
new architecture
every single
responder change
reactive coco
kvo ish thing
declarative
nice
suggestion
personally
swift
head around
crazy cool
json
really wanna learn
back tracking
objective c
chain block
reactive coco
hedius
obj c
swift resemble
15square blaket
air plane
someone twitter
cody coon
zero hour
awesome
almost
funny
amazing
movie
fantastic mash up
flight danger
canadian place
problem
native canadian