041 RR Code Metrics with Bryan Helmkamp

    0
    553

    01:10 – Bryan Helmkamp Introduction

    02:54 – Code Metrics

    • Code Coverage
    • Static Analysis

    04:24 – Why should you be looking at metrics?

    • Challenge the way you think about code
    • Start conversations within the team

    09:14 – Ruby Rogues Issues with Metrics

    13:27 – David Chelimsky's RubyConf Talk

    14:18 – Duplication in Controllers

    • Rails' Scaffolding

    17:03 – Code Complexity vs Duplication

    • Example: Code Climate
    • Flog
    • Ryan Davis
    • ABC Metric (Assignments, Branches, Conditions)

    19:17 – Aggregated Metric Examples

    • McCabe/Cyclomatic Complexity
    • Saikuro

    20:58 – Roodi

    • “Metrics Driven Development”

    23:06 – Composition / Composed Method Pattern

    • “Is all the code in the method at the same level of abstraction?”

    26:00 – Too Many Methods / Instance Variables?

    26:45 – Code Smell

    28:35 – Programming Style in Metrics

    31:27 – Tools for Detecting Immutability Violations

    32:00 – Tracking Code Metrics

    35:11 – Other Metrics

    37:20 – Measuring Test Complexity

    37:56 – Test Coverage Tools

    38:51 – Metrics Fitting Into Agile Team Process

    • Github Style
    • Retrospectives
    • Brown Bag Lunches
    • Group Refactoring Sessions

    42:00 – Downside of Metrics on a Team

    • Git Blame
    • Similar to Past: Unit Testing
    • Measuring Actual Cost of Code Problems: aka Technical Debt
    • Sonar

    45:12 – Organizational Uptake of Metrics

    48:00 – Metrics and Money

    50:34 – Behavioral Metrics

    • Time Spent on Problems
    • Proportional Investment

    53:02 – Custom or Idiosyncratic Metrics for Teams

    • Goal-Directed Metric