talk-railsconf-keynote-justin-searls#feedback-loops-and-thinking-about-thinkingAt 7:20 feedback loops and thinking about thinking. talk-railsconf-keynote-justin-searls#feedback-loops-and-thinking-about-thinking
At 13:40 "discovery testing" - freaking big problems down into more manageable ones
At 14:50 interesting file names for services
At 18 it started with realizing that programs are directed graphs
At 19 I want to express all of my programs as a tree, not just as a directed graph
At 21:30 desire to continuously improve breeds inconsistency, which is incidental complexity
At 24:40 estimates
talk-railsconf-keynote-justin-searls#using-mocking-to-find-interface1At 2830 the top of the tree is a delegator that doesn't do very much. He figures out what the sub pieces should do by determining what he wishes other pieces of code would do for him. He does that by mocking them while creating talk-railsconf-keynote-justin-searls#using-mocking-to-find-interface1
talk-railsconf-keynote-justin-searls#docs-and-tests-to-help-future-self1At 3010 he tried to make good tests more tests, and documentation to help his future self, but instead it ended up tying the hands of his future self because the features of had to change more tests and change more documentation. talk-railsconf-keynote-justin-searls#docs-and-tests-to-help-future-self1
talk-railsconf-keynote-justin-searls#disposable-code1At 3120 he talks about making his code disposable talk-railsconf-keynote-justin-searls#disposable-code1
At 3215 code reuse isn't free
At 3610 wrap your dependencies
At 42 introspective developers have a framework for evaluating new ideas