I love working with React... So WHY am I switching to Angular? Part 3

Ok, here goes part three of why I've chosen to go with Angular for my next project. If you're growing tired of me promising an answer with every post - see here and here - I don't blame you. Heck I'm growing tired of it and I already know the answer.

To finally get why the switch, I think it's important to tell you what I'll be building.

Some background

The wife and I have decided we want a change. The time has come to look for greener pastures in another country... we're moving to Canada.

But getting there is going to take some time - Express Entry takes at least 6 months to complete and we can start the application in November - which is when we will be writing the mandatory English exam.

In the meantime I have to start looking for potential places of employment - and what they'll require of me. Lo and behold, it seems as though pretty much every position advertising wants at least familiarity with Angular...

Interesting but not that surprising.

Why all the love for Angular... where is React

To be fair, there are plenty - and by plenty I mean several hundred, maybe thousand - opportunities for React only developers. You might even get an Angular job if you have enough experience and the right attitude. But to me at least it looks as though Angular is a favourite amongst organisations.

The reason I believe is because Angular sets itself up to work well with multidisciplinary teams. For the most part, the templates and styles can be made by a designer. Angular ships with a neat way of splitting everything up in modules and using dependancy injection to connect the modules together again. All of this makes Angular lend itself out to be a good team player.

Again, it's not that React cannot be used in teams or cannot be separated into independent modules. It's just more work to setup, and that means more documentation to write and more time needed to train newcomers to the team on how the project is structured. Angular is already documented and hiring someone that already knows how Angular works means it's less time training and more time building features.

What project will I be working on

Well... since I'm going to potentially start job hunting in the mid-future, I'm going to need an up to date resume. So while doing a Google search on how to write a good resume - instead of actually writing the resume - and more importantly trying to figure out what is the best order to place the sections of my resume, a thought came to me...
What if I don't have to worry about the order? What if I just send a link to a recruiter and they can order everything the way they want to? And for good measure add filters to hide what they deem unimportant. This might just be useful...

So then I thought, since Angular is well suited for teams and employers, I can build this "Web-Resume" with Angular. This way I
might be doubly prepared for a new potential employer - Angular experience and an online resume.

So there you go. The reason I'm learning Angular is so companies will find me more employable...

Really!? That's the most boring reason there is. You kept us in suspense for weeks now for that...?

I never said it would be interesting, just that I would share why.

Anyway... hopefully you learned something through the course of these posts.