2019 Wish : The #serverless community practices what it preaches, and focuses the conferences/talks/articles on the value gained, rather than the technology and concepts. In fact, we probably need to have some basic rules for serverless content. For example -
1) Must identify yourself as a practitioner (someone leveraging #serverless technologies to build something of end customer value) or a provider (someone who is providing technology that elables a practitioner to go serverless).
2) Practitioner content must highlight the agility/elasticity/cost gains from using the serverless tech, and the business value tied to solution.Bonus points for minimal code written:: value ratio.
3) Practitioners must share where they are in their #serverless journey, because the more you use, the more you know. Practitioners also welcome to give Provider critique, hacks to work around limitations, and best practices with existing tech, ideally explicitly labelled.
4) Provider talk must highlight how they are making security, usability, scale, or performance considerations better, or how practitioners can best use your product to get desired agility/elasticity/cost gains. Must ideally tie back to demonstrated practitioner value.
5) To claim to be a provider you must explain what you are eliminating for the practitioner, not just what you are. Bonus points for proof. Bonus points for previous practitioner hacks eliminated.
6) Focus on real use cases, not intros, not abstract patterns and behaviors. Save thought leadership for Twitter. Exceptions apply (keynotes, new providers) but ideally explicitly labelled.
What are other good rules to add? Which of these do you disagree with? @ben11kehoe @jeremy_daly @PaulDJohnston @brianleroux @mweagle @sbarski @jeffhollan
