I work in the Python data ecosystem, building tools like Dask and Coiled. I write about the technical and human aspects of this work.
I encourage colleagues to write blogposts frequently. It informs your community, increases visibility, and focuses you on work relevant to others.
Maintainers' willingness to help you for free is optional. Minimal, complete, verifiable examples take 10-30 minutes but dramatically increase your chances of getting help.
Abstraction has costs. Every layer you add is another place readers have to look. Sometimes the clearest code is the most direct.
In dynamic environments, historical advice often doesn't apply. Imposter syndrome is appropriate—but so is trusting your own thinking.
Resist the urge to answer technical questions. We want to show off how things work, but we often dive too deep before understanding the customer's actual problem.
Someone has to pay the psychological cost of uncertainty. I choose honesty, even when it has negative consequences.
Real-time chat makes everyone feel productive but does little for long-term consensus building. I prefer public, permanent, searchable, cross-referenceable discussions.
