17 Your Development Career

17.1 The Concept First

In Chapter 16, you learned to evaluate technologies systematically. But technical skills alone don’t build careers—they create potential. Converting that potential into opportunities requires a different skill set: professional development.

Consider two developers with identical technical abilities:

Developer A: Strong skills, no online presence, applies to jobs cold, waits for opportunities
Developer B: Strong skills, portfolio showcasing work, active in communities, creates opportunities

Developer B will have more options, better offers, and a clearer path forward. Not because they’re more talented, but because they’ve made their talent visible and accessible.

This chapter isn’t about self-promotion or personal branding gimmicks. It’s about the practical work of building a professional presence that accurately represents your capabilities and connects you with opportunities that match your goals.

17.2 Understanding Through Career Capital

Think of your career as a form of capital accumulation. You build different types of capital:

Technical Capital: Your skills and knowledge - The languages you know - The frameworks you’ve used - The problems you’ve solved

Social Capital: Your professional relationships - People who know your work - Communities you contribute to - References who vouch for you

Reputation Capital: How you’re perceived - Your portfolio and public work - Contributions others can see - Your professional presence

Most developers focus only on technical capital. But technical capital without social and reputation capital means opportunities don’t find you—you have to chase every one.

The Visibility Principle

Skills that people can see are worth more than skills they can’t. A public project demonstrates capability in ways a resume cannot. Documentation you’ve written, code you’ve shared, and problems you’ve solved publicly all create evidence of competence.

17.3 Discovering Career Building with Your AI Partner

Exploration 1: Portfolio Strategy

Ask your AI:
I'm building a web development portfolio. What types of projects
should I include? How do I make projects stand out when thousands
of developers have similar portfolios?

Key insights:

Quality over quantity: Three excellent projects beat ten mediocre ones

Show thinking, not just code: - Why you made certain decisions - Challenges you overcame - What you’d do differently

Variety that tells a story: - Different technologies demonstrating range - Increasing complexity showing growth - Business problems solved, not just technical exercises

Continue the conversation:
I have the projects from this course—the portfolio site, WordPress
business site, and React integration. How do I present these
professionally? What should I add or emphasise?

Exploration 2: Professional Positioning

You can’t be excellent at everything. Positioning means being known for something specific.

Ask your AI:
What does "positioning" mean for a developer's career? How do I
choose what to be known for when I'm just starting out?

Positioning isn’t limiting—it’s focusing:

Generalist trap: “I do everything” means “Hire me for anything” which often means “Hire someone else who specialises”
Specialist value: “I build accessible React applications” is memorable and referable
Evolution: Your positioning can change as you grow

Continue the conversation:
Based on what I've learned in this course (HTML/CSS, JavaScript,
WordPress, React), what are realistic positioning options for
someone entering the job market?

Exploration 3: Networking Without Networking

Many developers dislike traditional networking. But professional relationships matter.

Ask your AI:
I'm introverted and don't enjoy networking events. How can I
build professional relationships authentically as a developer?
What works better than collecting business cards?

Developer-friendly relationship building:

Contribute to open source: Work alongside others, earn respect through code
Answer questions: Stack Overflow, Reddit, Discord communities
Write about learning: Blog posts help others and demonstrate expertise
Attend (or speak at) meetups: Even quietly attending builds familiarity

Continue the conversation:
What's the minimum viable networking for a junior developer?
What activities have the highest return for the time invested?

Exploration 4: Continuous Learning

Technology changes. Your learning must continue.

Ask your AI:
How do I keep learning after formal education ends? How do I avoid
tutorial hell—watching courses without building real skills?

Effective continuous learning:

Learn by doing: Projects beat tutorials
Just-in-time learning: Learn what you need for current work
Depth over breadth: Master one thing rather than sampling many
Teach to learn: Explaining forces understanding

Continue the conversation:
How do I decide what to learn next? There are so many technologies.
How do I prioritise without chasing every trend?

17.4 From Concept to Code

Let’s make this practical.

Building Your Portfolio

Your portfolio demonstrates capability. Structure it intentionally.

Portfolio website essentials:

