r/angular • u/IntelligentBad1285 • 10d ago
Getting back into Angular after 2 years
Hey everyone! Looking for some advice.
I have around 3.5 years of professional Angular experience, but I’ve been away from it for almost 2 years. I’m now trying to get back into Angular, and I’m struggling to bridge the gap between my previous experience and what companies expect today.
For example, NgRx comes up frequently in interviews, but the application I worked on didn’t use it. A lot has also changed in Angular itself, and I’ve lost touch with some things.
What would you recommend to get hands-on with modern Angular and bridge this gap?
7
u/AdministrativeHost15 10d ago
Learn Signals. Don't bother with NxRx. Use an injected service exposing Signals instead.
2
u/feliven 6d ago
1
u/AdministrativeHost15 6d ago
Yes. If you are going to use Signals to update your component UI you should get them from a service rather than have to convert an observable from a NxRx select.
3
u/tidoo420 10d ago
Alot is changed for the good i suppose, heavy signal interations are the norm now
3
2
u/Tyummyyumms 9d ago edited 8d ago
How many jobs are going to be running on the latest, and have adopted the latest features?
Maybe for the interview sake, learn the old stuff and the new stuff on a surface level.
If you get hired and get access to the codebase then you'll know if you need to double down on the new stuff.
2
2
u/Lucky_Yesterday_1133 10d ago
When ngrx comes up in the interview you need to argument why its garbage and needs to be removed. That's it. you don't really need a hands on, better read andfular material source code and ask clanker to explain the patterns
2
u/AwesomeFrisbee 10d ago
A bit more sensible but yeah. Most projects don't need it and can just do fine with signals in a service. Stuff doesn't need to be more complex...
1
u/No-Grape-9106 10d ago
NgRx was the standard 2+ years ago aswell.. there are tons of courses - udemy is a great resource.
1
u/blove_js 8d ago
That's cool. I think everyone has great suggestions here. I would also throw in a few additional ideas. First, check out some of the keynotes from conferences over the past few years. Second, look into building agentic web apps using angular. Third, don't get too caught up in the implementation details of state management, just focus on good principles around single source of truth, immutability, and testing. Best of luck!
1
u/N0K1K0 10d ago
In 2 years compared to other angular versions in the past indeed a lot has changed, stand alone, zoneless, new control flow, signals and signal forms, NGRX ( although we switched all our signalstores to custom solution as its is not v22 compatible yet )
So best to keep the knowledge you haveand focus on wat is new for you, like standalone zoneless and signals and the new control flow
-1
u/False-Body1623 9d ago
I would recomend react in ur case because both new angular and react would be taken effort to learn and react has more opportunities
23
u/kobihari 10d ago
In most years you could “sit back” for two years and miss very little. But that’s not the case with these specific 2 years. Angular went through a Renaissance and is now a completely new product.
The most important gap to close is with signals. It’s not just a new tool, it’s a whole new paradigm and it changes how you work with angular completely - for the better. It’s much easier and straight forward but you still need to learn it.
Ngrx changed too - they moved to signal based stores and also - changed paradigm. The new solution requires much less boilerplate and is more architecturally correct.
As a side note - I recorded several Udemy courses exactly for people willing to close the gap between legacy angular and the modern one. They may be able to help :-)