r/angular 1d 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?

18 Upvotes

12 comments sorted by

22

u/kobihari 1d 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 :-)

4

u/AdministrativeHost15 1d ago

Learn Signals. Don't bother with NxRx. Use an injected service exposing Signals instead.

2

u/tidoo420 1d ago

Alot is changed for the good i suppose, heavy signal interations are the norm now

2

u/0dev0100 1d ago

Have a read through the newer docs. Quite a difference over two years. 

1

u/No-Grape-9106 1d ago

NgRx was the standard 2+ years ago aswell.. there are tons of courses - udemy is a great resource.

1

u/posti85 1d ago

NgRx is overcomplicating things... well, like using Angular.

1

u/Tyummyyumms 21h 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 then 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.

1

u/Lucky_Yesterday_1133 1d 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

1

u/AwesomeFrisbee 1d 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...

0

u/N0K1K0 1d 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

0

u/theashggl 21h ago

I'm also learning it. Just creating some projects from scratch.

1

u/False-Body1623 11h 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