I think the best reading on the fundamental afflictions that affect society is in Han's Burnout Society.

So thinking about loneliness and alienation is really easy through the lenses of the hyperpositivity and the rise of narcissism. Suddenly these are all aspects of the focus on the individual and the "You can" ethos.

> too many people feel that nobody sees them as a fellow human being

It's really hard to feel seen when everybody only interacts with everybody else if it serves their own project of self improvement.

> versioning is a bit confusing analogy because it usually additionally implies some kind of improvement

Exactly what I felt. Semver like naming analogies bring their own set of implicit meanings, like major versions having to necessarily supersede or replace the previous version, that is, it doesn't account for coexistence further than planning migration paths. This expectation however doesn't correspond with the rest of the talk, so I thought I might point it out. Thanks for taking the time to reply!

It's something that frustrates developers, spits out terrible pull requests and only fixes bugs by introducing new and exciting ones.

But it's something that you can put in your company's portfolio to attract VC capital.

It's a terrible tool that makes a lot of money for the corporation.

It's fine, but it wouldn't hurt to have a more formal alias like `docker push-over-ssh`.

EDIT: why I think it's important because on automations that are developed collaboratively, "pussh" could be seen as a typo by someone unfamiliar with the feature and cause unnecessary confusion, whereas "push-over-ssh" is clearly deliberate. Think of them maybe as short-hand/full flags.

I think it's interesting to juxtapose traditional coding, neural network weights and prompts because in many areas -- like the example of the self driving module having code being replaced by neural networks tuned to the target dataset representing the domain -- this will be quite useful.

However I think it's important to make it clear that given the hardware constraints of many environments the applicability of what's being called software 2.0 and 3.0 will be severely limited.

So instead of being replacements, these paradigms are more like extra tools in the tool belt. Code and prompts will live side by side, being used when convenient, but none a panacea.