Ce diaporama a bien été signalé.
Le téléchargement de votre SlideShare est en cours. ×

Evangelizing Explained

Chargement dans…3

Consultez-les par la suite

1 sur 102 Publicité

Plus De Contenu Connexe

Similaire à Evangelizing Explained (20)

Plus par Christian Heilmann (20)


Plus récents (20)

Evangelizing Explained

  1. Evangelism explained Christian Heilmann, Sao Paulo, Brazil, 06/11/2008 (Yahoo Internal)
  2. I’m Chris. Hello I am Chris
  3. I live in London, England
  4. But originally I am German
  5. Doesn’t matter though, both countries keep losing against you playing football...
  6. Anyways...
  7. Developer Evangelism
  8. Sounds like not working, right?
  9. Far from it.
  10. As a developer evangelist you are first and foremost a translator.
  11. Tech Colleagues The Business Evangelist The Outside world
  12. You are lucky if the business understands that as an evangelist you need your freedom.
  13. You are also lucky if the business doesn’t have any short-term agendas.
  14. Your colleagues are very much needed...
  15. ...as they keep you rooted in the now and the reality of the company.
  16. They can also be bad for the cause as they have to suffer a lot more day-to-day frustrations than you do.
  17. Your job is to find the middle ground of these frustrated voices and the business message.
  18. This is where the truth lies.
  19. First and foremost you need to be an independent voice.
  20. Keep your eyes open all the time and follow what is happening on the web.
  21. If a startup or a competitor of your company does something cool...
  22. ...you should know about it.
  23. Don’t barge into the developer “scene” trying to sell only your company’s solutions.
  24. No matter how cool they seem at the time.
  25. Instead show them as an offering, a system that works well with others...
  26. ...making everybody’s life easier and our jobs less of a hassle.
  27. This is very important right now as if you don’t work efficiently...
  28. ...you might become redundant.
  29. Which brings me to another, very important asset of successful evangelists.
  30. Don’t bring your own agenda...
  31. ... instead know what problems the people you talk to have.
  32. I’ve had quite a hard time in my career to get my bosses to sponsor me a ticket to go to conferences...
  33. ...or even leave the office and talk to other companies and developers.
  34. Which meant that when I finally went to one...
  35. ...I made sure I got my money’s worth.
  36. Whenever you talk to people about your products and services...
  37. ...make sure people can take something back to impress their bosses with.
  38. Which means that you need to do your homework and find out what people want from you.
  39. You show different products to a design agency that you would to a Python crowd.
  40. Talking about geeks...
  41. Coming from a large international company may be a benefit...
  42. ...but only when you use it right.
  43. Deep down every geek sees every large corporation as evil and replaceable by a small server script.
  44. I thought that.
  45. Now I know that these corporations are made up by geeks like you and me.
  46. Photo of Pete LePage of Microsoft and Peter-Paul Koch of Quirksmode.org drinking at The Ajax Experience in Boston Not the Antichrist Not a hairpiece
  47. And our job is to get the world to at least hear about these geeks...
  48. ...if not meet them in the flesh.
  49. Which is why we should not only be present at developer events...
  50. ...but also open ourselves to geeks and invite them to come to us for some informal (yes, beers) events.
  51. As a developer you need to be visible to get your concerns heard.
  52. You might be the best deliverer out there but if you really want things to change...
  53. ...you also need to tell people about what you do and how you succeed in being efficient.
  54. If you share your knowledge, you are less of a risk.
  55. You should work for the company, for yourself and for the next developer taking over from you.
  56. By sharing information internally you make sure that developers can have a real life and get sick without stalling projects.
  57. You also allow for developers to move around from project to project, thus preventing boredom and elitism.
  58. Sharing information internally is an absolute necessity to have a successful team.
  59. However, to get the full picture you also need to validate your ideas with the outside world.
  60. The same applies to big companies.
  61. We could be arrogant enough to say we know what people need.
  62. But in essence we know jack until we can get it confirmed from outside our echo chamber.
  63. And that is what we are doing with our evangelising.
  64. Evangelising means that we prove and improve our products and assumptions.
  65. Business Evangelist Internal Developers
  66. Evangelist World Evangelist Internal Business Developers
  67. So how can we get the message out there?
  68. Well, first of all by using the internet.
  69. Set up a local mailing list that people can subscribe to.
  70. Have a blog that explains techniques and solutions built in the company.
  71. A good example is the Filament group blog. http://filamentgroup.com/lab
  72. I found this via a bookmark on del.icio.us...
  73. ...that made it to hotlinks... http://dev.upian.com/hotlinks/
  74. ...which I have subscribed to in Google reader...
  75. ...which meant a friend of mine found it through my shared items...
  76. ...who lives next door to them and didn’t know them!
  77. The web is a web of linked systems.
  78. Not a billboard.
  79. Instead of just building something and hoping that people come...
  80. ...be present where people already hang out.
  81. Have a twitter bot telling people about things that happen.
  82. Use social bookmarking, photo sharing sites and social networks.
  83. Then you will reach much more people and point them to your resources.
  84. They in turn will tell their friends and contacts.
  85. And word of mouth from people I trust is much more powerful than a corporate message.
  86. Whatever you do, wherever you show up...
  87. Be very responsive. Establish yourself as a “way in”.
  88. So what do *we* have to offer you can talk about?
  89. It all starts at http://developer.yahoo.com
  90. Designers can benefit from our design patterns: http://developer.yahoo.com/ypatterns/
  91. The YUI is an amazing framework to build web sites with (CSS, JavaScript, Widgets) http://developer.yahoo.com/yui/
  92. Our APIs give access to all our data: http://developer.yahoo.com/everything.html
  93. In various handy formats and now even accessible with a SQL-style syntax: http://developer.yahoo.com/yql/
  94. Using the Yahoo Application Platform, people can develop applications running on Yahoo! sites: http://developer.yahoo.com/yap/
  95. The performance team assembled an amazing array of cool tools and information how to make web sites lightning fast: http://developer.yahoo.com/performance/
  96. There is great information on server security and attack vectors on the web: http://developer.yahoo.com/security/
  97. And for people who want to mash up data in a nice, visual way, there’s Yahoo! Pipes http://pipes.yahoo.com/
  98. There are several systems to use to authenticate users for your apps with our help: http://developer.yahoo.com/auth/ http://developer.yahoo.com/oauth/
  99. Lots of stuff to talk about and package up in an easy to understand way.
  100. Why not have a go at it?
  101. Obrigado! Christian Heilmann | http://wait-till-i.com | twitter: codepo8