It should be legal. Caveat Emptor applies always. to everything. I'd rather have choices available in a marketplace rather than a nanny state stifling innovation through its own incompetence.
Not to chastise you or your wife, there is an actual "Liver Warning" on Tylenol Product labels. They warn against 4000mg/day or with alcohol consumption. It's not an on/off switch, the damage occurs on a ramp that achieves a critical point after so much consumption.
Saying this to encourage label reading and to refute those who might try to characterize your wife's experience as anecdotal. And for those who stop reading a page like this one, after the first paragraph that touts "no evidence": https://www.tylenolprofessional.com/safety-and-efficacy/safe... when at the bottom it reveals the Liver Warning.
To me, this is no different than the c/c++ crowd screaming "But you need to understand types and memory management" to the Type-safe Managed Memory Language crowd.
Problem solving remains the primary skill. You're just working in a different medium. Instead of code, it's design and specification (which you should have been doing in the first place instead of firing it out on demand as fast as your fingers move and insisting your teammates get in the groove).
If you're worried that you won't be able to understand why generated code isn't behaving properly, pro tip: Ask mode > ask the LLM to map possible reasons why the code does this when it should be doing that. Your ability to target the 'right' problem area earlier vs later is a matter of experience, as it always has been.
And you have to spend more time being intentional about setting up context / rules to define your application-specific design patterns.
For the young-uns, they need to learn their own way to leap frog over the paradigms we were trained on. We should be honest with them and ourselves that those paradigms are obsolete. As is winding core memory by hand. As Musk has said, one day there will be no apps, just a model. We're not there yet but this is the future.
Nah, you need the 405 Method Not Allowed to be returned by legacy systems and proxies along the way to your bleeding edge server rather than silently failing whilst dropping the params in the request body.
Win95's ability to host multiple VMs was marginally better than Windows/386. It was a step in the right direction with the new driver architecture and elimination of TSRs (TSR-to-95 porting was one of my roles bitd). Just a baby step though, you could be just as rude in a '95 driver as a DOS TSR.
I get the microservice to ensure this. But 3 people dedicated to it? I guarantee you they spent their days trudging dungeons, playing CoD and ping pong.