Interesting points. I am also an ACM/IEEE/... member (current chair of SF Bay ACM).

I think a potential benefit to being open is providing room for mentors. As you mention, time takes time, a more curated experience to the wealth of knowledge I believe could come forward. I would happily pay for the "experts" in the field to provide a shortened and curated path through the material. More than just "read a,b, and d" but even associate study groups, etc. The new model they are taken will make this service even more important (my take).

On this front, we are attempting something of a salon on tech / society in my home town (starting with in-person and then consider being virtual as well) and hope this material will be integrated (along others).

I agree, the ACM will need to keep evolving, I am upbeat on this being open though (I create training material, while there is long term value, people want "the here and now").

While I understand the post, it misses the easy mark, showing there are alternatives. From the main site post, here is the link to an alternative source. https://archive.org/details/li... Funny enough, with Archive down and YT kicking video offline, shows why we need our own hosting.

I think the intent here is really a comment on teams and not developers per say. I get the term, but I suspect its more commentary on leveling up any role (dev, ops, manager, etc.). Saying '50 "is less performant than" vibing(10)' needs more context. Not all team members are equal in skill nor equal in responsibility (thus they don't even have a position/perspective to make a real impact). If 10 roles can "power up", and keep focus/influence outcomes, then I agree. If its just the same few power players, then not so sure. 10 developers on their own will still have lots of issues (if not just the code).

At least for myself, the Cruise app is still "offline" in SF.

Hopefully others will post their events here as well. https://gedsf.org/ (free hybrid event on 21-October).

While I suspect the sands of time have hidden some collective memory, pretty sure plenty of "real" people were at this event.

While I wouldn't normally ambulance chase, I think its instructive to show others the kinds of bugs that can hurt a service/system. Here is the related bug report for the redis-py project. https://github.com/redis/redis... Not blaming either party, mistakes happen, just a reminder of the interconnected world we live in and the risks involved.