Summary
As we build software projects, complexity and technical debt are bound to creep into our code. To counteract these tendencies it is necessary to calculate and track metrics that highlight areas of improvement so that they can be acted on. To aid in identifying areas of your application that are breeding grounds for incidental complexity Anthony Shaw created Wily. In this episode he explains how Wily traverses the history of your repository and computes code complexity metrics over time and how you can use that information to guide your refactoring efforts.
Preface
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With 200 Gbit/s private networking, scalable shared block storage, node balancers, and a 40 Gbit/s public network, all controlled by a brand new API you’ve got everything you need to scale up. Go to pythonpodcast.com/linode to get a $20 credit and launch a new server in under a minute. And don’t forget to thank them for their continued support of this show!
- And to keep track of how your team is progressing on building new features and squashing bugs, you need a project management system designed by software engineers, for software engineers. Clubhouse lets you craft a workflow that fits your style, including per-team tasks, cross-project epics, a large suite of pre-built integrations, and a simple API for crafting your own. Podcast.__init__ listeners get 2 months free on any plan by going to pythonpodcast.com/clubhouse today and signing up for a trial.
- Visit the site to subscribe to the show, sign up for the newsletter, and read the show notes. And if you have any questions, comments, or suggestions I would love to hear them. You can reach me on Twitter at @Podcast__init__ or email hosts@podcastinit.com)
- To help other people find the show please leave a review on iTunes, or Google Play Music, tell your friends and co-workers, and share it on social media.
- Join the community in the new Zulip chat workspace at pythonpodcast.com/chat
- Your host as usual is Tobias Macey and today I’m interviewing Anthony Shaw about Wily, a command-line application for tracking and reporting on complexity of Python tests and applications
Interview
- Introductions
- How did you get introduced to Python?
- Can you start by describing what Wily is and what motivated you to create it?
- What is software complexity and why should developers care about it?
- What are some methods for measuring complexity?
- I know that Python has the McCabe tool, but what other methods are there for determining complexity, both in Python and for other languages?
- What kinds of useful signals can you derive from evaluating historical trends of complexity in a codebase?
- What are some other useful metrics for tracking and maintaining the health of a software project?
- Once you have established the points of complexity in your software, what are some strategies for remediating it?
- What are your favorite tools for refactoring?
- What are some of the aspects of developer-oriented tools that you have found to be most important in your own projects?
- What are your plans for the future of Wily, or any other tools that you have in mind to aid in producing healthy software?
Keep In Touch
- anthonywritescode on GitHub
- @anthonypjshaw on Twitter
- Website
- Medium
Picks
- Tobias
- Anthony
Links
- Wily
- Dimension Data
- Pluralsight
- Real Python
- Seattle
- C#
- Cyclomatic Complexity
- McCabe
- Git
- C
- Assembly
- Halstead
- Radon
- The Zen Of Python
- Vocabulary Metric
- Java
- Anti Patterns
- God Object
- Pre-Commit
- Codeclimate
- Glom
- ASQ
- PyCharm
- PyDocStyle
- PyLint
- Black
- Sunburst Chart
- Visual Studio Code
The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA
Activity