Find people and experiences by name, username, role/title, keyword, or technology tag.
We ran into this around team onboarding during a traffic spike. The work was mostly unblocking other people, not closing my own tickets. Clear noes protected the roadmap more than extra hours. Writing the doc nobody wanted still changed how fast the team moved. Impact was hard to see until a project stalled without that context. I am still learning to describe that work without vanity metrics.
We ran into this around team onboarding after we split the monolith. We did not rewrite the service. We moved one endpoint at a time. Dual writes ran until nightly totals matched for several days. A flag sent a small percentage of reads to the new path. The hard part was matching rounding the old code had hidden. Cutover finished with a small blast radius and an easy rollback.
We ran into this around team onboarding while rolling back payments. The work was mostly unblocking other people, not closing my own tickets. Clear noes protected the roadmap more than extra hours. Writing the doc nobody wanted still changed how fast the team moved. Impact was hard to see until a project stalled without that context. I am still learning to describe that work without vanity metrics.
We ran into this around team onboarding on a quiet Sunday incident. We did not rewrite the service. We moved one endpoint at a time. Dual writes ran until nightly totals matched for several days. A flag sent a small percentage of reads to the new path. The hard part was matching rounding the old code had hidden. Cutover finished with a small blast radius and an easy rollback.
We ran into this around team onboarding after the replica failover. The work was mostly unblocking other people, not closing my own tickets. Clear noes protected the roadmap more than extra hours. Writing the doc nobody wanted still changed how fast the team moved. Impact was hard to see until a project stalled without that context. I am still learning to describe that work without vanity metrics.
We ran into this around team onboarding during a Friday deploy. We did not rewrite the service. We moved one endpoint at a time. Dual writes ran until nightly totals matched for several days. A flag sent a small percentage of reads to the new path. The hard part was matching rounding the old code had hidden. Cutover finished with a small blast radius and an easy rollback.