In my experience, declarative APIs are very powerful abstractions for specific cases where finding the path to the declared state is better left to a machine. This is seldom the case - in most cases, offering the programmer control over the changes leads to better behaviors.

Kubernetes and IaC tools lead the way to a declarative state of infrastructure and these add a ton of value. But, they were also incredibly hard to build - it took many years before Kubernetes eventing and control loop abstracts were rock solid. Most CRD-backed implementations suffer from tons and tons of bugs, and most CRDs are not declarative - they abstract away an imperative operation! I guess this is nothing new - "anything in excess is bad".

Anyways, I think an imperative approach offers much higher control and predictability at a lower cost. The world inherently is imperative.

I'm on H-1B with an approved EB-2 via my current employer and an approved EB-1A (self-petition). I want to switch employers or take a break. I expected my priority date to become current in Q3 or Q4 2025.

Questions

1. If I switch to an H-4 status for a break, can that affect I-485 via EB-1A?

2. I need to visit family urgently and I have got a few offers in hand. Can I quit and travel internationally while the H-1B transfer is in progress and re-enter the US? My stamp expires in 6 months and my partner can mail the approved I-797. What are the general risks here apart from the mail getting lost?

3. Can a change of employment lead to issues with an AOS application in the future using EB-1A?