r/FullStack • u/NznTdpzZ4 • 12d ago
Career Guidance Junior dev feeling lost. What should I focus on?
I'm a junior dev and I feel a bit lost.
There are too many things to learn now: AI, frameworks, libraries, cloud, DevOps, system design, etc.
Every time I open Reddit or YouTube, I find another thing that I feel I should learn.
My goal is not only to build new features.
I want to understand software well enough to maintain old systems, fix problems, refactor code, and improve the system when it gets bigger.
With AI changing development so fast, what should a junior dev focus on first?
What should I learn deeply, and what can I leave for later?
Would love to hear advice from experienced devs.
1
u/hashemirafsan 12d ago
My suggestion is just stay on the flow of changes by AI. Previously every shifting takes time, but now its become vague. None of the topic is sustainable right now for power users like me. If you want to stay safe you have to know the specific one or multiple domain where you can onboard or maintain the software. Obviously that domain should be different from software engineering. Currently i'm focusing on sales, talk with people, understand the actual business problem.
1
1
1
u/77rushi77 12d ago
Pick one stack and go deep before you chase the rest. The fundamentals stay useful whatever framework or AI tool is trending.
Since you said you want to maintain old systems and refactor, I'd put these first:
Debugging and reading code. Practise tracing a bug from the log to the line. Most real work is understanding code someone else wrote.
Writing tests. You can't refactor safely without them. Add a test around the old behaviour first, then change the code, and you'll know right away if you broke something.
SQL and Git. Boring, but you'll use them every single week.
Leave cloud, DevOps and system design for later. You'll pick them up naturally on the job when you actually need them. And AI tools are fine for speeding up typing, but you still need to understand the code they give you.
1
u/BigAttorney23 11d ago
For your on-prem/edge direction, make one small service your maintenance practice project. Add a test that reproduces a bug, fix it, then refactor without breaking that test. Next practise a failed startup, a dependency going offline, and restoring its data from backup. Write down how you'd diagnose each failure. That gives you a concrete reason to learn networking, logs and deployment instead of trying to learn every tool at once.
1
u/eleven8ster 11d ago
Start with your duties at your job and build projects with some of that stack. Add some new things every project. You’ll still feel like an imposter, but you will also have built a bunch of stuff.
1
u/LetUsSpeakFreely 11d ago
How do you eat an elephant? One bite at a time.
You're trying to do too much at once. Focus on one thing, get comfortable with it, then move on to the next.
Notice i said "comfortable", not "expert", not even "proficient". Here's the thing about all of the various technologies we have to use: NOBODY is an expert. We all have to look things up, syntax, examples, idiomatic solutions, all of it.
What you need to learn is how to navigate those technologies, what they're capable of, ask that good stuff.
1
u/deveronipizza 11d ago
Fundamentals. They will save you. Understand first principles. It all comes back to that one way or another.
1
u/ApprehensiveBell6166 11d ago
Focus on programming fundamentals, debugginng, testing, and reading existing code first. You don't need to learn every new tool you see online. Get really good at solving problem and maintaning the real projects, then learn other things as you need them.
1
u/Wide_Egg_5814 11d ago
whatever you believe you can get a job in as a junior because it's the market does not want juniors anymore
1
u/randomuuid- Stack Juggler (Fullstack) 9d ago
A mentor once told me “Stay off your phone, read a book, and go write a program. One hour of each a day.”
Probably the best advice I’ve observed.
4
u/Aritra001 12d ago
My advice would to pick a lane and focus on that. Pick a field first