
Compose a 2-minute audio reflection on what 'developer' means after shipping features without writin
You'll have a recorded 2-minute voice piece articulating your role, skills, and judgment calls as someone who shapes, prompts, and ships with AI rather than typing code—a narrative you can share with
What you'll make
Developer Identity Audio Reflection
- Opening: What you actually do when you 'develop' with AI
- Skills: The 3-4 capabilities that make you effective beyond prompting
- Judgment: A specific example of where you had to override or redirect AI
- Close: How you'd explain your role to another developer
Record and upload a 2-3 minute audio file - can be phone voice memo, computer recording, or any clear audio format
The 3 parts
Each part ends with a check you can see.
Map Your Override Moments
Identify specific instances where you rejected or redirected AI's output and analyze what triggered those decisions
Done when
You have 3-5 documented override situations with your reasoning for each rejection or redirection
Test Your Language
Try explaining your AI-augmented developer role to someone and see where the explanation breaks down
Done when
You have tested 2-3 ways of describing your role and identified which explanations land vs which sound like hype
Record Your Reflection
Create the 2-minute audio piece using your tested language and concrete examples
Done when
You have a 2-3 minute audio recording that defines your AI-augmented developer identity using specific examples and tested language
Capstone: you put together your Developer Identity Audio Reflection.
Where this helps
An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.
About this lesson
What you'll be able to do
- Record a 2-minute audio piece articulating your role as someone who ships features through AI prompting rather than traditional coding
- Identify 3-4 specific skills you've developed as an AI-augmented developer that differ from traditional programming
- Have a clear narrative about your value as a 'conductor' vs 'coder' that you can share with peers or in professional contexts
Who it's for
- Developers who've been using AI tools to ship features and want to articulate what they actually do
- People transitioning from traditional coding to AI-augmented development who need language for their new role
- Anyone who builds with AI but struggles to explain their skills beyond 'I'm good at prompting'
What it won't cover
- Technical prompt engineering techniques or specific AI tool tutorials
- Career advice about transitioning industries or negotiating titles
- Defending AI development against traditional coding skeptics
Skills you'll practise
- Professional narrative development
- Technical skill articulation
- Role boundary definition
- Voice recording and delivery