Portfolio Site
├── About
│   ├── Brief professional introduction
│   ├── What you're looking for
│   └── Contact information
├── Projects
│   ├── Featured project 1 (most impressive)
│   ├── Featured project 2
│   └── Featured project 3
│   (Each with: description, technologies, challenges, links)
├── Skills
│   └── Technologies with honest proficiency levels
└── Blog/Writing (optional but valuable)
    └── Technical posts showing your thinking

Project case study template:

## Project Name

**Overview**: One paragraph explaining what this is and why it matters.

**The Challenge**: What problem did this solve? What constraints existed?

**My Approach**: Key decisions and why you made them.

**Technologies Used**: List with brief explanation of why each was chosen.

**Key Features**:
- Feature 1 and its purpose
- Feature 2 and its purpose
- Feature 3 and its purpose

**Challenges Overcome**: Specific problems you solved (this shows learning).

**Results**: If applicable, metrics or outcomes.

**What I Learned**: Reflection that shows growth mindset.

**Links**: Live demo, GitHub repository, related blog post.

Example project description:

## Business Dashboard (React + WordPress)

**Overview**: A React single-page application that displays business
data from a WordPress backend, demonstrating headless architecture.

**The Challenge**: Create a modern, fast frontend while allowing
non-technical staff to manage content through WordPress.

**My Approach**: Chose React for component reusability and WordPress
REST API for content management. Used Tailwind for rapid styling.
Prioritised loading states and error handling for reliability.

**Technologies**: React, WordPress REST API, Tailwind CSS, Vite

**Key Features**:
- Dynamic content fetched from WordPress
- Responsive design (mobile-first)
- Loading skeletons for perceived performance
- Filter and search functionality

**Challenges Overcome**: WordPress featured images required the
`_embed` parameter—debugging this taught me to read API documentation
more carefully and test endpoints directly.

**What I Learned**: Headless architecture separates concerns
effectively. The frontend can evolve independently of the CMS.
I'd add TypeScript next time for better maintainability.

**Links**: [Live Demo] [GitHub] [Blog Post: Headless WordPress Lessons]

GitHub Profile Optimisation

Your GitHub profile is often viewed before your resume.

Profile README (create a repository named after your username):

# Hi, I'm [Your Name]

I build web applications with a focus on [your positioning].

## Currently Working On
- 🔨 [Current project]
- 📚 Learning [current focus]

## Recent Projects
- [Project 1](link) - Brief description
- [Project 2](link) - Brief description
- [Project 3](link) - Brief description

## Technologies
![JavaScript](badge) ![React](badge) ![WordPress](badge)

## Get in Touch
- Portfolio: [link]
- LinkedIn: [link]
- Email: [email]

Repository presentation:

Clear README for every project
Live demo links where applicable
Descriptive commit messages (people read these)
Consistent activity (small, regular commits beat sporadic large ones)

Writing for Professional Development

Writing demonstrates expertise and aids learning.

Blog post formats that work:

Tutorial: “How I Built X with Y”
- Teach something you learned
- Include code and explanation
- Address common pitfalls
Problem/Solution: “How I Fixed X”
- Describe the problem clearly
- Explain your debugging process
- Share the solution with context
Comparison: “X vs Y: When to Use Each”
- Fair evaluation of alternatives
- Specific use cases for each
- Your recommendation with reasoning
Learning Journey: “What I Learned Building X”
- Honest reflection
- Mistakes and lessons
- Advice for others

Writing tips:

Write for your past self (what did you need to know?)
Include code examples (developers scan for code)
Be concise (respect readers’ time)
Proofread (errors undermine credibility)

Ask your AI:
I want to write a blog post about something I learned while building
my React project. Help me brainstorm topics that would be useful to
other beginners and demonstrate my understanding.

LinkedIn for Developers

LinkedIn matters for job searching, even if you don’t love it.

Profile optimisation:

Headline: Not just “Student” but “Web Developer | React, WordPress, JavaScript”
Summary: Brief story of your path and what you’re looking for
Experience: Include projects, not just jobs
Skills: List specific technologies
Recommendations: Request from collaborators, instructors, colleagues

Activity that helps:

Share your blog posts
Comment thoughtfully on industry discussions
Celebrate completions (courses, projects, certifications)
Engage with content from companies you’re interested in

