April 17, 2026 meetup archive
A single tile for the previous meetup itself, with the gallery and overall context kept together instead of tying it to one talk.
Revisit recent meetup sessions, see how a normal evening is structured, and keep a visible record of the talks that mattered enough to preserve.
Keep this top block for the upcoming event. The current Lu.ma embed is live now and can be swapped once the May listing is updated.
Format
Networking, pizza, short shares, and practical discussion around agentic tooling in the room.
Registration
Use the embedded checkout on the right. When the next event changes, replace only the Lu.ma event ID.
A single tile for the previous meetup itself, with the gallery and overall context kept together instead of tying it to one talk.
Jan Idziak on mobile-first setup decisions, operator visibility, and what changes when the workflow leaves the desktop.
Marton Szel on where loose AI-assisted coding works, where it breaks, and how people keep it useful.
Martin Griggs on where process automation helps first, where review cost shows up, and how teams should sequence AI-assisted internal work.
Every meetup follows a simple structure: people arrive, food lands, organisers frame the room, short shares happen, and the real discussions continue after that.
Next Scheduled Meetup
The same event is embedded above, so this side card can stay as a quick note instead of another registration button.
Back to topPeople arrive, meet each other, compare notes, and the room starts to take shape before food lands.
Food shows up and conversations get less formal. This is usually where the first good side discussions happen.
Short notes from the organisers, then 5 minute lightning talks or quick sharing sessions from people in the room.
The formal part softens and the useful conversations keep going in smaller groups around the room.
"The best meetup moments usually start right after somebody stops presenting and the room starts comparing notes."