Reading notes from 2020; revised November 17, 2026. Reported architecture and scale refer to the source period.
Keep a record of contribution
My most reusable career habit is a short work log. Record the problem, my part, collaborators, and the observed result while the details are fresh. It is easier to prepare a fair performance narrative from evidence than from the last memorable incident.
Say no with the tradeoff visible
“Don’t overcommit” becomes actionable when I name the displaced work. For example: “I can take this investigation today, but the migration review will move to Thursday. Which is more valuable this week?” That opens a prioritization discussion instead of turning a boundary into a personal rejection.
Ask why before choosing a tool
Before moving from a request to implementation, write the intended outcome and constraints. Then compare a few approaches. This makes it easier to notice when the requested solution solves a different problem.
A weekly reflection
| Question | A useful record |
|---|---|
| What changed? | A result, link, or decision |
| Who helped? | Specific collaborators and shared credit |
| Where did I overcommit? | The competing promises and next adjustment |
| What relationship needs attention? | A conversation to schedule or follow up |
| What should stop? | Work with low value or unclear ownership |
These are practices, not a claim that being above a team median guarantees growth. Roles, opportunities, and organizational expectations matter. See the brag-document template for a more detailed record.