The Job Search Process

When you’re ready to apply:

Application strategy:

Target, don’t spray: Quality applications beat quantity
Research the company: Reference specific things in applications
Customise materials: Generic applications get generic rejections
Follow up appropriately: Once, after a week
Track everything: Spreadsheet with company, role, date, status

Technical interviews:

Practice coding problems (but don’t only practice problems)
Be ready to discuss your projects in depth
Ask thoughtful questions about their work
Follow up with thank-you notes

Portfolio presentations:

When asked to present work:

Start with the problem, not the technology
Explain your decision-making process
Be honest about challenges and what you’d do differently
Connect technical choices to business outcomes
Prepare for questions about alternatives you considered

17.5 Building Your Mental Model

Career Capital Accumulation

                    Opportunities
                         ▲
                         │
         ┌───────────────┼───────────────┐
         │               │               │
         │   Technical   │   Reputation  │
         │   Capital     │   Capital     │
         │   (Skills)    │   (Visible    │
         │               │   work)       │
         │       ▲       │       ▲       │
         │       │       │       │       │
         │       └───────┼───────┘       │
         │               │               │
         │         Social Capital        │
         │         (Relationships)       │
         │               ▲               │
         │               │               │
         └───────────────┴───────────────┘
                         │
                    Your Effort

All three types of capital reinforce each other. Skills let you build visible work. Visible work attracts relationships. Relationships lead to opportunities that build more skills.

The Career Flywheel

Build Skills → Create Projects → Share Work → Build Relationships
     ▲                                                │
     │                                                │
     └───────── Get Opportunities ◄───────────────────┘

Each element powers the next. Starting anywhere gets the wheel turning.

Positioning Quadrant

                    Specialist
                        │
            ┌───────────┼───────────┐
            │           │           │
   Frontend │  "React   │  "Full-   │ Full-Stack
            │   Dev"    │   Stack   │
            │           │   Dev"    │
            ├───────────┼───────────┤
            │ "WordPress│  "Agency  │
            │   Dev"    │   Dev"    │
            │           │           │
            └───────────┼───────────┘
                        │
                    Generalist

Different positions have different advantages:

Specialist: Higher rates, clearer referrals, deeper expertise
Generalist: More flexibility, broader opportunities, varied work
Neither is better—choose based on your preferences and market

17.6 Business Applications

Understanding the Hiring Perspective

Employers evaluating candidates consider:

Risk: Will this person succeed or create problems?
Evidence: What demonstrates capability?
Fit: Will they work well with the team?
Growth: Can they improve and adapt?

Your portfolio and presence reduce perceived risk by providing evidence. Everything you make public helps employers answer “Can this person do the job?”

The Value of Visible Contributions

Open source contributions, blog posts, and public projects:

Demonstrate skills without requiring trust
Show communication ability (code is communication)
Indicate engagement with the community
Provide conversation starters in interviews

Even small contributions count. A typo fix in documentation shows you engage with the ecosystem.

Long-term Career Planning

Think beyond the first job:

Year 1-2: Build foundation, try different areas
Year 3-5: Develop specialisation, build reputation
Year 5+: Leadership opportunities, consulting, teaching

Each stage requires different strategies. Early career is about learning and visibility. Later career is about leverage and impact.

ULO Connection

This develops ULO 2 (professional communication and project management). Career development isn’t separate from technical work—it’s how you translate technical capability into professional opportunity. These skills matter regardless of which technologies you ultimately work with.

17.7 Practice Exercises

Exercise Levels

Level 1: Direct application
Level 2: Minor modifications
Level 3: Combining concepts
Level 4: Problem-solving
Level 5: Open-ended design

Exercise 13.1: Portfolio Audit (Level 1)

Evaluate your current portfolio presence:

Google your name—what comes up?
Review your GitHub profile—what does it communicate?
Check your LinkedIn—is it complete and current?
List three things you could improve immediately

Exercise 13.2: Project Case Study (Level 2)

Write a case study for one of your projects using the template provided:

Choose your strongest project
Complete all sections of the template
Get feedback from a peer
Revise based on feedback

Exercise 13.3: Professional Positioning (Level 3)

Develop your professional positioning:

