By
Download on the App Store

episodes

  • Get out of Technical Debt Now!
    Technical debt is stuff that gets left behind during a project: postponed documentation, unwritten tests, unfixed "TODO" notes throughout your code, and other workarounds you promise to do to "later". Like financial debt, unpaid technical debt accrues interest until you go bankrupt. Software projects start out fun, but often accumulate technical debt that drains project resources and makes developers miserable.
    In this session, you'll learn:
    * How to work debt payments into projects, and show the value of this unseen work
    * How to tell good debt from bad
    * Where to start correcting a debt-ridden project
    * Automated tools for measuring and tracking your debt level
    * Habits to develop to keep debt to a minimum
    * How to keep the quest for perfection from causing paralysis
    43 min
  • Lint
    Now that perl's Lint has support for plugins, I'd like to publicize that a bit and hopefully demystisize the process of writing lint detectors a bit.
    Through the use of plugins for B::Lint and Perl::Critic, programmers can add warnings and other validation. I'll demonstrate how to add create new warnings to flag bad code. There'll be a breezy tour of the optree using B::Concise and how to match bad stuff.
    12 min
  • How Perl::Critic Facilitates Code Best Practices
    Damian Conway's book "Perl Best Practices" has sparked a revolution in coding style among CPAN developers. Even before that book, many of those developers have wanted a way to judge whether their code conforms with a selection of best practices, hence modules like Perl::Tidy, B::Lint and even "use strict". Perl::Critic is a new module which strives to be a powerful and flexible tool to judge code against a user-selected array of "Policy" modules. Example policies include "CodeLayout::ProhibitHardTabs" and "TestingAndDebugging::RequireUseStrict". As of v0.15, we have implemented 70 policies, most of which derive from the 256 recommendations made by Conway. The API uses Module::Pluggable to enable third-parties to easily add more policies. A separate Test::Perl::Critic module makes it easy to confirm that your code is still in compliance with your established policies.
    In this presentation, I will present Perl::Critic's features and demonstrate how you can start using it against your own code.
    29 min