Readable code in practice
Beyond the rules: what makes Python code easy to read, how to review it, how to bring an existing codebase in line, and practical notes for developers' working lives.
- A Code Review Checklist for Python Projects
A practical checklist for reviewing Python code: what to automate before review, what a human should look at (behaviour, tests, names, structure, errors, security), how to write review comments that help, and how to respond as an author.
- Adopting PEP 8 and a Formatter in an Existing Python Codebase
How to bring an existing Python project in line with PEP 8 without disrupting the team: agreeing on rules, one-off reformatting versus gradual adoption, keeping git blame useful, baselining linter warnings, and enforcing the result in CI.
- Readable Python Code: Beyond PEP 8
What makes Python code easy to read once the style checker is happy: the Zen of Python, names that reveal intent, flat control flow, small functions, named constants and the standard library idioms that say what they mean, with a tested before-and-after example.
- Relocating as a Software Developer: A Practical Checklist for Your First Months in a New City
A practical relocation checklist for developers moving for a new job: paperwork and right to work, finding a place to live with a good connection and a sane commute, the first week's admin, setting up your work, onboarding into a new codebase and building a life outside work.
