参加 AI 活动之后，我想留下的不是打卡记录

最近一段时间，我常常在做同一件事：看活动议程，比较几个场馆，查有没有直播，再想一想自己到底该去哪里。

一开始，我也会被活动名称吸引。AI、Agent、科学智能、黑客松，听起来都像是值得去现场看看的东西。但当活动变多，时间和精力有限时，我开始意识到，问题不是“哪个活动更厉害”，而是“我希望从这次出门带回什么”。

如果我关心的是 AI 产品怎么进入真实场景，那么一场技术论坛、一家自动化实验室的参观、一次比赛决赛，带给我的东西就不一样。论坛适合听趋势和行业表达；参观更容易看见技术怎样嵌进流程；比赛现场则能让我观察团队如何把想法压缩成一个可展示、可评审的方案。它们没有统一的价值排序，只有和当下问题是否匹配。

所以我现在会先给自己设一个很小的目标。比如，去之前写下三个想弄明白的问题：这个产品服务谁？用户原来怎么解决？AI 介入后，哪一步真的变轻了？如果是看一场比赛，我会留意评审在追问什么、团队怎样解释取舍，而不只盯着最后的名次。

这也改变了我对“参加活动”的理解。到场不等于收获，拍照、领物料、听完几场分享，也不自动变成经验。真正有用的部分，可能是一个我之前没想到的问题，一种可复用的观察方法，或者一次让我重新评估方向的现场对话。

当然，这不意味着每次活动都要被安排得很满。有时我只是想了解一个陌生领域，允许自己听不懂一部分；有时活动内容和预期不符，提前离开也不算浪费。出门不是为了证明自己足够努力，选择不去也不是错过了某种人生机会。

我还在练习把“想去看看”变成更具体的判断：这次最想看什么，结束后留下些什么，哪些问题仍然没有答案。也许一场活动最好的后续，不是发一条热闹的动态，而是把现场看到的东西带回自己的项目和选择里，再试着验证一次。

下一次出发前，我还是会打开议程表。但我想先问自己：我现在真正卡住的问题是什么？

Recently I have been doing the same thing over and over: checking event agendas, comparing venues, looking for a livestream, and then asking myself where I should actually go.

At first, event names drew me in too. AI, agents, AI for science, hackathons — they all sounded worth seeing in person. But as events multiplied and my time and energy stayed limited, I realized the question was not “which event is more impressive,” but “what do I want to bring back from going out?”

If what I care about is how AI products enter real scenarios, then a tech forum, a tour of an automated lab, and a competition final each give me something different. A forum suits hearing about trends and industry narratives; a site visit makes it easier to see how technology embeds into workflows; a competition lets me watch how teams compress an idea into something presentable and judgeable. There is no single ranking of value among them — only whether they match the question I currently face.

So now I set myself a very small goal first. For example, before going, I write down three questions I want to answer: Who does this product serve? How do users solve it today? After AI steps in, which step actually got lighter? If I am watching a competition, I pay attention to what the judges press on and how teams explain their trade-offs, instead of only staring at the final rankings.

This has also changed how I understand “attending an event.” Being there is not the same as gaining something. Taking photos, collecting swag, and sitting through talks do not automatically become experience. The truly useful parts might be a question I had not thought of, a reusable way of observing, or a hallway conversation that makes me reassess my direction.

Of course, this does not mean every event must be fully scheduled. Sometimes I just want to get a sense of an unfamiliar field and allow myself to not understand part of it; sometimes the content misses my expectations, and leaving early is not a waste. Going out is not to prove how hard I am working, and choosing not to go is not missing some once-in-a-lifetime opportunity.

I am still practicing turning “I want to check it out” into a more concrete judgment: what do I most want to see this time, what will remain afterward, and which questions still have no answers. Perhaps the best follow-up to an event is not a lively post, but taking what I saw on site back into my own projects and choices, and trying to verify it once.

Before the next trip, I will still open the agenda. But I want to ask myself first: what question am I actually stuck on right now?