Overview of Story: The Aging Programmer
Adam Gordon Bell interviews Kate Gregory (C++ expert, conference speaker, cancer survivor) about aging as a software developer. They discuss surprising survey results and research Kate collected about what programmers fear as they age, what actually breaks down, how workplaces and culture amplify or mitigate decline, and practical steps to have a long, fulfilling career in tech.
Core themes and conclusions
- Biggest worry vs. reality:
- Survey respondents were most worried about eyesight (not abstract cognition)—and eyesight is often easily remediable (glasses, surgery, larger fonts).
- Many physical problems people assume are “just aging” have specific, fixable causes.
- The real threats:
- Social and structural factors (loneliness, boredom, loss of purpose, ageism, workplace design) often harm older developers more than inevitable physical decline.
- Negative stories about aging (internalized or cultural) become self-fulfilling and correlate with worse health outcomes.
- Agency and planning matter:
- Building reserves (financial, social, professional) and deliberately pursuing “gains” (new hobbies, networks, skills) mitigate loss and boredom.
- Small practical accommodations and asking for help make a large difference.
Key takeaways
- Assistive tech is underused: People adapt to worse vision/hearing rather than getting glasses/hearing aids, which costs cognitive bandwidth and participation.
- Motivation beats raw ability: Older devs can learn well but may resist repeatedly changing tools/processes—sometimes for good reasons (skepticism), sometimes from inertia or cynicism.
- Ageism is real and subtle:
- Decision-makers may openly or unconsciously exclude older devs from training, long projects, or visibility.
- Workplace design (e.g., meeting rooms only on different floors, no elevators nearby) and social expectations can push people out.
- Loneliness and loss of workplace social networks are major retirement/aging worries; work often supplies most of a programmer’s social life.
- Survivor bias: Seeing mostly young people at conferences or companies hides those who left, were pushed out, or died.
- Mindset influences health: People who think aging is bad have higher stress and worse health outcomes; expectations shape behavior (e.g., stop doing activities vs. seek fixes).
Notable anecdotes & insights
- People report dramatic perceptual gains after getting glasses or hearing aids (“I could finally see tree leaves”).
- Kate discovered multiple fixable health issues (knee injury treatable by arthroscopic surgery; idiopathic stenosis found on a scan) that she initially misattributed to “just aging.”
- Examples of ageism:
- “We’ll send Bill (25) on that course” versus excluding a 55-year-old.
- Servers treating someone with a cane as incapable of ordering.
- Office built to force young-staff movement up/down stairs, excluding those with mobility issues.
- Codebase continuity: Many systems rely on a single person; sometimes that person has died and no one documented rationale—this compounds loss when contributors leave or pass away.
Practical, actionable recommendations
- Fix sensory problems early:
- Get an eye exam; consider glasses/contact/laser surgery.
- Check hearing; use hearing aids when needed.
- Ask for larger fonts, captions, and other accessibility adjustments in meetings and tools.
- Treat workspace and tooling as mutable:
- Advocate for distributed meeting rooms, accessible routes, or remote/hybrid norms that include people with mobility or caregiving constraints.
- Build reserves:
- Financial: savings, credit lines, retirement planning.
- Social: cultivate hobbies that put you in places to meet people; join clubs, classes, local groups (darts, pickleball, art, etc.).
- Professional: maintain contacts, document codebases, mentor and be mentored.
- Guard attitude and stories:
- Avoid writing a resignation script for your future self (i.e., “I’m old so I’ll stop trying”).
- Maintain optimism about what can be fixed; seek medical opinions rather than assuming decline is inevitable.
- Plan transitions:
- Prepare for changes in role, location, or energy levels (e.g., negotiate no-evening events or flexible schedules).
- Create a semi-retirement model if you want to phase out rather than quit abruptly.
- Use lifetime skills for new problems:
- Apply project planning, networking, and problem-solving skills to build a new social life or second career if needed.
- Let people help: accept practical help from neighbors and colleagues when appropriate—it strengthens social ties.
Limitations & context of Kate’s research
- The survey was not a statistically representative sample: it skewed toward Kate’s networks (C++ community), likely older, and mostly American respondents.
- Still valuable as qualitative insight into a broad set of concerns that many developers will encounter.
Who this episode is for
- Mid‑career and senior software developers thinking about longevity in tech.
- Managers and company leaders who want to make workplaces more inclusive for aging staff.
- Anyone in tech who’s planning their long-term health, social life, and career transitions.
Final practical checklist (quick)
- Schedule eye and hearing checks; adopt assistive tech as needed.
- Document systems and reach out to former owners before they’re gone.
- Start or deepen at least one in-person hobby that exposes you to new social circles.
- Build financial and social reserves now (savings + relationships).
- Advocate for accessible workplace design and inclusive training opportunities.
- Reframe aging: expect loss, but plan for gains.
Credits: host Adam Gordon Bell; guest Kate Gregory (C++ developer, cancer survivor, co‑lead on Carbon language, conference organizer).