I certainly had much more time & energy for startup shenanigans in my mid 40s than I did in my mid 30s. But even with that experience I’d be very hesitant to extrapolate about any age because of how different everyone’s lives are.
I don't want to speculate too wildly, but I think it may be possible that everybody's life and energy levels and motivation and interests are not tracked on the same fixed linear path.
Though I guess it would be nice as somebody in my 20s to picture that my future is an established track to follow.
One of the setups that gives me issues is machines that are resumed from a historical snapshot and start doing things immediately, if the NTP date hasn't been updated since the last snapshot you start getting issues (despite snapshots being updated after every daily run). Most sites won't break (especially with a 24h window, although longer always have issues), but enough sites change their certs so frequently now, it's a constant issue.
Even with a 10 year cert, if you access at the right time you'll have issues, the difference now is it isn't a once in a 10 year event, but once in every few days some times.
Perhaps if TLS clients requesting a time update to the OS was a standardized thing and if NTP client daemons supported that method it would be a lot less painful?