They aren't blameless, friends and family only should be the default even if you don't engage much. Why would they default it to a bunch of junk.

Yes but able bodied people shouldnt decide to use a wheelchair until their legs attrophy and become useless.

I understand the rationale, but don’t you see how this idea contradicts autonomy of decisions for able-minded people? Such good intentions tend to be a pavement on roads to bad places.

I’d rather suggest to inform about all the potential benefits and drawbacks, but leave decisions with the individual.

Especially given that it’s not something irreversibly permanent.

I'd agree but we're closer to getting forced into the chair than making a decision that's right for us

I've been very happy using cdk for interacting with aws. Much better than terraform and the like.

I second this. I do use some terraform, but for most of our stacks, CDK has been fantastic.

Or how you'll get all your data out and imported into your custom system.

Just give multiple options in the config file. Give us the current default, what you now call verbose mode and the previous verbose mode. If Claude is as effective as marketing claims then maintaining all 3 options should be trivially doable, we've been doing more complex configuration in tons of apps for decades.

I assume all ads are scams. That's easier.

Worse enough it isn't addictive. The goal is non-addictive, whatever changes to whatever part are necessary to hit that goal.

"non-addictive" isn't a well-defined thing. It's like telling McDonalds that their food must be "healthy". There's a lot of regulation affecting the food that McDonalds serves (and that's probably a good thing), but it's all based on measurable things.

We could measure it for cocaine and cigarettes couldn't we.

Yes, which is why substance addictions are in the DSM-5 and internet/gaming/social media addictions are not.

Is that what I should be doing? I'm just encouraging the devs on my team to read designing data intensive apps and setting up time for group discussions. Aside from coding and meetings that is.

This is the bad side of things like OKRs. They push you away from user satisfaction since that harder to measure, coupled with go consequences for missing them. People just force adoption without taking the product signals that come from users rejecting your changes.