The deck is the source
This was a meetup briefing built from presentation slices. The article should not pretend to be a transcript. The useful object is the deck, with a short note explaining why the sequence mattered.
The April 22 session moved from agent productivity stacks into model and infrastructure choices. Self-hosting, Kimi, Claude, Qwen, RunPod, and weekly AI news were all ways of circling the same practical question: what does a builder need to own directly, and what can be rented or called as a service?
That frame is more durable than the individual release notes. The exact model names will keep changing. The placement problem stays.
What carried forward
The practical takeaway was a mixed-stack mindset. A local model can answer small private questions. A budget API can cover medium tasks. A rented GPU can handle focused heavy sessions. A frontier model still earns its place when the work needs judgement, long context, or high quality synthesis.
The problem is not choosing one permanent winner. The problem is knowing what the work needs before the tool choice becomes habit.
The replay is attached because the deck shows the transitions between those choices. It is more useful as a working sequence than as a list of isolated headlines.