10: Isn't the last stage of grieving acceptance?
Giant Robots Smashing Into Other Giant Robots
English - September 03, 2012 00:00 - 43 minutes - 19.7 MB - ★★★★★ - 88 ratingsTechnology Business Entrepreneurship design development software saas business of software app development founders software development business Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Ben Orenstein is joined by Joe Ferris and Mike Burns. They start off with some recommendations for awesome programming books and then dive right in to questions about not following "Tell don't ask" in the view, how MVC and the Single Responsibility Principle may be at odds with "Tell don't ask" in the view, and what a more object oriented approach may look like. They also discuss "Class-oriented programming", what it is, why it is bad, how Rails does it, and how to avoid it. They take a quick trip through Mike's experiments in Ruby and Smalltalk in creating his own programming language. The three codecateers then take on the really important topic of method order and code organization, and finally they reflect on how their code has changed over the years, how no solution is foolproof, and how to move to the next level as a programmer. These topics and more, in this installment of the GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS podcast!
Structure and Interpretation of Computer Programs
MIT course that everyone failed
Growing Object-Oriented Software, Guided by Tests
Clean Code: A Handbook of Agile Software Craftsmanship
Tell Don't Ask
Single Responsibility Principle
Shotgun Surgery
Smalltalk, Squeak
Scala, Play framework
Follow @thoughtbot, @r00k, @joeferris, @mikeburns on twitter.
Ben Orenstein is joined by Joe Ferris and Mike Burns. They start off with some recommendations for awesome programming books and then dive right in to questions about not following "Tell don't ask" in the view, how MVC and the Single Responsibility Principle may be at odds with "Tell don't ask" in the view, and what a more object oriented approach may look like. They also discuss "Class-oriented programming", what it is, why it is bad, how Rails does it, and how to avoid it. They take a quick trip through Mike's experiments in Ruby and Smalltalk in creating his own programming language. The three codecateers then take on the really important topic of method order and code organization, and finally they reflect on how their code has changed over the years, how no solution is foolproof, and how to move to the next level as a programmer. These topics and more, in this installment of the GIANT ROBOTS SMASHING INTO OTHER GIANT ROBOTS podcast!
Structure and Interpretation of Computer Programs
MIT course that everyone failed
Growing Object-Oriented Software, Guided by Tests
Clean Code: A Handbook of Agile Software Craftsmanship
Tell Don't Ask
Single Responsibility Principle
Shotgun Surgery
Smalltalk, Squeak
Scala, Play framework
Follow @thoughtbot, @r00k, @joeferris, @mikeburns on twitter.