In terms of tech labor, this means there will be more devs than now, not zero devs.

But I think devs are afraid of that too.

Not sure any established trade wants more competition.

This shift is partly driven by age‑related thinning of the posterior cingulate cortex, linking brain structure to changes in risk attitudes over time.

Check out this article for the complete breakdown: drive.google.com/file/d/19IIe...

Loss aversion follows a U‑shaped path across adulthood—decreasing in early adulthood but rising again from mid‑life onward:

Young: loss looms large → play it safe

Mid‑life: loss aversion dips → bolder bets

Elderly (60+): cortex thins, loss aversion spikes → back to caution.

But until we get it realllly humming, I still think most of my discovery activities will go something like this:

me: "Hey, who told you that?"

them: *tells me a name*

me: *searches that name in Figma search and opens the files they most recently worked on*

Yes, engineering adoption is the ultimate conversion metric, but it's a lagging indicator.

And Product docs aren't stable enough--the design process turns them inside out.

The sweet spot for design system #product-discovery is Figma.

Given we have such a strong design -> dev handoff culture, this will help us identify what stuff our core design system's team might want to build, adapt or deprecate.

And we'll do that several months faster than usual.

If you don’t like your org chart, fight for a reorg. But don’t fight for collaboration or co-ownership across the org without the proper incentives in place.