Skip to main content

How long will we still look at code at meetups?

I go to a lot of meetups in my hometown. We have world-class organizers here like Juhis, people who keep the whole thing running year after year. And I have gained something from every one of those meetups, some insight from a talk, or from a conversation over beers afterward.

In recent meetups the tech talks have still been technical in the plainest sense: there is literal code on the screen, we look at it, and try to look like we understand it.

I checked this year's topics in TampereJS meetups and the titles hint towards something deeply technical. Same goes for Turku <3 Frontend talks. Looking at code is increasingly not happening in our day jobs though.

HelsinkiJS's guidance for speakers says the ideal talk is one where you share your personal experience of working on something, the challenges you ran into and how you overcame them, or a niche topic, and that introductory talks on frameworks that plenty of online material already covers are less interesting.

So talk about something you have faced, not something an LLM can blurt out.

What I expect from a talk is inspiration, maybe something that makes me say "ah, that's clever", and above all the feeling that a real human being put real effort into this and is really talking to me, not to a machine. I also appreciate it when the speaker is brave enough to show vulnerability.

The ground is shifting under us, and the value of hard-earned technical skill is deteriorating. I suppose this will show up at meetups too. Back in the day, a meetup talk could be a relatively small piece of code, something the presenter put serious legwork into. Now we don't look at the code at our office desks. Having said that, nobody wants a tour of a mega system someone built over a weekend, as we meat-proxies cannot grasp things that size in 20 minutes. 

So what is the right size of thing to stand up and present? I have no idea.

But I do know what is left when the code gets cheap. That is, of course, something the clanker won't do for us: talking to another human being and making a real connection. Perhaps the developer skill set is shifting towards connecting with people, and not only at meetups but in the workplace too. Will talking about these soon-to-be-hot skills keep audiences' phones in their pockets?

In many ways, the presentations are just an excuse to gather around a common interest. Even neckbeards gather around stories.

What will draw a crowd to a developer meetup in the future, when at our day jobs we are literally herding coding agents and nobody wants to watch that? Maybe a talk about how I helped build a stronger team culture. Maybe how I made an evening event happen, and how I built it. Maybe how I influenced my company's deployment process beyond my team and made it 15% better, and how I did it. So: talks about a human being interacting with other humans and changing something around them for the better.

And maybe, one day, a talk about how I made a real connection and built more trust. Would that fill a room full of developers on a Thursday evening?

Comments

Popular posts from this blog

Bird is causing high CPU on my macOS

There is no lack of people complaining about MacOS Tahoe, mostly about rounded corners and inconsistent design decisions. I have not paid that much attentention to that, but there is one mac bug i have paid attention to. It hasn't been a visual or ux but rather few system processes pegging the CPU. trustd , alongside with ecosystemd and ecosystemanalyticsd all reported high CPU usage. I can't exactly recall when this started, it might have predated my Tahoe upgrade but anyway, the trio of processes all had high CPU usage. Sure, it may have been the virtual efficiency cores and whether it affeced battery life or slowed down other processes i don't know to be hon...

How my work has changed in the past few years

When I started at my current job 3ish years ago, we had nothing but a few PowerPoint slides and a Figma prototype. I recall talking with one of the founders, whom I had worked with some 10 years ago, and pointing out that the very next step after PowerPoint and Figma was still the same as it had always been: translating those slides and mockups into CRUDs, forms, and other basic building blocks. Sure, all the new fancy tools and frameworks (we had jQuery then) help, but I still had to tinker with very basic primitives like tables and forms. I could not just say, "here is a table, here is a form." Well, yes, technically I could, but I still needed to write a lot of code to make a working form or table. This was around the time of GPT-3, Copilot beta, and very early Cursor. I did attempt to use them, but they could only perform very basic tasks and were pretty much useless for frontend work. We, being one of the first-wave "ChatGPT wrapper" startups has naturally pus...

Building a OTel sink that follows GenAI semantic conventions

I've been working on an OTel sink recently. To be more specific, it concerns receiving telemetry data from LLM interactions. Fortunately, there is a spec for all of this called GenAI Semantic Conventions . That is what I based my work on, so I can make assumptions about key attributes to highlight in the sink's UI, which is actually a CLI in my case. I dogfooded my handrolled sink using Pydantic AI (my favorite LLM framework), and all good, it follows the spec well. Key attributes flow in as specified. Pydantic AI also includes some of its own attributes, but that is expected. However, pick something like Claude Code, (via anthropic agent sdk), the reality is a bit different. It does not follow the spec at all. It has its own custom attribute layout . Same direction, different flavor with LangChain. The Python source has zero opentelemetry imports anywhere. None. The ls_* namespace ( ls_provider , ls_model_name , ls_temperature ) is its own thing, with LangSmith as the on...