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:

Word is Doomed, Flawed LLM benchmarks, hard sorting and CSS mistakes Spot LLM benchmark flaws, learn why sorting is hard, how to run Doom in Word and how to say "no" like a manager.
30 years of JS, Browser AI, how attackers use GenAI, whistling code Learn how to use AI in your browser and not on the cloud, why AI makes different mistakes than humans and go and whistle up some code!
197: Dunning-Kruger steroids, state of cloud security, puppies>beer
196: AI killed devops, what now? LLM Political bias & AI security Learn how AI killed DevOps, create long tasks in JS, why 1 in 5 security breaches are AI generated code & play "The Scope Creep"
195: End of likes, JS Zoo and Tim Berners-Lee doesn't see AI vs Web Meta kills like buttons, Tim-Berners-Lee thinks AI won't kill the web, GitHub is ending toasts and the worst selling Microsoft product.

My other work: