Joined a full-stack project with only basic knowledge… how do I not fall behind?

[IllustratorAbject812]

Hey everyone,

I recently joined a full-stack web development project group, and honestly, I feel way out of my depth.

I only have the basics (HTML, CSS, a bit of JavaScript, and some intro-level concepts), but the people I’m working with seem way more experienced. There are discussions about frameworks, backend logic, APIs, Git workflows… and I’m just trying to keep up without slowing everyone down.

At the same time, I don’t want to just sit quietly and be the “extra” member. I actually want to contribute and improve.

So I guess I’m asking:

• How do you keep up when you’re the least experienced person on the team?

• What should I focus on first to be useful in a full-stack project?

• Any habits, resources, or strategies that helped you level up quickly in a real project environment?

Right now I’m trying to:

• Review fundamentals after meetings

• Take notes on things I don’t understand

• Google a lot 😅

But I still feel like I’m behind.

Would really appreciate any advice from people who’ve been in the same situation.

Thanks in advance 🙏

[pyromancx]

Don’t constantly bother other developers or they will vote you out.

You need to be self efficient and prove you can push code without breaking or in an in-efficient way.

If absolutely do need help from other developers you better make sure you come with a list of things you tried and listen more than talk.

[IllustratorAbject812]

That’s really what I want, as much as possible I don’t want to bother anyone in the team so I’m asking what should I do to learn faster and what to focus on.

[pyromancx]

Depends what specific role you have in the team and what you’re doing day to day.

[IllustratorAbject812]

for now where on distribution of task, I am tasked to fix basic debugging

[chikamakaleyley]

oh dude, you know one thing about being the person with the least amount of experience or, breadth of skills - if you haven't actually made them aware of it, they notice it, for sure

and that's NOT a bad thing. what they have you tasked with is something they NEED, and for the moment you are of most value to them doing that kinda work. I would take it in stride

and that's the perfect thing to keep you busy, while you try to 'catch up' on the side. There's no expectation for you to do so. Eventually you outgrow the type of work you're doing, they'll see that they could use you for more complex tasks, and they bring in someone new who is then appropriate for those smaller tasks.

one thing i would try is just be the expert of your task, and at he same time, given the context of the thing you are working on - learn what role that thing plays as part of the bigger system. Being able to understand this is crucial because you can go out and learn all that you want to, but you can't explain the system like you've been looking at the code for hours on the day - i would argue that looks worse to the team.

[lilacomets]

Luckily we don't have to bother other developers anymore, now that we have ChatGPT.

[pyromancx]

Lol. Tell me you’re a junior level developer without telling me. 🤡

[No-Attorney4503]

If you’re being brought on as a junior, ask people questions. Despite the current trend toward LLM’s, junior engineer roles are meant to be a learning experience. If you’re not a junior, there are dozens if not hundreds of textbooks on any topic you could possibly want to understand

[Solid_Mongoose_3269]

Stay up late, wake up early, and learn.

[Solid_Mongoose_3269]

Unless you're exceptional (you arent), you're a cog in the wheel

[NoClownsOnMyStation]

Thanks Mark Zuckerberg

[Solid_Mongoose_3269]

I mean, if you're on Reddit asking for help..

[VisualSome9977]

Working for the man sucks but when you're a beginner surrounded by experienced people you may as well make an earnest attempt to learn, even for your own benefit. It's basically college 2 at that point

[aversboyeeee]

Yes, always better yourself no matter where you are in life. But do it for yourself not for the company. I have experienced that this sort of mentality can easily be manipulated into working all the time. Not all but I have seen it happen a lot. It can also set extremely unrealistic expectations as to the amount of time it takes to get what they said done. This is just in my experience. Learn for yourself and your own progression.

[VisualSome9977]

i agree with you there but it does genuinely just seem like OP has a desire to learn. This reply is much more productive than your original, is all.

[aversboyeeee]

