Career Advice for Programmers
Central idea
Manage your career around the options and life you want, then make your experience visible enough that other people can connect it to opportunities.
Summary
A career should be steered rather than passively received. Gee starts with desired outcomes—flexibility, income, influence, meaningful work, family time, or simply more future options—then treats technologies, companies, and roles as means rather than destinations. Moving into a new role requires visible evidence: reframe existing work around the target responsibilities, seek projects that exercise them, and keep a monthly record of shipped work, leadership, and difficult situations handled. Technical visibility can begin with internal demos, user groups, public code, or useful writing. The same evidence improves promotion discussions, job searches, and salary negotiation, while company fit determines whether the title actually provides the life and work being sought.
Key ideas
Choose options before titles
Start from the work and life you want to make possible, then evaluate roles, technologies, and employers against that direction.
Make experience legible
Translate existing responsibilities into evidence that matches the next role instead of waiting for recruiters or managers to infer the connection.
Visibility enables recognition
Promotion and opportunity require an evidence-backed story that decision makers can remember and use.
A career steering loop
Define the options you want to preserve.
Build skills and evidence for the next direction.
Make useful work visible in low-risk ways.
Choose roles and companies for real fit.
Review the evidence and adjust the route.
Why it matters now
AI accelerates tool and role change. Engineers need a durable way to steer their careers, demonstrate judgment, and keep future options open rather than tying identity to one technology wave.
Continue with the original
This short version preserves the main argument. Follow the source for the complete talk, article, or book.