Repository files navigation

• Introduction
• Dev Productivity
  • Use Docker and stop hearing "Works on my machine!"
  • Ensure reproducibility
  • VS Code productivity tips (or "Know Your IDE")
• Variables
  • Variable names should reveal intent
  • Use meaningful and pronounceable variable names
  • Use the same vocabulary for the same type of variable
  • Avoid magic numbers and magic strings
  • Use variables to keep code "DRY" ("Don't Repeat Yourself")
  • Use explanatory variables
  • Avoid mental mapping
  • Don't add unneeded context
• Dispensables
  • Avoid comments
  • Remove dead code
  • Avoid print statements (even glorified print statements such as df.head(), df.describe(), df.plot())
• Functions
  • Use functions to keep code "DRY"
  • Functions should do one thing
  • Functions should only be one level of abstraction
  • Function names should say what they do
  • Use type hints to improve readability
  • Avoid side effects
  • Avoid unexpected side effects on values passed as function parameters
  • Function arguments (2 or fewer ideally)
  • Use default arguments instead of short circuiting or conditionals
  • Don't use flags as function parameters
• Design
  • Avoid exposing your internals (Keep implementation details hidden)

Clean code practices (fromClean Code andRefactoring) adapted for machine learning / data science workflows in Python. This is not a style guide. It's a guide to producingreadable, reusable, and refactorable software.

If you’ve tried your hand at machine learning or data science, you would know that code can get messy, quickly.

Unclean code adds to complexity by making code difficult to read and modify. As a consequence, changing code to respond to business needs becomes increasingly difficult, and sometimes even impossible. This has been written about extensively in several languages, and even in Python (e.g. Clean Code, Refactoring, clean-code-python). In this repo, we have adapted these principles for data science / machine learning codebases.

Targets Python3.7+

Inspired byclean-code-javascript and forked fromclean-code-python.

By James O Coplien (Source: Foreword of Clean Code (Robert C. Martin))

In about 1951, a quality approach called Total Productive Maintenance (TPM) came on the Japanese scene. Its focus is on maintenance rather than on production. One of the major pillars of TPM is the set of so-called 5S principles:

• Seiri, or organization (thinksort in English). Knowing where things are—using approaches such as suitable naming—is crucial.
• Seiton, or tidiness (thinksystematize in English). There is an old American saying: A place for everything, and everything in its place. A piece of code should be where you expect to find it—and, if not, you should re-factor to get it there.
• Seiso, or cleaning (thinkshine in English): Keep the workplace free of hanging wires, grease, scraps, and waste. What do the authors here say about littering your code with comments and commented-out code lines that capture history or wishes for the future? Get rid of them.
• Seiketsu, orstandardization: The group agrees about how to keep the workplace clean. Have a consistent coding style and set of practices within the group.
• Shutsuke, or discipline (self-discipline). This means having the discipline to follow the practices and to frequently reflect on one’s work and be willing to change.

If you'd like to try out these practices, we've created arefactoring exercise which you can follow along. Starting witha jupyter notebook with many code smells, you can apply these clean code principles and refactor it to be readable and maintainable. The sample final solution can be found insrc/train.py.