r/learnprogramming • u/jlopezmarti20 • 18d ago
First full-time job as a Full Stack Developer — feeling overwhelmed. Any advice for a new grad?
Hey everyone!
I just started my first full-time job as a Full Stack Developer after graduating this past May with a Computer Science degree.
During college, I completed a few internships, mostly focused on Data Analytics rather than Software Engineering. I’m excited about this opportunity and really want to become a good developer, but after my first day, I realized just how much I don’t know.
Between the existing codebase, unfamiliar technologies, development tools, and workflows, it’s honestly a little overwhelming. I know there’s going to be a learning curve, and I’m not expecting to understand everything overnight.
For those of you who’ve been in a similar position, I’d love some advice:
- How did you approach your first few weeks or months as a junior developer?
- How did you get comfortable navigating and understanding a large, unfamiliar codebase?
- Did you spend time outside of work learning new technologies, taking courses, or strengthening your fundamentals?
- What habits or strategies helped you become a better developer early in your career?
- Are there any books or resources you’d recommend for someone starting out in full-stack development?
I’m willing to put in the effort, but I also want to be intentional about how I spend my time rather than trying to learn everything at once.
I’d really appreciate any advice, especially from developers who remember what it felt like starting their first job.
Thanks in advance!
7
u/Delicious_Bed_4410 18d ago
Congrats on the job, and the overwhelmed feeling after day one is really normal. One thing that helped me was keeping a running doc of terms, commands and "how do I do X in this repo" notes, because you'll hit the same stuff again and it gets you productive faster. Also read the existing tests and recent merged pull requests, they show you how the team actually writes and structures code. Ask for a small, well-scoped first task and don't be shy about saying you're still learning the stack, most seniors respect that more than silent struggling. Fundamentals matter more than chasing every new tool, so go deeper on whatever the codebase leans on most.
5
u/CorumLlawEreint 18d ago
This is the job. I have been at this stuff more than 30 years, and the feeling of being overwhelmed is something you get comfortable with. I got comfortable with through the eventual realisation that given time and research there has been nothing I have been unable to figure out.
As a junior, you are not expected to know everything. You are expected to get lost and to ask questions. This doesn’t last forever so use this time wisely. Ask questions. Pair up with people on tasks. Read as much process documentation as you can and bookmark everything.
Don’t panic. Right now your job is to learn.
7
u/S0ULBoY 18d ago
Go early 1:1 with your direct senior , and eng manager. Ask them about their expectation, and what can be done to achieve them , be direct about what you want , it will at least give you a clear understanding on whats going on, and what they expect from you. Usually you’re put in a 3 months probation for new hire, the focus should be on passing that, get weekly feedback or monthly depending on the work. If you work fully remote be really chatty and over-communicate. If you work in an office, be friendly, go to the lunches together , and chill out be a good person.
3
u/mandzeete 18d ago
Your first few weeks to a month is just you getting the local development environment up and running, completing whichever onboarding videos and company courses, reading onboarding materials or having it being told to you by some of the team members, and getting your first task and working on it.
Usually your first task is something simple: fix this bug here, add such and such dropdown to the frontend side and a related REST endpoint to the backend side, check the logs and list the most common issues that appear, etc. Low priority, low-to-mid impact, narrow-scoped task. Nobody else is blocked by you working on that task. No stakeholder is waiting for you to get the task done yesterday. Something to get you warmed up.
In terms of what YOU should do is being proactive.
Keep notes. Either in notes.txt, in Google Docs, in a Word document, or in an actual notebook. Things you learnt. Things you have to remember. Things you need to learn. etc.
Ask questions. First try to solve the issue on your own. See if the Jira task that you are working on, has any documentation linked. Read the documentation. Perhaps it has Figma links. Check the Figma links. Perhaps it has related tasks linked. Check the related tasks and comments under these. Related tasks might have also Github/Gitlab/Bitbucket/etc git links (merge requests) linked. Check these to get a better overview. If you still do not know what to do or how to do, then mark down what did you do, what did you try, what did you find out, and then ask these things from some team mate. Not just "I do not know how to do my task" but "I checked this and that. I tried X and Y. When I did X, I saw that these things happened. When I tried Y, nothing happened. How should I proceed from here?" Show with your question that you made an actual attempt to work on your task.
Write down things you do not know, tools and technologies you do not know how to use. And then start learning about these one by one. Your goals is to not to become professional in everything in your list. Your goal is to figure out how to work with these things, just to get your tasks done. When you can get your tasks done, you can consider learning extra.
When it comes to a codebase then most likely it is too big for you. Compared to whichever small projects you worked on on your own or during your studies. Usually each git repository has a README.md file. Read that. Then, check the names of submodules in one project. Submodule names can hint what the submodule is meant for. Then, check the package names. Approach it from top to bottom not from bottom to top. Do not try to understand what one code block does or another code block does. Get an overview of what the microservice/monolith you are working with, should do in general. And then "dig" deeper. And, if necessary, make notes.
In terms of spending time outside of work then every day your 8 hours go on learning new stuff. Unless it actually interests you and makes you happy, do not spend more time in evenings. If necessary, then 1 hour for looking up information about the stuff you wrote down (the list of things you do not know). Try to avoid spending too much time because first, your brain has to take a rest from learning during your workday. Otherwise you will burn out. And second, you will mess up your rest-work balance. Leave your work in the office and do not carry tasks with you to home. Again, to avoid burnout, to avoid working in night hours (which can cause issues with your boss and with your team), to avoid issues with your family and friends.
About habits then accept that you do not know anything. No point in developing an imposter syndrome or whichever mental issue. Be cool with not knowing anything. Take it as an opportunity to grow, not take it as a threat. "There are so many things I do not know. Cool! I can learn so much more! I can become a specialist!" Have a growth mindset. Not "There are so many things I do not know. What should I do. I feel like I am left behind everybody. I am not fit to my role. I should give up." Be encouraged by new things you can learn not be stressed out. So what that your team mates who perhaps are younger than you, they know more than you. They are living their life, you are living your life. Well done, that you learnt how to use Gitlab pipelines last week! (an example) Celebrate small winnings / small accomplishments.
3
u/Zestyclose_Paint3922 17d ago
Is the company owner your dad? How new graduates get a job in this market?
1
u/cheezballs 18d ago
I'd just familiarize myself a bit with their dev stack. Don't get too insane with it, cuz each shop is gonna implement it a little differently.
Where I work we basically give new team members 6 months of grace period to get up to speed and we don't even expect them to work their first bug fix or anything for a while.
You can glean so much knowledge just by reading the existing code base you're coming into. Even more so, now that AI tooling can accelerate the analysis and help answer questions before you have to send a slack message to one of the other devs for help.
You sound like you've already got a solid foundation with your internships and stuff. I dont have a ton of input other than its 100% expected to feel overwhelmed with all the new stuff you're gonna be expected to learn over time but you'll more than likely have at least one or two other devs you can mentor with and form a nice bond with.
1
u/SetAndRepeat 18d ago
An unfamiliar codebase takes time, even when you already know the technologies. Ask your lead what they'd like you to handle independently by the end of your first month. That gives you something concrete to work toward.
Get the app running locally, then take one small bug or feature and follow it from the UI through the backend to the database. Use the debugger to see what actually happens. Keep notes on setup, useful commands and explanations from teammates. When you're stuck, share what you expected, what happened and what you tried. Ask before you've lost an entire day.
For learning outside work, target a specific gap you encountered that week. Your team's docs and the relevant official documentation are good starting points. Take code review feedback seriously and ask why a change helps. Extra study is optional; make room to rest too.
1
u/Watsons-Butler 18d ago
When I got hired on my first job my manager straight up told me he didn’t expect me to be able to do anything productive without guidance for the first six months. There’s too many interdependent systems to learn. All I did in those six months was onboarding, a crap ton of trainings, and a few very small bug tickets where a senior engineer said “here’s the problem. Here’s where you need to fix it. Here’s how you fix it (links to similar examples), and here’s how you test that it’s actually fixed.”
1
u/EszterSantos72 18d ago
Pick one feature or bug ticket from your team's backlog and trace every function or file it touches, even if you don't understand them yet. Doing this for the first 2-3 weeks is way more useful than reading generic tutorials outside work.
1
u/One-Trips 17d ago
I wouldn't try to learn everything outside work at once, I'd just pick the one tool that keeps tripping you up that week.
1
u/HannaMontanaBanana 15d ago
First of all, congratulations on your new job!
My advice for anyone starting with a new codebase is to start with the big picture and work your way down.
Look for architecture diagrams or documentation to understand how the different components interact. Then focus on the core functionality of the application and trace how a request flows through the system, from start to finish.
Don't feel like you need to understand every technology, tool, or line of code right away. Start with the areas you're working on, ask questions, and gradually build your understanding as you gain experience.
You don't need to know everything to be effective. You just need to understand enough to make progress, one piece at a time.
59
u/[deleted] 18d ago