A thread · 3 notes · Engineering
Dev habits for a team of one.
Starting a Python project right, updating old ones without breaking them, and a DevOps checklist sized for one person.
- 1
Scaffolding a Python Project So Future-You Doesn't Hate It
The folder layout, the one config file, and the handful of checks I want in a Python project before the first real line of code. Plus where my notes had fallen behind the tools.
- 2
Keeping an Old Project Alive With Small, Surgical Updates
My notes on safe updates were written for a big team with canary releases and approval chains. Here's the same idea cut down for one person with a project that still has to work tomorrow.
- 3
A DevOps Reference for a Team of One
My DevOps reference note is a stack of prompt cards for everything from repo setup to installers. Condensed: which cards earn their keep for one person, what to watch in each, and the order I'd run them.