On Conferences: What's Worth It and What Isn't

I have attended a lot of technology conferences. KubeCon, AWS re:Invent, Google Cloud Next, a number of smaller specialist events. The pattern I've noticed is that the value of a conference correlates weakly with its size and strongly with the people you are already going to talk to when you arrive.

The sessions are mostly not the valuable part.

This is not a criticism of conference talks. Some are excellent, and the best ones — a genuine practitioner sharing hard-won lessons from a production environment, a researcher presenting findings that challenge a common assumption — are worth the time. But the median conference talk is a polished version of information you could have found in a blog post.

The large conference sessions at the major events are often marketing. The vendor-sponsored talks are marketing by definition. Even the community talks are optimized for the format: 40 minutes, a narrative arc, memorable takeaways — which is a format that rewards certain kinds of knowledge (lessons learned, opinions, frameworks) and underserves others (nuance, ambiguity, genuine uncertainty).

What is actually valuable at conferences:

The hallway conversations. The person you end up talking to after a session, or at lunch, who is working on a problem adjacent to yours. These conversations are unstructured, honest, and often produce more insight than the sessions because neither party is presenting — both are thinking aloud.

The people you already know. A conference is a time-boxed excuse to have in-person conversations with people you have been in professional contact with remotely. The investment in those relationships — which compounds over years — is worth the trip cost.

The single workshop or working session where a small group actually works through something together. These are rarer but consistently the highest-value conference format I have encountered. A problem, a room of practitioners, structured discussion. The output is not a slide deck; it is understanding.

What I've stopped doing at conferences: attending sessions because they are on topics I "should" know more about. The sessions that land are the ones where I have genuine context — where I can evaluate the claims, recognize the gaps, and connect what is being said to problems I've actually encountered. Attending sessions to acquire basic literacy on a topic is an inefficient way to learn that topic.

What I've started doing: attending with a shorter list of people I want to talk to, leaving more unscheduled time, and being willing to skip sessions for a good conversation.

The conferences I value most now are smaller, more focused, and less polished. The conversations are more candid when there is not a vendor sponsor to offend. The speakers are more willing to say they are uncertain or that something did not work. The format is less optimized for appearance and more for exchange.

If the choice is between a three-day mega-conference and a two-day focused practitioner gathering, I will take the smaller one most of the time.

Working on this in production?

We do this work directly alongside engineering teams — architecture review, migration, and hands-on enablement.