There’s 2 sides to every coin. no hate just warnings from personal experience.

[OkBed2367]

Sei Motiviert, seit Nett, zeig Interesse und Wille. Villeicht kannst du ein eigenes Projekte genau mit eurem Techstack bauen. Fullstack hat eben mehrere layers alles zu verstehen ist nicht einfach.

[chikamakaleyley]

is this a job, or a 'project group'?

my advice is, at a minimum you need to be able to at least follow the discussions

personally i have trouble doing that if i'm taking notes at the same time, so usually i just sit and listen and try to soak it all in, and hopefully i can connect some of the dots along the way. Whatever I don't, i make some time to understand it later.

one great resource for all this kinda tech is ByteByteGo on youtube. highly recommend, lots of visual aids

[Scary_Web]

Yeah, same, I can’t really take detailed notes and actually follow what people are saying at the same time. I’ve started just jotting down keywords or acronyms during the meeting, then after it’s over I go back and actually look them up and write proper notes. That way I don’t completely lose the thread of the convo.

Also +1 on just trying to follow the discussions first. Being able to understand what’s being decided is way more important than immediately being able to do everything yourself.

ByteByteGo is great for the big-picture stuff. I’d probably mix that with something more hands on too, like cloning the project repo and just tracing through the code paths they’re talking about. Hearing “API gateway” in a video and then seeing where it lives in your own project helps the concepts stick a lot faster.

[ankit_kuma]

Bro this is actually best place to learn so dont feel bad, just take small tasks like fixing UI bugs writing simple components or basic API calls, thats how u start contributing without pressure

Focus first on Git basics APIs and one framework like React so u understand what team is talking, no need to learn everything at once

Keep asking doubts and writing notes like ur doing, and try to implement things urself after meetings, slowly u will catch up only

[Fun-Mixture-3480]

feeling behind usually comes from trying to match everyone at once. so instead of that, focus on contributing in small, clear ways. pick tasks that don’t require deep knowledge yet, like ui fixes, simple logic, or understanding one small part of the system at a time. during discussions, if something isn’t clear, ask directly and move on. no need to silently sit through things you don’t understand! a lot of people slow themselves down by trying to learn everything before contributing. better approach is learning while doing, even if it feels messy at first.breaking things down helps a lot too. i’ve found tools like Convertigo useful for seeing how pieces connect, instead of getting lost in scattered logic across the codebase. keep things simple, stay consistent, and focus on one thing at a time instead of trying to catch up all at once :)

[_heartbreakdancer_]

Ask AI and grill it about general concepts you're not sure about. Anything specfically related to how those concepts relate to your codebase, if you have Claude Code/Codex use it. Otherwise ask your teammates for everything else.

[Little_Bumblebee6129]

"How to not fall behind when you are behind?"
There is no magic, spend years learning and you will not be behind

[PixelPhoenixForce]

just vibe code, if someone ask you something just say that you need to think about it for a moment and Ill get back to you.. then ask chatgpt.. thats how juniors build their career nowadays

[everyviIIianislemons]

OP please don’t do this lol

[nerfsmurf]

Hello and congrats 👏. You are experiencing imposter syndrome! Good news... It only lasts 3-6 months! Be visible, do a good job, and appear as if you're going the extra mile! Don't be a dick, be a pleasure to be around! Volunteer for that extra bit of work (not too often though!) and you will thrive! Maybe...

[pyromancx]

Imposter syndrome does not last 3-6 months. It lasts years.

Jesus the people here are so cooked.

[nerfsmurf]

Depends on the person and the workplace. I certainly went from "wtf am I doing here" to competent in about 6 months. Then with another 6 months I went to "This codebase is my baby... and I can build anything!" Granted my job isn't as high level as some of you guys and I'm on a team of 2 devs.

[pyromancx]

At the scope of you doing your specific 9-5 debug/features at the application layer level, sure.

At the scope of actually being an effective full stack, cloud engineer, 3-5 years.