DestroyAllSoftware Screencasts for Serious Developers

Discussion in 'E-Books & Tutorials' started by BetterRhyme, Apr 19, 2012.

  1. BetterRhyme

    BetterRhyme Guest

    DestroyAllSoftware Screencasts for Serious Developers
    English | Mov | 1440x900 | 30fps | Mp3 128kbps 44100hz | 602mb
    Genre: e-learning

    Just watch the example screencast and you see what I mean. However, what made me really sign up was the perfect mix of tools, development and programming:it has a lot of Ruby, Unix, Vi(m), TDD, and Git. So yes “for serious developers”.

    Orignal Provider -->

    0001 - Statistics Over Git Repositories

    We'll use the shell and the git command line tools to iterate over revisions, computing a statistic for each revision. Initially, it'll be a one-liner at the prompt. Then we'll promote it to a full script, refactor it, and add some more features.

    0002 - How and Why to Avoid Nil

    We'll look at nil from many angles. Why do nils show up in your programs? What kinds of problems can they cause when they get out of control? How can we design our systems to fail loudly when unexpected nils exist and, more importantly, to avoid the introduction of nils entirely? This screencast uses Ruby, but the techniques apply in any language.

    0003 - Building RSpec from Scratch

    RSpec has lured many programmers into the Ruby world with its beautiful syntax. For some, its working remain a mystery. Let's dispel that. We'll build some of RSpec's basic syntax from scratch, test driving it using Test::Unit. This is done in Ruby, of course. Basic Ruby knowledge will definitely help.

    0004 - Source Code History Integrity

    Source code history is a touchy topic. Should we ever edit history? Is it safe? We'll look at what can go wrong when editing history, and how to avoid the potential problems. We'll also briefly talk about the Mercurial and Git communities. Warning: there's some editorializing!

    0005 - Extracting Domain Objects
    In modern web frameworks, it's easy to extend model and controller objects over and over again, leaving you with huge, unwieldy objects. To avoid this, you can extract small pieces into their own classes. This has many benefits, such as: much faster test execution, naming concepts in the system that were previously implicit, and adding explicit abstraction layers. We'll look at an example from Destroy All Software itself, a Rails app, and pull a piece of model logic embedded in a controller out into its own class with isolated tests.



  2. VIRUS_666

    VIRUS_666 New Member

    Mar 4, 2012
    Likes Received:
    Trophy Points:
    many thanks to u ....

Share This Page