Developer Zero

AKA "Dogfooding ++"

Transcript

1. 01100100 01100101 01110110 01100101 01101100 01101111 01110000 01100101 01110010 00100000 0011000 0 DEVELOPER ZERO Steven Serrata
2. Developer Zero • Inspired by Ade Oshineye interview on developer advocates as “customer zero” • Dogfooding ++ • “How can I help improve the product?” • ”How can I enable the best developer experience? Product Management Engineering Quality Assurance Developer Relations Developer Community * Ade Oshineye is a Senior Staff Developer Advocate @Google
3. Application Framework Suite of APIs that enable developers to rapidly build innovative security solutions. The apps are published to our Cloud Services Portal, our “app store” for security solutions. • Logging Service – data lake that can store logs from firewalls, endpoints, cloud services, etc. • Event Service – subscription service with filtering capabilities that allows applications to poll for notifications • Directory Sync Service – provides applications access to customer User Directory data
4. Prologue “An existential crisis is a moment at which an individual questions if their life has meaning, purpose, or value.” --Wikipedia The chars: “The Inward Thinker” “The Adventurer” “The Hero” “The Oaf”
5. Setup • The PAN Cloud Python SDK – idiomatic python SDK for the App Framework • API Explorer – sample app that enables users to “test drive” the App Framework APIs • “Kickstart” Developer Relations team • Currently team of 6 and growing • 30+ partner app demos featured at Ignite ’18 conference • 7 apps are currently GA
6. Chapter 1 - “Steven’s Quest” “The Adventurer” Logging Service Event Service Directory Sync Service OAuth2 App Portal ?
7. Chapter 1 – Access to APIs • Internal-only/non-public APIs • Most required client certificates (PKI managed by IT) • Event Service and API gateway layer didn’t exist • API endpoints pre-GA • Non-existent or incomplete documentation • No clear idea who ”owns” what, never mind how to engage them “The Oaf”
8. Chapter 1 – Access to APIs • “Asked around town” • Searched employee directory/org charts for ”owners” • Searched Confluence • Lync/Skype, Slack “The Adventurer”
9. Chapter 1 – Access to APIs “The Adventurer”
10. Chapter 2 – Develop the SDK • Swagger down pat • Early TechPub documentation • OAuth2 playground • Focus on DevEx and usability • Familiar “feel” and usage patterns “The Inward Thinker”
11. Chapter 3 – Build the sample app • End-to-end testing of app onboarding, activation and authorization • QA tool • Partner/developer enablement • Increased recognition and respect from Eng/QA • Leverage sample app and SDK to validate API behavior and recommend improvements “The Hero”
12. Epilogue (discussion) • Why is “Developer Zero” important (or why not?) • Do you have a personal “Developer Zero” story to share?