You could do what I do and check out some existing Angular projects and see how it gets actually used. There's always a lot of "this is how the docs say to use it" and "this is how people actually use it" type stuff that you can only find out by reading code.
programming
-
Post about programming, interesting repos, learning to program, etc. Let's try to keep free software posts in the c/libre comm unless the post is about the programming/is to the repo.
-
Do not doxx yourself by posting a repo that is yours and in any way leads to your personally identifying information. Use reports if necessary to alert mods to a potential doxxing.
-
Be kind, keep struggle sessions focused on the topic of programming.
That's a good idea. I think I might burn through the official tutorial, the. Look at how people are actually using it. Do you like Angular or is it mostly just a time l for the job?
I have a deep hatred of JavaScript and only use shitty Python libraries for my job instead.
My field is more in geospatial data/drafting automation and I spend most of my day re-writing the dogshit legacy code that I have to interface with so I'm not constantly pulling my hair out lol.
Which, to be fair, will also likely be 90% of your job working with Angular as well. If you read other people's solutions though, you'll at least be aware of what it is you need to learn and what it is that people hate and you can ignore (or work around).
I'd also take any existing projects you have and try to translate them to Angular. I do that all the time when I write a new library or extendinh a library I've written to test that functionality matches and compare performance/syntax.
I do sometimes have to use a JS library for my job, but it's a super specialized library (ArcGIS Arcade) that is essentially useless and dogshit slow, but is required for specific actions. I also try to factor out as much of that as possible and rely as heavily as possible on the lowest level API granted to us which is Cursors.