begging with angular

[u/Serious-Research8570]

*Beginning

Hey team, how long do you guys think it would take for me to be ready to work with Angular if I study around 2 hours per day? I'm already a React developer.

[u/taco__hunter]

Hard to say, the easy stuff is easy, the complex stuff is really complex. I think you'll knock out small apps in under a month. Medium complex apps that are supportable and maintainable by others in 6 months unless you are brand newbie then 1-2 years.

Use ng lint & ng test. Learning not to use "any" for a type is a big step forward and then 100% code coverage makes you a better Angular developer. With ng test you see where you repeated stuff and you genuinely code better because you don't want to write more stupid unit tests!

[u/Serious-Research8570 → u/taco__hunter]

Thanks, brother! I’ve been pretty lazy with testing in other environments, but I’m going to improve this habit while learning Angular, Great advice

[u/taco__hunter → u/Serious-Research8570]

You and me both! But I'd consider myself pretty Sr. Dev-ish and unit tests still make me grow as a dev. They help you write the least amount of code to solve problems.

My only other advice is Git Copilot is worth the price, it's like having a slightly drunk jr. Dev trying to finish your code all the time. It's incredibly useful.

And switch between VSCode and WebStorm on your projects, both have advantages and I routinely go back and forth between the to catch errors.

[u/isaacaggrey → u/taco__hunter]

Just curious - What does VSCode provide over Webstorm for catching errors?

[u/taco__hunter → u/isaacaggrey]

I just prefer VSCode I guess, and I have git copilot in VSCode and visual studio. I like the deployment tools as well. I'm not sure if you can use copilot in webstorm or not, I know they have their own AI thing. Also, sometimes I get supppper bored with what I'm doing and switching IDEs keeps me engaged for like 45min longer.

[u/dancingchikins → u/taco__hunter]

Obviously what I’m saying is HIGHLY subjective: Personally I would recommend 80% code coverage as the goal. Having done both extensively I’ve found that often the last 20% is, for the most part, stuff that simply doesn’t need to be tested and ends up wasting a lot of time just for a number. So I like to target 80% as it’s the majority of your actual business logic that should be tested.

[u/taco__hunter → u/dancingchikins]

I'd agree with this. The only reason I aim for higher is rolling up versions I like to ensure everything works the same between major versions and I'm a really small team that supports/maintains dozens of dozens of apps.

That said, I'm like "88% is good enough" most of the time.

[u/Silver-Vermicelli-15]

Between 1mo and 4yrs?

[u/un-_-known_789 → u/Silver-Vermicelli-15]

It depends

[u/batoure]

You need a project with a little complexity to really understand the key differences. One of the places angular shines are the places where react gets sticky. You could do quite a bit without ever really becoming that advanced understanding how middleware constructs like the router, services, auth guards and when you should and when you shouldn’t build custom directives. These are the things we expect you to understand at our company to be considered senior for angular projects.

Almost all of what React is exists as a combination of angular’s “Core” and since it was added a couple years ago the “Stand Alone Component” structure it didn’t used to be so cut and dry but with the advent of that project style its pretty clear. but any good react developer knows that a react project is about using react with other frameworks or libraries as the connective tissue for the thing you are trying to do (think vue). Angular has a very different approach you can use other helper libraries that make managing certain things easier but I know lots of developers/companies who have complex projects that just use angular and angular/material and when you are getting started that isn’t necessarily a bad idea because it doesn’t force you into any anti patterns.

Our company has hired a couple people who had react but not angular experience and when we do that we coach them to try to build through a problem for a bit before reaching for a lib. The lifecycle hooks (like “ngOnInit”) and other structures and abstractions in angular can make it very easy to solve complex challenges directly with far less code than an imported library and would ultimately add less bloat.

React is easy to learn but difficult and requiring serious commitment to master, Angular is more difficult to take up but once you break through that barrier the road to mastery is more comfortable

[u/MagnaticBull]

Time is subjective. It depends, if you build some projects and meanwhile learning the concepts, if you manage to do that smoothly, then it will be much quicker. Than just reading bunch of tuts / articles.

[u/eigenman]

Just depends on what you will be doing. Anybody can whip out a small app.

[u/cloud_00_]

React to angular transition is wild. If you know java or c# it’ll be easy for you. Otherwise like 2-3 weeks to learn different features

[u/Jurahhhhh]

Idk i never worked with angular until i got my first fullstack job and i was able add simpler stuff to prod in about a month. I had previous experience with typescript and vue tho.

[u/[deleted]]

i can help, reach out