# Seven Tips for Junior Developers

DevFeed: [Seven Tips for Junior Developers](<https://devfeed.tech/articles/7-tips-to-survive-as-a-junior-developer-20092.md>)

Original publisher: [Read original article](<https://medium.com/jobteaser-dev-team/7-tips-to-survive-as-a-junior-developer-b15b47586fb4?source=rss----bd77d16a0035---4>)

Author: Clément Gateaud

Published: 2023-05-23T14:06:01Z

Content type: tutorial

Language: en

Sources: [JobTeaser](<https://devfeed.tech/sources/jobteaser.md>)

Topics: [coding](<https://devfeed.tech/topics/coding.md>), [Code](<https://devfeed.tech/topics/code.md>)

Tags: [careers](<https://devfeed.tech/tags/careers.md>), [code](<https://devfeed.tech/tags/code.md>), [developer](<https://devfeed.tech/tags/developer.md>), [junior](<https://devfeed.tech/tags/junior.md>), [junior-developer](<https://devfeed.tech/tags/junior-developer.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>), [tips](<https://devfeed.tech/tags/tips.md>)

## AI overview

A career-advice article for junior developers. It recommends focusing first on the code needed for the current task, attempting to work through problems before seeking help, and using web resources to investigate issues.

## Source excerpt

© Midjourney Whether you're fresh out of school or transitioning from another career, landing a job as a junior developer is a great accomplishment. But it's only the first step on your path to a successful career. Finding your marks in this new position is the next big challenge. In this article I'll share with you 7 tips I would have loved to receive when I started as a junior developer, one year ago. 1. Learn to walk before you run During your first days as a "professional" developer, you will most likely feel overwhelmed by the size and complexity of your company's codebase. "What are all those files? Do we really need millions of lines of code to run our application?". It will for sure look very different from the small side projects you've worked on so far. Don't bother trying to understand the whole codebase and how everything is structured. Just focus on what you need for your current task. If your first task involves a minor fix to a specific behavior, focus on the file that's responsible for that behavior and forget about the rest. It's already a significant challenge to understand the necessary code for your initial task, especially since you'll also be learning about the company's processes, people, and products. https://medium.com/media/12a11f60dbd4c74090fdadd0e0f0fded/href Don't get me wrong, getting a bigger picture is important, but take it one step at a time. You will get more comfortable with the rest of the codebase over time. If you try to assimilate everything, you will assimilate nothing. Choose your fights. Time will do the rest. 2. Getting stuck is great (but not for too long) You'll get stuck on some issues when coding (just like every developer in the history of mankind). It may sound counterintuitive but getting stuck is a chance. Why? Because it is in those situations that you'll learn the most. https://medium.com/media/2776dac640fcf556b334de07293fd1e4/href Do not ask for help right away. Do your best to understand how things work and try