Christian Heilmann

No more “Expert, Intermediate, Beginner”: Classifying talks in Call for Papers/Conference agendas

Friday, September 6th, 2024 at 6:50 am

Old crack intro offering a level skipper for a game

I am currently working on creating the new Call for Papers for the next WeAreDevelopers World Congress and one of the feedback items we got was that levels like “Expert, Intermediate and Beginner” don’t make much sense. First of all, speakers do not choose the right level as they are worried that a beginner or expert talk will not attract enough audience. Secondly, attendees might feel peer pressure to not watch the “beginner” talk, as that might be more suited to be a workshop.

So I thought that instead of levels, I ask speakers for classifications:

  • Case Study – “How we use Kololores.js in company Blumentopferde and how it made us 30% more effective”
  • Deep Dive – “Looking under the hood of Kokolores.js and why it works so well”
  • Technology Introduction – “How Databaserandomising will change the way you think about structured databases”
  • Tool Explanation – “Taking the pain out of Kokolores.js with Pillepalle – a visual interface and API to get you started quicker”
  • Thought Piece – “Kokolores.js isn’t the answer – we need to approach this in a different way”
  • Expert Advice – “How we scaled Kokolores.js to 231242 users and what to look out for”
  • Level Up – “So you started using Kokolores.js – here is how to become more efficient with it”
  • Learnings – “How we got rid of Kokolores.js and what it meant for our users”
  • Creative – “Did you know you can use Kokolores.js to do Pillepalle?”

This should make it easier for audiences to pick a talk without having to value themselves. What do you think?

Share on Mastodon (needs instance)

Share on Twitter

Newsletter

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

Dev Digest 146: 🥱 React fatigue 📊 Query anything with SQL 🧠 AI News

Why it may not be needed to learn React, why Deepfake masks will be a big problem and your spirit animal in body fat! 

Dev Digest 147: Free Copilot! Panel: AI and devs! RTO is bad! Pi plays!

Free Copilot! Experts discuss what AI means for devs. Don't trust containers. Mandated RTO means brain drain. And Pi plays Pokemon!

Dev Digest 148: Behind the scenes of Dev Digest & end of the year reports.

In 50 editions of Dev Digest we gave you 2081 resources. Join us in looking back and learn about all the trends this year.

Dev Digest 149: Wordpress break, VW tracking leak, ChatGPT vs Google.

Slowly starting 2025 we look at ChatGPT vs Google, Copilot vs. Cursor and the state of AI crawlers to replace web search…

Dev Digest 150: Shifting manually to AI.

Manual coding is becoming less of a skill. How can we ensure the quality of generated code? Also, unpacking an APK can get you an AI model.

My other work: