edit-article

Article Description: [66:00]VIDEO pt 1/2 - By DHH - addresses the topics of ...

Chapter ID/Name:

Status: Write Writing Written

Add Photo:

Owner ID:

Content: use HTML Edit Content <h1 style="text-align: center;">Rails Conference Keynote by DHH</h1> <h2>[WHAT]</h2> <ol> <li>] <a href="http://www.justin.tv/confreaks/b/522089408" target="_blank">http://www.justin.tv/confreaks/b/522089408</a>&nbsp;- [66:00] David Heinemeier Hansson(DHH) Creator of Ruby on Rails and partner at Basecamp. Part 1 of 2 of keynote, *VIDEO does not start until 11:00 minute mark, part 2 of</li> <li>] <a href="http://www.justin.tv/confreaks/b/522101045" target="_blank">http://www.justin.tv/confreaks/b/522101045</a>&nbsp;- part 2</li> <li>]&nbsp;src =hn&nbsp; comments <a href="https://news.ycombinator.com/item?id=7629212" target="_blank">https://news.ycombinator.com/item?id=7629212</a></li> </ol> <h2>[WHY]</h2> <ol> <li>]&nbsp;got started late in programming (20's), after starting 3 years later, rails was built</li> <li>] tried to learn programming as a kid several times, gave up b/c it was 'too hard', it was hard</li> <li>] math was not a strong suit for him, english was</li> <li>] realization that he was not a programmer,&nbsp;ala Linus Torvalds&nbsp;</li> <li>] realization that he (like many) was a builder of information systems, not likely to ever be a programmer</li> <li>] programming, computer science is the holy grail</li> <li>] programming as truth, hard fact UNLIKE 17th century french poetry which is open to 1000 different interpretations</li> <li>] BUT programming is often subject to interpretation, EXAMPLE of trying to understand someone elses code</li> <li>] law of demeter - pseudoscience - collection of beliefs where people believe they are doing science but they are not actually doing science</li> <li>] compares to 'diet science'</li> <li>]</li> <li>] lots of people willing to tell you 'what' to do,</li> <li>]</li> <li>] TDD -&nbsp;worst of all</li> <li>] tests first, TD design, felt like what i was supposed to do, write all tests first then write code,</li> <li>] dirty code looked better</li> <li>[40:00] code examples</li> <li>] gospel of TDD is that anything that is 'easier to test', is better, IF&nbsp; you cant test it easily ...</li> <li>]</li> </ol> <h2>[WHERE]</h2> <ol> <li>]</li> </ol> <h2>[WHEN]</h2> <ol> <li>]</li> </ol> <h2>[EXAMPLE]</h2> <ol> <li>]</li> </ol> <h2>[HOW-TO]</h2> <ol> <li>]</li> </ol> <h2>[REFERENCE]</h2> <ol> <li>]</li> </ol> <h1 style="text-align: center;">&nbsp;</h1>