This is code for the book "Fighting Churn With Data: Science and strategy for keeping your customers"; the book serves as a detailed guide to the code. You can get more information at:
This page contains the most up to date setup instructions.
Before you can load data or run the code you have to do some setup on your system. If you never have done this before it may seem like a lot of work, and it kind of is, but this amount of setup is routine when you begin to work with a new technology. These setup instructions should work for most people using either shell Python, Jupyter Notebook, or an IDE, on either Mac or Windows. That said, I must apologize because I am neither an expert in PostgreSQL nor an expert in Python, but I am about to give a lot of advice on how to setup and use these technologies - if you find I am not doing things the best way, or just not how you would have done it, please be patient. If you want to make things better please help help out! :)
WARNING TO PYPI USERS: None of the internal links in this document work on the pypi.org website! To use the internal links in this README view it on github.
Python and PostgreSQL are required.
After the pre-requesisites, you have a choice on how to run the Fighting Churn With Data Code:
pipPython package installation. This is great if you want to run the code and see the output, but you do not want to change the code or run it line by line.
This version of the README if for the the code released with the fightchurn pip package in September 2021. In this version there have been some modifications to the paths described in the first printing of Fighting Churn With Data to enable packaging the Python code. The following two differences summarize the changes:
fight-churn/listings/py/run_churn_list.py: the path in the current code is
fight-churn/data-generation/: the path in the current code is
There is also some extra code from the development phase of the book, which are partially documented on this page.
This project is licensed under the MIT License - see the LICENSE.md file for details.