A career in computing is a long series of choices about what to learn, what to build and with whom. The field is wide: product engineering, infrastructure, security, data, research, teaching, management. Tools change quickly, but fundamentals, habits of learning and a record of finished work stay valuable for decades.
Key concepts
- Fundamentals first: algorithms, data structures, systems and networks outlast any framework.
- Evidence of skill: projects, contributions and writing that others can read and run.
- Breadth and depth: a broad base with one or two areas you know deeply.
- Paths: the individual-contributor track, the management track and moves between them.
- Learning on purpose: choosing a gap, closing it with a project, then reviewing what stuck.
Vocabulary
- Portfolio: a small set of finished projects that show how you work.
- Mentor: someone further along who gives you perspective and honest feedback.
- Specialist and generalist: deep in one area, or useful across many.
- Career ladder: a published description of expectations at each level.
What to study, in order
- Write down what you enjoy and what you do well, then list the roles that use both.
- Build one complete project end to end and publish its source and its documentation.
- Contribute a small fix to an open-source project you actually use.
- Write about something you learned, as if for a colleague who missed it.
- Review your plan twice a year: what to drop, what to deepen, what to try next.
Related tags
#interviews #engineering-management #open-source #technical-writing