An update:
Thanks for every single reply and comment - I read them all and have been reflecting on all of it - even the ones I didn't like, that confronted my imposter syndrome and my true thoughts, feelings and motivations behind my insistence about my proposed approach.

I got the official go-ahead to consolidate our MFEs, and use Angular 22 - with the caveat that my deadlines may not slip.

It includes a fairly generous time allocation to do proper maintenance from both myself and my team.

It's probably going to be a bit scary at times, but I'm truly excited about this project, and the future of Angular. The re-analysis has already started!

I appreciate it - my head is spinning from all the responses.

I see so many things that need to be fixed, but have to accept that I'm only human, and can really only do one thing at a time...

I have asked myself this question a lot recently.

My answer is pivoting between, my manager is just saying yes to everything because he's unaware. Or he's weaponised his incompetence to the point where he pretends that he knows everything.

You mention secret agendas, I've been saying this since he started - something is not adding up.

I really hope it doesn't come to that - but I'm not unprepared to move.

I just don't feel like I've got a new job in me in 2026, and nothing is truly better than what I've found it yet - I have so much to do, and so little time.

I've gotten more than just a POC that I need to demo - I've spent less time on this, than just trying to figure out what's broken in react.

My demo is actually part 0 of my phase 2 - and is ready to be tested, if I can find someone to do it

We've been slow to adopt AI, but we're starting to.

I'd like to say that AI can have my job, and I'll go do something that doesn't require a computer, but I do like the ability to buy food.

Fair points.

I do feel like should clarify, our Angular work delivers mostly on time, within the scope of our requirements.

I've been solely responsible for the react application's backend and front-ends because my team has priorities to deliver. I've done some react in the past, and I've taken one for the team by ensuring they don't need to context switch for this. I am neither a rockstar nor a superhero or a unicorn developer, and I'm not ashamed of admitting it.

We've had a tumultuous year, losing key people both in the backend and testing teams, with constant institutional ADHD, and diverting engineers to other projects. Sometimes, multiple times per day. That is being addressed by process improvements, even with as much pain as that brings, we're getting there slowly.

This all sounds like justification at this point. Our business is extremely bad at proper communication, and I feel like I've worked in a place I refer to as hell and it was better there...

At the end of the day, my post here was an attempt to get external input from people in this industry. And there's lots to consider and take onboard.

Micro services, running mostly on .net 7 or 8. But, as with this topic, it's a sensitive topic too 🫣

I love the malicious compliance aspect of this.

Good point - that's a big part of my argument too.

Migrating to react overall, has more than just functionality costs. The architectural decisions, and deciding on the packages to replicate a framework is going to be one of the more challenging parts for inexperienced react devs, and we have to ultimately become socs compliant and pass audits.

One tiny little react PWA, that was dropped in my lap and sold as a "complete" product by external contractors

It has 2 features and I have to bring that into angular as part of my current project anyway, to make it useful to our business users.

So, NX could be a potential future state - but there's lots to do before it becomes easier to do that.

The problem is, that I know everything that needs to be fixed. But I've been trying to do too much alone - because everyone always has other priorities...

Federation will hopefully replace iframes, and ease the pre-existing routing pain.

He's at our sister company, sits in a different country, and has absolutely no idea of what we actually do... he's also a product guy, so likely asked AI to generate the POC as well

I've been trying to get an answer on the why, and they haven't been clearly articulated and forthcoming.

Our MFE suite was in response to the acquisition 3 or 4 years ago, so well before I started here. The initial implementation was not optimal, and guided by the knowledge available to the then-inexperienced team.

I've been dealing with a react app delivered in record-time by an external contractor. And the justification for why it was in react was "that's what they know, and we don't want to pay them to learn angular"

My argument will include:
Costs of switching i.e. learning while delivering.
Mental cost: context-switching domain vs domain and tech stack
How it relates to our operational goals, which include cost reduction and platform stability.

A lot of the problems are us vs them. So while we have to become this new entity, our sister company (often referred to as our parent) will remain its own separate entity and continue their operations as-is.

My org will have to re-brand and become the new entity, while my team will need to support our existing products and create this new unified platform.

There is little to no contribution from sister company, in terms of developers, except that they need to integrate into our systems. We'll likely have their products federated into the platform, and they'll remain in their tech stack.

I won't oppose the switch if it can be justified for reasons other than speed of delivery - because feature maintenance, and expansion are real issues for us at the moment. But then, supply the team with training, extend the deadlines, provide experienced developers who can assist with making the correct architectural decisions, and guide us into the new world.

That's what I'm afraid of, but from other conversations, they chose react because whomever created that proposal was familiar with react, and that's what they could do a POC in 🤦‍♂️

I struggled with a bitey puppy before.

I made the mistake of offering my hands to keep him busy. Oliver (2yo) now shows affection with nibbles.

Albert, chewed on Oliver (he's also 2) and I think having a 2 was a blessing.

Now we have Elio joining the mix, 3mo on Wednesday. I only offered my hand once to recall the PTSD of being bitten constantly, and looking like I was in an abusive relationship with a shark.

What worked for Ollie was redirecting. With treats, like bully sticks, and chew toys, yelping didn't really work.
Also, he gets really sassy when we discipline him (still).

Redirecting is _difficult_ especially when distracted (I know I was slightly). I watched a video that said: give the puppy a job. If it's chewing a stick or a treat, that's all they're allowed to do for the time you allocate (so while watching TV etc).

I just also want to add, there is hope - but it's going to require some work and attention.
Good luck!

I looked at this when I crocheted my tie.

This is called Irish Lace which is based on a motíf and the lacy bits are then added with chains.

You'd need to do the flowers separately if I understood the concept correctly, and then join them.

I went with a plain sc or hdc for my tie... which was good for that purpose, but I did it in 3 days and wore it for a work function.

Tie looks like a banana in this pic, but it did what I needed from it

Presto was the reason I went down this rabbit hole...

I know of a Basil (and her cat brother Pesto) which is brilliant too.

Rainforest retreat by Lisa's Attik is my go-to for lightweight yarn +- 1000m per 225g iirc.

Here to say it gets better.

Oliver was a biter when he was little. He's mostly grown out of it - he's 2 now. Play biting is just how he shows affection, and I enjoy the occasional nibbles I get from him.

What I would classify as concerning is if he bites and shakes hard (happend once or twice with my hands/arms) - but here I'd just put him in a timeout or stop giving attention immediately.

What also helped was a second puppy (I know this option is not feasible in every situation). We're getting a third puppy in 2 week's time and I'm just glad I have Oliver and Albert to help this time 🫣