List your strongest skills
Identify which combinations are distinctive
Research job postings that match your skills
Write a positioning statement (one sentence that describes what you do)
Get feedback—is it clear? Memorable? Accurate?

Exercise 13.4: Content Creation (Level 4)

Create professional content:

Write a technical blog post about something you learned
Publish it (dev.to, Medium, personal blog, or LinkedIn)
Share it on one social platform
Reflect: What was harder than expected? What did you learn from writing?

Exercise 13.5: Career Strategy (Level 5)

Develop a 12-month career strategy:

Define where you want to be in one year
Identify the gaps between current state and goal
Create a plan with monthly milestones
Include: skills to develop, projects to build, connections to make, content to create
Write 500 words explaining your strategy and reasoning

17.8 Chapter Summary

Technical skills create potential; professional presence creates opportunities
Portfolios should show thinking, not just code
Positioning helps you be memorable and referable
Relationships develop through contribution, not just networking
Continuous learning requires intentional practice, not just consumption
Career development is a long game—invest consistently

17.9 Reflection

Before moving to Chapter 14, ensure you can:

Explain what makes a strong portfolio project
Write a compelling project case study
Describe your professional positioning
Identify at least three ways to build professional relationships
Plan continuous learning without chasing every trend
Understand what employers look for beyond technical skills

17.10 Your Learning Journal

Record your responses to these prompts:

Portfolio Assessment: What’s the strongest thing in your current portfolio? What’s the biggest gap?
Positioning Exploration: What do you want to be known for? How does this align with your interests and the market?
AI Conversation Reflection: What career question did you explore with AI? What insight was most valuable?
Networking Comfort: What forms of professional relationship building feel authentic to you? What would you avoid?

17.11 Next Steps

You now have frameworks for building your professional presence and planning your career development.

In Chapter 18, we’ll conclude by examining what it means to be a developer in the AI era. How do AI tools change the profession? What skills remain essential? How do you prepare for a future where AI capabilities continue to expand?

