Christian Heilmann

Call for Papers is open for the WeAreDevelopers Berlin and San Jose events 2026 – here’s what we’re looking for…

Wednesday, October 1st, 2025 at 10:40 am

Red rubber ducky with a megaphone stating call for papers

Alright folks, the call for papers is open for two of the WeAreDevelopers events 2026, so if you want to speak at any of them, activate the following links and enter your details and the ones of your session(s):

Here are some points on how to write a talk description that will be likely to be picked by us:

  • Talk titles we pick tell something about the topic – not just be open question clickbait
  • Good talks tell stories and describe experiences that can be repeated – not just show a solution
  • Great talks offer technology in context: “Intro to X” is good, “how we used X to achieve Y” is much better
  • Talks that are based on research are excellent, don’t just show a solution, share the journey how you got there
  • If you use ChatGPT to create your talk title and description, we invite ChatGPT and not you.
  • Avoid clichés: we had enough “from zero to hero” and “everything you know about x is wrong”
  • Describe your talk in the description, don’t describe the current landscape. “In the fast paced world of…” is a tired ChatGPT cliché.
  • Answer the WIIFM (What is in it for me) for the audience, explain what people will get away with
  • It is OK to recycle talks, it is not OK to bombard us with your backlog. Submit 2-3 talks, not your portfolio
  • Most talks are half an hour – try to focus on one topic and deliver this with context
  • Hands-on talks are great – a good code recording that works is better than live code that fails
  • Speak about what excites you – not what you think the market needs you to cover right now
  • Make it your talk – not a sales pitch for your product or service

Looking forward to your submissions!

Share on Mastodon (needs instance)

Share on BlueSky

Newsletter

Check out the Dev Digest Newsletter I write every week for WeAreDevelopers. Latest issues:

160: Graphs and RAGs explained and VS Code extension hacks Graphs and RAG explained, how AI is reshaping UI and work, how to efficiently use Cursor, VS Code extensions security issues.
159: AI pipelines, 10x faster TypeScript, How to interview How to use LLMs to help you write code and how much electricity does that use? Is your API secure? 10x faster TypeScript thanks to Go!
158: 🕹️ Super Mario AI 🔑 API keys in LLMs 🤙🏾 Vibe Coding Why is AI playing Super Mario? How is hallucinating the least of our worries and what are rules for developing Safety Critical Code?
157: CUDA in Python, Gemini Code Assist and back-dooring LLMs We met with a CUDA expert from NVIDIA about the future of hardware, we look at how AI fails and how to play pong on 140 browser tabs.
156: Enterprise dead, all about Bluesky and React moves on! Learn about Bluesky as a platform, how to build a React App and how to speed up SQL. And play an impossible game in the browser.

My other work: