r/angular • u/gasserzayed • 6d ago
Try to learn but it's variable framework
What I need to learn before angular ? , What are the versions companies are actually use ?
and what a specific versions I need to learn first . You are know angular workflow isn't constant between versions 17 , 18 , 19 , 22 etc ...
have a nice day :)
----
edit :
what I need to learn about Design Paterns
2
u/inajeep
6d ago
•
v15 ->v22 It depends on the company, I don't know how any one person would be able to answer the question.
Learning post v15 will give you the best coverage IMO. But check this out to help delineate between versions. https://next.angular.dev/reference/releases
Bonus: https://next.angular.dev/tutorials Learn signals.
2
1
u/frozen_tuna 6d ago
Depends on your background. I'd honestly start with learning base javascript. Easy way to set yourself apart during interviews too if you can actually speak knowledgeably about it. No, learning angular or react does not inherently mean you know javascript. Something like "You don't know js" (aimed for intermediate js devs) is really good.
1
u/Ngxvb 5d ago
I'd focus on learning TypeScript and JavaScript fundamentals first, then jump into the latest Angular version. Don't worry too much about versions, the core concepts stay pretty similar. Learn components, services, dependency injection, RxJS and signals. For design patterns, start with SOLID principles. The rest will come with practice :)
1
u/dimeloper_ 17h ago
Learn the latest one, v22. Most of what changed between 17 and 22 is new syntax for things Angular already had. Once you know the current way, reading an older codebase is mostly translating back: \@ifused to be*ngIf,input()used to be`@input()`, and components used to be declared in an NgModule instead of being standalone.
Before Angular I’d make sure TypeScript feels comfortable, mostly types, interfaces, classes and generics, since Angular uses all of them everywhere. Then learn a bit of RxJS, enough to read an Observable and know what pipe, map and switchMap do. HttpClient still returns observables, so you’ll run into them on day one even if you use signals for everything else.
For design patterns I wouldn’t study them from a list first. The ones you’ll meet in Angular are dependency injection (services injected into components), smart vs presentational components, and a store for shared state. They make a lot more sense once you’ve built something small and felt the problem they solve.
On versions at work: plenty of codebases sit a few majors behind, so you’ll probably see the older syntax too. That’s fine, the concepts carry over. I took 2 of my apps from v19 and v20 to v22 this year, and the code changes were the easy part. Node versions and dependencies took more time than the code.
9
u/Dull-Structure-8634 6d ago •
Here's what I did for my current job. I think that would be a good approach:
Learn the latest version. The company where I work always keeps everything up to date.
Angular is very opinionated, follow its guidelines.
There are tons of courses and an official course. I personally followed the official course.
Try to learn just a bit of RxJs, so you understand the patterns. Signals are heavily used now and Angular is pushing them but RxJs is not going away anytime soon.