# Your Development Career {#sec-development-career} ## The Concept First In @sec-emerging-technologies, you learned to evaluate technologies systematically. But technical skills alone don't build careers—they create potential. Converting that potential into opportunities requires a different skill set: **professional development**. Consider two developers with identical technical abilities: - **Developer A**: Strong skills, no online presence, applies to jobs cold, waits for opportunities - **Developer B**: Strong skills, portfolio showcasing work, active in communities, creates opportunities Developer B will have more options, better offers, and a clearer path forward. Not because they're more talented, but because they've made their talent **visible and accessible**. This chapter isn't about self-promotion or personal branding gimmicks. It's about the practical work of building a professional presence that accurately represents your capabilities and connects you with opportunities that match your goals. ## Understanding Through Career Capital Think of your career as a form of capital accumulation. You build different types of capital: **Technical Capital**: Your skills and knowledge - The languages you know - The frameworks you've used - The problems you've solved **Social Capital**: Your professional relationships - People who know your work - Communities you contribute to - References who vouch for you **Reputation Capital**: How you're perceived - Your portfolio and public work - Contributions others can see - Your professional presence Most developers focus only on technical capital. But technical capital without social and reputation capital means opportunities don't find you—you have to chase every one. ::: {.callout-tip} ## The Visibility Principle Skills that people can see are worth more than skills they can't. A public project demonstrates capability in ways a resume cannot. Documentation you've written, code you've shared, and problems you've solved publicly all create evidence of competence. ::: ## Discovering Career Building with Your AI Partner ### Exploration 1: Portfolio Strategy ``` Ask your AI: I'm building a web development portfolio. What types of projects should I include? How do I make projects stand out when thousands of developers have similar portfolios? ``` Key insights: **Quality over quantity**: Three excellent projects beat ten mediocre ones **Show thinking, not just code**: - Why you made certain decisions - Challenges you overcame - What you'd do differently **Variety that tells a story**: - Different technologies demonstrating range - Increasing complexity showing growth - Business problems solved, not just technical exercises ``` Continue the conversation: I have the projects from this course—the portfolio site, WordPress business site, and React integration. How do I present these professionally? What should I add or emphasise? ``` ### Exploration 2: Professional Positioning You can't be excellent at everything. Positioning means being known for something specific. ``` Ask your AI: What does "positioning" mean for a developer's career? How do I choose what to be known for when I'm just starting out? ``` Positioning isn't limiting—it's focusing: - **Generalist trap**: "I do everything" means "Hire me for anything" which often means "Hire someone else who specialises" - **Specialist value**: "I build accessible React applications" is memorable and referable - **Evolution**: Your positioning can change as you grow ``` Continue the conversation: Based on what I've learned in this course (HTML/CSS, JavaScript, WordPress, React), what are realistic positioning options for someone entering the job market? ``` ### Exploration 3: Networking Without Networking Many developers dislike traditional networking. But professional relationships matter. ``` Ask your AI: I'm introverted and don't enjoy networking events. How can I build professional relationships authentically as a developer? What works better than collecting business cards? ``` Developer-friendly relationship building: - **Contribute to open source**: Work alongside others, earn respect through code - **Answer questions**: Stack Overflow, Reddit, Discord communities - **Write about learning**: Blog posts help others and demonstrate expertise - **Attend (or speak at) meetups**: Even quietly attending builds familiarity ``` Continue the conversation: What's the minimum viable networking for a junior developer? What activities have the highest return for the time invested? ``` ### Exploration 4: Continuous Learning Technology changes. Your learning must continue. ``` Ask your AI: How do I keep learning after formal education ends? How do I avoid tutorial hell—watching courses without building real skills? ``` Effective continuous learning: - **Learn by doing**: Projects beat tutorials - **Just-in-time learning**: Learn what you need for current work - **Depth over breadth**: Master one thing rather than sampling many - **Teach to learn**: Explaining forces understanding ``` Continue the conversation: How do I decide what to learn next? There are so many technologies. How do I prioritise without chasing every trend? ``` ## From Concept to Code Let's make this practical. ### Building Your Portfolio Your portfolio demonstrates capability. Structure it intentionally. **Portfolio website essentials:** ``` Portfolio Site ├── About │ ├── Brief professional introduction │ ├── What you're looking for │ └── Contact information ├── Projects │ ├── Featured project 1 (most impressive) │ ├── Featured project 2 │ └── Featured project 3 │ (Each with: description, technologies, challenges, links) ├── Skills │ └── Technologies with honest proficiency levels └── Blog/Writing (optional but valuable) └── Technical posts showing your thinking ``` **Project case study template:** ```markdown ## Project Name **Overview**: One paragraph explaining what this is and why it matters. **The Challenge**: What problem did this solve? What constraints existed? **My Approach**: Key decisions and why you made them. **Technologies Used**: List with brief explanation of why each was chosen. **Key Features**: - Feature 1 and its purpose - Feature 2 and its purpose - Feature 3 and its purpose **Challenges Overcome**: Specific problems you solved (this shows learning). **Results**: If applicable, metrics or outcomes. **What I Learned**: Reflection that shows growth mindset. **Links**: Live demo, GitHub repository, related blog post. ``` **Example project description:** ```markdown ## Business Dashboard (React + WordPress) **Overview**: A React single-page application that displays business data from a WordPress backend, demonstrating headless architecture. **The Challenge**: Create a modern, fast frontend while allowing non-technical staff to manage content through WordPress. **My Approach**: Chose React for component reusability and WordPress REST API for content management. Used Tailwind for rapid styling. Prioritised loading states and error handling for reliability. **Technologies**: React, WordPress REST API, Tailwind CSS, Vite **Key Features**: - Dynamic content fetched from WordPress - Responsive design (mobile-first) - Loading skeletons for perceived performance - Filter and search functionality **Challenges Overcome**: WordPress featured images required the `_embed` parameter—debugging this taught me to read API documentation more carefully and test endpoints directly. **What I Learned**: Headless architecture separates concerns effectively. The frontend can evolve independently of the CMS. I'd add TypeScript next time for better maintainability. **Links**: [Live Demo] [GitHub] [Blog Post: Headless WordPress Lessons] ``` ### GitHub Profile Optimisation Your GitHub profile is often viewed before your resume. **Profile README (create a repository named after your username):** ```markdown # Hi, I'm [Your Name] I build web applications with a focus on [your positioning]. ## Currently Working On - 🔨 [Current project] - 📚 Learning [current focus] ## Recent Projects - [Project 1](link) - Brief description - [Project 2](link) - Brief description - [Project 3](link) - Brief description ## Technologies ![JavaScript](badge) ![React](badge) ![WordPress](badge) ## Get in Touch - Portfolio: [link] - LinkedIn: [link] - Email: [email] ``` **Repository presentation:** - Clear README for every project - Live demo links where applicable - Descriptive commit messages (people read these) - Consistent activity (small, regular commits beat sporadic large ones) ### Writing for Professional Development Writing demonstrates expertise and aids learning. **Blog post formats that work:** 1. **Tutorial**: "How I Built X with Y" - Teach something you learned - Include code and explanation - Address common pitfalls 2. **Problem/Solution**: "How I Fixed X" - Describe the problem clearly - Explain your debugging process - Share the solution with context 3. **Comparison**: "X vs Y: When to Use Each" - Fair evaluation of alternatives - Specific use cases for each - Your recommendation with reasoning 4. **Learning Journey**: "What I Learned Building X" - Honest reflection - Mistakes and lessons - Advice for others **Writing tips:** - Write for your past self (what did you need to know?) - Include code examples (developers scan for code) - Be concise (respect readers' time) - Proofread (errors undermine credibility) ``` Ask your AI: I want to write a blog post about something I learned while building my React project. Help me brainstorm topics that would be useful to other beginners and demonstrate my understanding. ``` ### LinkedIn for Developers LinkedIn matters for job searching, even if you don't love it. **Profile optimisation:** - **Headline**: Not just "Student" but "Web Developer | React, WordPress, JavaScript" - **Summary**: Brief story of your path and what you're looking for - **Experience**: Include projects, not just jobs - **Skills**: List specific technologies - **Recommendations**: Request from collaborators, instructors, colleagues **Activity that helps:** - Share your blog posts - Comment thoughtfully on industry discussions - Celebrate completions (courses, projects, certifications) - Engage with content from companies you're interested in ### The Job Search Process When you're ready to apply: **Application strategy:** 1. **Target, don't spray**: Quality applications beat quantity 2. **Research the company**: Reference specific things in applications 3. **Customise materials**: Generic applications get generic rejections 4. **Follow up appropriately**: Once, after a week 5. **Track everything**: Spreadsheet with company, role, date, status **Technical interviews:** - Practice coding problems (but don't only practice problems) - Be ready to discuss your projects in depth - Ask thoughtful questions about their work - Follow up with thank-you notes **Portfolio presentations:** When asked to present work: 1. Start with the problem, not the technology 2. Explain your decision-making process 3. Be honest about challenges and what you'd do differently 4. Connect technical choices to business outcomes 5. Prepare for questions about alternatives you considered ## Building Your Mental Model ### Career Capital Accumulation ``` Opportunities ▲ │ ┌───────────────┼───────────────┐ │ │ │ │ Technical │ Reputation │ │ Capital │ Capital │ │ (Skills) │ (Visible │ │ │ work) │ │ ▲ │ ▲ │ │ │ │ │ │ │ └───────┼───────┘ │ │ │ │ │ Social Capital │ │ (Relationships) │ │ ▲ │ │ │ │ └───────────────┴───────────────┘ │ Your Effort ``` All three types of capital reinforce each other. Skills let you build visible work. Visible work attracts relationships. Relationships lead to opportunities that build more skills. ### The Career Flywheel ``` Build Skills → Create Projects → Share Work → Build Relationships ▲ │ │ │ └───────── Get Opportunities ◄───────────────────┘ ``` Each element powers the next. Starting anywhere gets the wheel turning. ### Positioning Quadrant ``` Specialist │ ┌───────────┼───────────┐ │ │ │ Frontend │ "React │ "Full- │ Full-Stack │ Dev" │ Stack │ │ │ Dev" │ ├───────────┼───────────┤ │ "WordPress│ "Agency │ │ Dev" │ Dev" │ │ │ │ └───────────┼───────────┘ │ Generalist ``` Different positions have different advantages: - **Specialist**: Higher rates, clearer referrals, deeper expertise - **Generalist**: More flexibility, broader opportunities, varied work - **Neither is better**—choose based on your preferences and market ## Business Applications ### Understanding the Hiring Perspective Employers evaluating candidates consider: - **Risk**: Will this person succeed or create problems? - **Evidence**: What demonstrates capability? - **Fit**: Will they work well with the team? - **Growth**: Can they improve and adapt? Your portfolio and presence reduce perceived risk by providing evidence. Everything you make public helps employers answer "Can this person do the job?" ### The Value of Visible Contributions Open source contributions, blog posts, and public projects: - Demonstrate skills without requiring trust - Show communication ability (code is communication) - Indicate engagement with the community - Provide conversation starters in interviews Even small contributions count. A typo fix in documentation shows you engage with the ecosystem. ### Long-term Career Planning Think beyond the first job: - **Year 1-2**: Build foundation, try different areas - **Year 3-5**: Develop specialisation, build reputation - **Year 5+**: Leadership opportunities, consulting, teaching Each stage requires different strategies. Early career is about learning and visibility. Later career is about leverage and impact. ::: {.callout-note} ## ULO Connection This develops **ULO 2** (professional communication and project management). Career development isn't separate from technical work—it's how you translate technical capability into professional opportunity. These skills matter regardless of which technologies you ultimately work with. ::: ## Practice Exercises ::: {.callout-note} ## Exercise Levels - **Level 1**: Direct application - **Level 2**: Minor modifications - **Level 3**: Combining concepts - **Level 4**: Problem-solving - **Level 5**: Open-ended design ::: ### Exercise 13.1: Portfolio Audit (Level 1) Evaluate your current portfolio presence: 1. Google your name—what comes up? 2. Review your GitHub profile—what does it communicate? 3. Check your LinkedIn—is it complete and current? 4. List three things you could improve immediately ### Exercise 13.2: Project Case Study (Level 2) Write a case study for one of your projects using the template provided: 1. Choose your strongest project 2. Complete all sections of the template 3. Get feedback from a peer 4. Revise based on feedback ### Exercise 13.3: Professional Positioning (Level 3) Develop your professional positioning: 1. List your strongest skills 2. Identify which combinations are distinctive 3. Research job postings that match your skills 4. Write a positioning statement (one sentence that describes what you do) 5. Get feedback—is it clear? Memorable? Accurate? ### Exercise 13.4: Content Creation (Level 4) Create professional content: 1. Write a technical blog post about something you learned 2. Publish it (dev.to, Medium, personal blog, or LinkedIn) 3. Share it on one social platform 4. Reflect: What was harder than expected? What did you learn from writing? ### Exercise 13.5: Career Strategy (Level 5) Develop a 12-month career strategy: 1. Define where you want to be in one year 2. Identify the gaps between current state and goal 3. Create a plan with monthly milestones 4. Include: skills to develop, projects to build, connections to make, content to create 5. Write 500 words explaining your strategy and reasoning ## Chapter Summary - Technical skills create potential; professional presence creates opportunities - Portfolios should show thinking, not just code - Positioning helps you be memorable and referable - Relationships develop through contribution, not just networking - Continuous learning requires intentional practice, not just consumption - Career development is a long game—invest consistently ## Reflection Before moving to Chapter 14, ensure you can: - [ ] Explain what makes a strong portfolio project - [ ] Write a compelling project case study - [ ] Describe your professional positioning - [ ] Identify at least three ways to build professional relationships - [ ] Plan continuous learning without chasing every trend - [ ] Understand what employers look for beyond technical skills ## Your Learning Journal Record your responses to these prompts: 1. **Portfolio Assessment**: What's the strongest thing in your current portfolio? What's the biggest gap? 2. **Positioning Exploration**: What do you want to be known for? How does this align with your interests and the market? 3. **AI Conversation Reflection**: What career question did you explore with AI? What insight was most valuable? 4. **Networking Comfort**: What forms of professional relationship building feel authentic to you? What would you avoid? ## Next Steps You now have frameworks for building your professional presence and planning your career development. In @sec-ai-era-developer, we'll conclude by examining what it means to be a developer in the AI era. How do AI tools change the profession? What skills remain essential? How do you prepare for a future where AI capabilities continue to expand?