No, it's about perspective - I know that 'cos I wrote the article, but perhaps it didn't come across very clearly!
Here's the specific problem that advice is intended to remedy, which I have seen happen many, many times:
Somebody writes a talk about, say, what's new in C# 13. It's a solid talk: they've done the research, they've prepared some good demos. At local user groups, it does very well. At regional and community conferences, it does very well.
But it doesn't have any personality. It's not a case study. It's not based on using those features in production, or applying them to a specific domain. The presenter has read all the docs, run all the examples, maybe found an edge case or two, and put together a decent slide deck and some engaging demos - but even if they've done a fantastic job, there are a thousand other tech presenters out there who could do exactly the same thing.
They then start submitting that talk to big conferences which have a .NET track, and it never gets accepted.
Why? Because those conferences have people like Mads Torgersen, the actual lead designer of C# at Microsoft, on speed dial. If NDC Oslo or CraftConf or Yow! wants to fly somebody in to talk about what's new in C#, they can get the person who wrote those docs to do it.
Now, consider that talk was "how I used C# 13 to rebuild my smart home dashboard", or "how my team used C# 13 to save $5000 a month in AWS bills", or "I built an online game server using C# 13". Those kinds of talks do well because they have personality; there's more there than just the technology itself.
That's what I mean by "a story nobody else can tell" - it's a presentation that's anchored in the speaker's own real world experience; detail and context that hitherto only existed in their head.
I run presentation workshops for software professionals, and one of the things I ask my students to do is to come up with something - doesn't have to be tech-related - that they know better than anybody else in the group. We've had folks talk about how to cook ragu, how to surf on a longboard, how to get their kid to fall asleep ("literally nobody else in the world can do this, not even my wife"), and it is always remarkable to me how much more engaging and animated people become when they are telling their own story rather than paraphrasing research.
Here's the specific problem that advice is intended to remedy, which I have seen happen many, many times:
Somebody writes a talk about, say, what's new in C# 13. It's a solid talk: they've done the research, they've prepared some good demos. At local user groups, it does very well. At regional and community conferences, it does very well.
But it doesn't have any personality. It's not a case study. It's not based on using those features in production, or applying them to a specific domain. The presenter has read all the docs, run all the examples, maybe found an edge case or two, and put together a decent slide deck and some engaging demos - but even if they've done a fantastic job, there are a thousand other tech presenters out there who could do exactly the same thing.
They then start submitting that talk to big conferences which have a .NET track, and it never gets accepted.
Why? Because those conferences have people like Mads Torgersen, the actual lead designer of C# at Microsoft, on speed dial. If NDC Oslo or CraftConf or Yow! wants to fly somebody in to talk about what's new in C#, they can get the person who wrote those docs to do it.
Now, consider that talk was "how I used C# 13 to rebuild my smart home dashboard", or "how my team used C# 13 to save $5000 a month in AWS bills", or "I built an online game server using C# 13". Those kinds of talks do well because they have personality; there's more there than just the technology itself.
That's what I mean by "a story nobody else can tell" - it's a presentation that's anchored in the speaker's own real world experience; detail and context that hitherto only existed in their head.
I run presentation workshops for software professionals, and one of the things I ask my students to do is to come up with something - doesn't have to be tech-related - that they know better than anybody else in the group. We've had folks talk about how to cook ragu, how to surf on a longboard, how to get their kid to fall asleep ("literally nobody else in the world can do this, not even my wife"), and it is always remarkable to me how much more engaging and animated people become when they are telling their own story rather than paraphrasing research.