91 karma · joined March 24, 2023
I don’t fully believe that either, but I see where the point would come from.
This is what I see motivating non-technical people to learn about agents. There’s lots of jobs that are essentially reading/memorizing complicated instructions and entering data accordingly.
For an example, take this quote:
> But that is not the whole story. In mid-life and beyond people can still experience the joy of a random meeting, however short, which somehow touches a nerve.
What exactly is the joy? Is that joy not something I can obtain more easily via the “traditional” social channels I’ve cultivated over the course of my life thus far? And won’t a social interaction in one of those channels have a much greater chance of lasting positive impact given that person is more likely to be someone I interact with regularly, enabling me to build off that initial interaction over time?
Moreover, what’s the downside of the encounter? I suspect a lot of asocial people like myself strongly dislike the much more common awkwardness and self-doubt that accompany a social interaction that goes poorly. Is enduring a lot of that really worth the few instances where you feel a fleeting sense of connection?
Putting effort into that social interaction also means I will have less energy to put into other pursuits that mean more to me: my marriage, playing piano, reading, career goals, riding my bike, existing friendships, etc.
I don’t disagree with the article necessarily, but I do think it’s mostly an “ode to random social encounters” more than a serious attempt to make a case for why people not predisposed to doing so should try to have more random social encounters.
The questions you ask in your last two sentences really get at the interesting stuff. But of course they are too nuanced and complex to answer in any comprehensive, generalized way within an easily digestible length.
To give a concrete example from my past experience, I used to work on a product that essentially knitted a bunch of services from a major cloud provider together to provide a user experience comparable to traditional HPC clusters. We never included telemetry, but we always wanted to in order to gain insight into how many compute queues people were using, how many VMs were in each of them, how many jobs were run over a certain amount of time, how many VMs those jobs ran across, etc. The sole reason we wanted this information was because the configuration exposed for this product was extremely complex, and we wanted to put layers on top of it to more easily enable the most common use cases.
Is this not a legitimate reason to collect telemetry? Is the concern that, even though the dev team wanted the data for legitimate purposes, eventually bad actors will use the capability to start collecting data for more nefarious purposes?
Edit: I see you amended the original to include a statement about opt-in opinions. What do you mean by that?
Full disclosure: this is the first I’ve ever heard of Storybook, so if there’s something particularly gross about telemetry for this use case I’m not aware of it.
Not saying the financial benefits aren’t worth it by themselves. Asking because I always figured I’d probably top out where you’re at, and I’m wondering what the view is like there.
(This sounds like a sarcastic, leading question, but it’s genuine. I don’t know this space well at all.)
The further you keep the user away from training and hosting, the less you’re in those businesses. But I would think it’s only economical to do that if you have some type of advantage in implementing the things you’re abstracting away.
Any chance you could explain this a bit more? Intuitively it makes sense that this would be as important if not more so than the modeling itself, but I have no context for the difficulties encountered when implementing it.