The First 90 Days Define Your Career Trajectory
Your first job as a developer is overwhelming. Imposter syndrome hits hard. The codebase looks alien. Your teammates speak in acronyms you don't understand.
I've been through it. Here's the survival guide I wish I had.
Week 1-2: Observe and Learn
Do:
- Read the codebase — Don't try to understand everything. Focus on the main user flows
- Set up your dev environment — This always takes longer than expected
- Ask questions — Write them down first, then batch them
- Take notes — You'll forget 90% of what you hear in meetings
Don't:
- Propose architecture changes on day 1
- Compare yourself to senior devs
- Stay silent when you're stuck for more than 30 minutes
Week 3-4: Start Contributing
Your First PR Checklist
[ ] Picked a small, well-defined issue
[ ] Read related code thoroughly
[ ] Asked clarifying questions if needed
[ ] Wrote tests for my changes
[ ] Self-reviewed my own PR before requesting review
[ ] PR description explains WHY, not just WHAT
The Magic Phrase
When you don't understand something, say:
"I want to make sure I understand correctly. Is [your interpretation] right?"
This shows you're thinking, not just asking to be spoon-fed.
Month 2: Build Momentum
The 3-Task Rule
Every day, complete at least:
- One code task (feature, bug fix, refactor)
- One learning task (read docs, watch a talk, explore codebase)
- One relationship task (pair program, ask a question, help someone)
Track Everything
Keep a simple log:
Date: 2026-03-18
- Completed: Fixed pagination bug in /users endpoint
- Learned: How our caching layer works
- Blocked: Need access to staging DB
- Tomorrow: Start feature X
This log is invaluable for:
- Performance reviews
- Updating your resume
- Seeing your own progress when imposter syndrome hits
Month 3: Establish Yourself
Go Beyond Your Tickets
- Write documentation for something that confused you
- Create a README for a poorly documented service
- Automate a manual process
- Improve error messages
Build Internal Reputation
- Be reliable — Deliver what you promise, when you promise
- Be helpful — Answer questions in Slack when you know the answer
- Be curious — Attend tech talks, read RFCs, join architecture discussions
The Mistakes I Made
1. Trying to prove myself too fast
I took on complex tasks before I understood the codebase. Result: wasted time and bad PRs.
2. Not asking for help early enough
I spent 4 hours debugging something a senior could have spotted in 5 minutes. Set a 30-minute rule: if you're stuck for 30 minutes, ask.
3. Ignoring non-code skills
Communication, time estimation, and stakeholder management matter as much as coding.
Essential Tools for New Developers
| Category | Tool | Why |
|---|---|---|
| Notes | Notion/Obsidian | Track everything you learn |
| Git | GitLens | Understand code history |
| Debug | Console/Xcode | Learn your debugger deeply |
| AI | Claude/ChatGPT | Explain code, generate tests |
| Time | Toggl | Track where your time goes |
The Truth About Imposter Syndrome
Every developer feels it. Even seniors. The difference is that experienced devs know it's normal and push through it.
You were hired because someone believed you could do this job. Prove them right by showing up, being consistent, and improving every day.
Starting a new dev job? What's your biggest challenge? Share in the comments!
Follow me: @SwiftUIDaily on Telegram
Top comments (0)