Plan
My first 30, 60 and 90 days
A plan, not a promise of experience: this is how I would approach a new team and a new codebase.
Days 1 to 30 · Learn
- →Map the codebase first: architecture, conventions, tests, how a change reaches production.
- →Run it locally, run the checks, read recent pull requests to learn the review culture.
- →Ship a small first pull request: a bug, an accessibility fix or a test.
- →Ask many questions early and write the answers down for the next newcomer.
Days 31 to 60 · Contribute
- →Own a small feature end to end: design review, implementation, tests, review feedback.
- →Improve one measurable thing, for example a Lighthouse score, test coverage or build time, and show the numbers.
- →Use AI tools the way the team allows, with rules and a check on every result.
Days 61 to 90 · Own
- →Take responsibility for one area, such as performance, accessibility or internationalisation.
- →Document how it works and propose the next improvement with a clear reason.
- →Help the next newcomer the way the first month helped me.
How I work with a team
- ✓Small pull requests with context: what changed, why, how to test it.
- ✓Short written updates instead of long meetings.
- ✓I say early when I am blocked or unsure.
- ✓I read code reviews as help, not as criticism.