But how would you do what in Rust's Tokio is a `spawn_blocking` in Swift?

In Cursor you have Sandbox mode to deal with that issue?

I feel more like is forcing to write better engineering not just the code.

The disruption comes from the economics of cognitive labor, the synthetic assistants are making feasible things that before were unbearably cognitively costly so manually we invested all that energy into the code parts.

I've made this to leverage that:

https://github.com/sebastianconcept/ai-squads

Isn't plenty of space of efficiency value in SaaS over AIs? And depending on the use-case and what the optimization is, also performance?

Only depend on platforms as redundancy. Never as primary source.

Break that discipline and you are exposing yourself to this danger.

The issue is that one of the services is the events hub for the rest to remain in loose coupling (observer pattern).

The criticality of Kafka or any event queue/streams is that all depend on it like fish on having the ocean there. But between fishes, they can stay acyclicly dependent.

Okay yes, agree. This goes inline what I do and promote among teammates all the time "maintain one-way dependency discipline".

Tree or not, it will render you acyclic graphs.

> Why vibe code with a language that has human convenience and ergonomics in view?

Because you would not be able to audit the code if you don't (you'll be terribly slow to read and understand the inner flows correctly and that's if these aren't so bad that would do you some brain damage).

Dang, AI is pushing us all to become managers.

The reports about our death were greatly exaggerated.

Well we need like successful technological disruptions like in 7 dimensions before this can be scale and ROI positive.