A Quant Developer’s Workflow for Environments, Git, and Library Changes
Summary
This tutorial surveys a practical development setup for quantitative programming: code editors, command line terminals, isolated language and library environments, Git version control, repositories, and cloud machines. Its core advice is to choose tools by the functions they provide and isolate each project’s dependencies so that updates for one project do not disrupt another. It gives Conda as an example for managing Python versions and libraries, and describes using Git to save snapshots, branch work, track changes, and collaborate.
The worked example modifies a chart title in the open source pyfolio library, installs the local development version, checks the changed file, and records the modification in Git. This illustrates a small contribution workflow, not a trading method or a benchmark of development tools. The article is oriented around particular software and commands, and it does not provide a general installation manual; readers would need to check current tool documentation because versions and project availability can change.
Key ideas
- Separate development environments help keep project-specific interpreter and library versions from interfering with one another.
- Git records changes over time and supports recovery, parallel development, and collaboration.
- The example workflow edits an open source performance-reporting library, installs the local version, and commits the change.
- Tool choice is framed as a matter of useful functionality and developer preference, and the tutorial’s specific software details may age.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.