thoughtbot Build Phase #33
phonegap/ios-sim · GitHub
Command-line application launcher for the iOS Simulator
thoughtbot Learn : iOS on Rails (Beta): a book by thoughtbot
This book is for a developer who wants to build an iOS application with a Rails backend
Keybase
node-keybase
nodeを入れないといけないのが不満
dblock/obcd · GitHub
Deal with obsessive compulsive issues of programmers in Objective-C
HeaderStyle: Check header style on top of .h, .m and .pch files.
bbatsov/rubocop · GitHub
A Ruby static code analyzer, based on the community Ruby style guide
objClean
You can choose which rules you want to apply to your projec
Boundaries — Destroy All Software Talks
https://www.destroyallsoftware.com/talks/boundaries
initの中でnilチェックをしたくない
Objective-cの作法の間違い
tv show
rasberry pi
twitter feed
homebrew
rubygem
npm
node
keybase
ios sim
simulator
weekly
obj c file
xcode5.1
broke
by weekly
run xcode project from vim
node package manager
keybase
main argument
keybase node
should available homebrew macport
not npm
cool thing
obcd
rubocop
fix comment
syntax
lint
objective clean
code review
checking line
pull request
rather care about texture
do you read
2 slashes
semi colon
ios and rails
dyana jessy
book
learn about
26 dollar
source code
github repo
both
learn something new
ios rails .net
dont wanna check nil in initializers
nib
not property in init
jack stockholm
pros cons
using accessors
dont know realistically possible
trigger kvo
side effect
register
reference to object
setting up kvo
subclass object
override init
inherit property
super init
bad idea
using accessor
mention
dealloc
arc
release everything
message zombie
couple of time
this fields
verbal
dealloc kvo
arc change rule
mental model
completely wrong
challenge assumptions
stupid checking code
not cheking
side effect
use accessors
only use accessors inside init
self nil
skip it
side effect setter
one side
other side
should only use ivars
his argument
kvo stuff
side effect
using accessor
set foo
overridden
internal mutation
concrete example
reload data
dependent
initializer
ui table view
make sense
to be aware of
right order
side effect setters
cells
unexpected
manually
crazy
manually setting
main problem
subclass my class
super init
my init
side effect
keep saying side effect
cant guarantee
minimize
easier inplicit
self underscore foo
nil
doesnt really make sense
argue about accessor
ivar
conditional check
idealistic
functional programming
dont like side effect
exception lazy initialization
totally understand
table view
make sense
set data source
guessing
consistency
old data
no longer exist
delete cell
necessary
change datasource
reload data
different
ui
haskel
functional call
side effect
forced by language
ui layer ios
have to happen
external view
can limit side effect
prefix
subclass
same side effect
reload data
representation
class knows
index just deleted
view
data representation
view representation
point
facing user
waiting human
lot make sense
mutate object
supecial exception
ui layer
unique to view
ios app
client base
messy interaction
bad input
correctness
interaction
messy
intersting
treat ui
functional programming concept
safer
make sense
boundaries
idea
cool thing
object oriented method
wrote app
commandline utility
shows up essentially ui layer
fanctional concept
immutability
large scale
