Feedback cycles and their role in improving overall developer experiences

•Descargar como PPTX, PDF•

0 recomendaciones•337 vistas

Drawing from experiences from open source work and her time at Spotify, Serah’s talk cover the challenges, opportunities and hacks around proactive and reactive monitoring, processing, tracking and acting on stakeholder and community feedback, and argue for the centricity of well-defined feedback loops in improving the overall developer experiences for any product and features you are responsible for.

Tecnología

P. 1
Hey
there! Serah Njambi Kiburu
Senior Developer Advocate
@serahkiburu

P. 2
The F between D and X:
Feedback Cycles and
their Role in Improving
Overall Developer
Experiences DEVELOPER EXPERIENCE
1
DEVELOPER JOURNEYS
2
SPOTIFY FOR DEVELOPERS
3
VALUE OF ADOPTION
4
FEEDBACK: ROLE, MODES, CYCLES
5

OLE HEJLSKOV ALVARO NAVARRO PJ HAGERTY
JO FRANCHETTI
GU JIAN THORBIÖRN FRITZON SERAH KIBURU
JOSH BROWN

Web API
RESTful API to fetch
metadata about
music artists,
albums, tracks, and
podcasts. Interact
with user data and
playlists.
Web Playback SDK
Client-side
Javascript library that
allows you to create
a new player in
Spotify Connect and
play audio from
Spotify in the
browser.
Commercial
Hardware
Library to integrate
speakers and other
devices with Spotify
Connect.
Embeds
Provides
embeddable views of
tracks, artists,
albums, playlist, and
podcasts to use
within your web
page.
Ads API
build, manage, and
report on Ad Studio
campaigns

Imitation
is the
finest
form of
flattery?
Design by Isabel Castillo Guijarro

Design by Isabel Castillo Guijarro
Adoption
is has to
be the
finest
form of
flattery -
Spotify
Edition

P. 16
The F between D and X:
Feedback Cycles and
their Role in Improving
Overall Developer
Experiences DEVELOPER EXPERIENCE
1
DEVELOPER JOURNEYS
2
SPOTIFY FOR DEVELOPERS
3
VALUE OF ADOPTION
4
FEEDBACK: MODES, ROLE, CYCLES
5

Developer Journeys
____________________________
What are the myriad of
ways that developers
perceive and use the
tech resources
available to them
(platforms, tools,
documentation,
opportunities and
communities)? Design by Isabel Castillo Guijarro

P. 18
The F between D and X:
Feedback Cycles and
their Role in Improving
Overall Developer
Experiences DEVELOPER EXPERIENCE
1
DEVELOPER JOURNEYS
2
SPOTIFY FOR DEVELOPERS
3
VALUE OF ADOPTION
4
FEEDBACK: MODES, ROLE, CYCLES
5

Developer Relations: How to Build
and Grow a Successful Developer
Program. Apress, 2022.
Caroline Lewko and James Parton.

Facets of Developer Experience work
1. Interfacing with community of users to triage
issues, understand use cases, discuss ideas,
foster innovation, recognize efforts, maintain
feedback loops
2. Documentation to facilitate discovery,
decision-making, onboarding
3. Standardization in the way APIs are designed
and developed
4. Ease of experimentation via consoles,
tutorials, code snippets, sandboxes
5. Ease of use via reference docs, error codes,
changelogs, versioning
6. Use case amplification as sources of
inspiration and clarity around use

P. 21
The F between D and X:
Feedback Cycles and
their Role in Improving
Overall Developer
Experiences DEVELOPER JOURNEYS
1
DEVELOPER EXPERIENCE
2
SPOTIFY FOR DEVELOPERS
3
VALUE OF ADOPTION
4
FEEDBACK: ROLE, MODES, CYCLES
5

Feedback Cycles: Theory of
Feedback and Feedback Facilitation
in the Carpentries, 2020.
Serah Kiburu, Lou Woodley, Kari Jordan.
The linear feedback
model

Feedback Cycles: Theory of
Feedback and Feedback Facilitation
in the Carpentries, 2020.
Serah Kiburu, Lou Woodley, Kari Jordan.
Feedback cycles, ideally.

1.1:1 Interviews
or shadowing
____________________________
Check-ins with
individual developers
or teams to hear
about their
experiences firsthand
Design by Isabel Castillo Guijarro

2.OFFICE
HOURS AND
DEVELOPER
DAYS
____________________________
Periodic scheduled
check-ins onlines or
as meetups to hear
from developers and
offer realtime support Design by Isabel Castillo Guijarro

3. FEEDBACK
CHANNELS
____________________________
Dedicated spaces like
forms, issue repositories,
Slack or Discord
channels and forum
pages for people to
interact with owners and
maintainers of the APIs
they use regularly

4. ADVOCATES AND
COUNCILS
____________________________
Working in roles like
developer advocates to
constantly think about
DX and Developer
Journeys, interface with
and advocate for end
users, and / or set up
community councils so
your users can be heard
and responded to
regularly
Design by Isabel Castillo Guijarro

www.devrelbook.com/ Feedback Cycle and
Facilitation models in an
Online Open Source
Community by Serah Kiburu,
Lou Woodley, Kari Jordan
docsfordevelopers.com/

THANK YOU
developer.spotify.com
@serahkiburu

Más contenido relacionado

Similar a Feedback cycles and their role in improving overall developer experiences

5 Keys to API Design - API Days Paris 2013

Daniel Feist

Current research into the use of mobile devices and tablet computers like the iPad indicate there are multiple opportunities to support and enhance learning and we already know a considerable amount about what works in classrooms when these devices are deployed. However it is still unclear why or how these technologies make a difference and this presentation argues that design based research (DBR) would help practitioners and researchers gain a better understanding about the design principles required to develop effective and meaningful learning sceanrios using mobile technologies

Using design based research to develop meaningful mobile learning scenarios

Kevin Burden

Brief, but descriptive tutorial of the Scaled Agile Framework (SAFe) 4.5. Starts with impetus for agility, overview of lean and agile thinking, definition of portfolio management, explanation of SAFe and its values and principles, etc. Then, provides a level-by-level overview of SAFe, including case studies, metrics, business case, adoption statistics, roles, responsibilities, and other considerations. Closes with a nice summary of key SAFe implementation principles ...

Scaled Agile Framework (SAFe) 4.5 Tutorial ...

David Rico

02 API Academy - path to success

CHARLES Frédéric

IJSRED-V2I2P5

IJSRED

apidays LIVE Australia 2020 - Federating API Development at Australia’s large...

apidays

BbWorld'08 Podcasting Preconference Session

ekunnen

Slides for my talk at ApacheCon 2016 https://apacheconeu2016.sched.org/event/8ULf/exploring-and-integrating-ux-in-open-source-software-development-victoria-bondarchuk-seoul-tech-society The importance of introducing usability activities into free open source software development has been acknowledged in the research and by the community, yet FOSS products have been criticized for having little or no emphasis on usability. The decentralized and engineering-driven approach of open source projects can conflict with usability methodologies. We will review existing cases of UX design contribution to open source projects, discuss how designers can become part of the community and what engineers can do to improve usability of the software they build.

Exploring and Integrating UX in Open Source Software Development

Victoria Bondarchuk

Introduction to Open Source

Epic

Revolution R Enterprise: 100% R and More (14 Mar 2013)

Revolution Analytics

Treating Code Quality as a First Class Entity (icsme15) [doc. symposium]

Yuriy Tymchuk

Analyzing the Eclipse API Usage: Putting the Developer in the Loop

Alexander Serebrenik

Providing a good API product to your users is the minimum. With all the competition developers have many more expectations than quality APIs; developer community, documentation, tutorials, developer tools and this is exactly where the Developer Relations (DevRel) team fits. In this talk we’ll discuss why your API product needs a DevRel team and how it can drastically upgrade the face of your API program and satisfy your users. We’ll talk about how the DevRel team can engage your users to nurture a long-term community and make your API product successful.

Why you need a Developer Relations team for your API

Pronovix

mobile app development.pdf

GlobeTechSoft1

«Технологии удалённого общения неизбежно возьмут своё в будущем. А те, кто освоит их раньше, получат больше шансов на успех», – уверен Максим Павловец, ведущий блога о бизнес-возможностях платформ для удаленного общения Webinarism.ru, ставший недавно обладателем гранта от программы «Менеджмент в сфере интернет-технологий». Подробнее - http://www.rma.ru/internet/news/8374/

Webinarism.ru got RMA grant

spasibokep

How do we reach developers and sustain a quality relationship with them? In this presentation, I cover tips on discoverability, support engineering, developer resource generation, and more, with the aim to create great developer programs that users trust and appreciate. But wait, there's a surprise! Liam Neeson will be our guide through this DevRel training montage. His lesson: Always mind your surroundings! This presentation was given at API City 2018 on Oct 4th.

Always Mind Your [Developer] Surroundings - API City 2018

Bill Doerrfeld

UX research at Napster: A Product Manager’s perspective

UserTesting

apidays LIVE Hong Kong - Why you need a DevRel team for your API by Anna Tsol...

apidays

apidays LIVE Australia 2021 - OpenAPI Generator - The Babel Fish of the API W...

apidays

Six Principles of Software Design to Empower Scientists

David De Roure

Similar a Feedback cycles and their role in improving overall developer experiences (20)

5 Keys to API Design - API Days Paris 2013

Using design based research to develop meaningful mobile learning scenarios

Scaled Agile Framework (SAFe) 4.5 Tutorial ...

02 API Academy - path to success

IJSRED-V2I2P5

apidays LIVE Australia 2020 - Federating API Development at Australia’s large...

BbWorld'08 Podcasting Preconference Session

Exploring and Integrating UX in Open Source Software Development

Introduction to Open Source

Revolution R Enterprise: 100% R and More (14 Mar 2013)

Treating Code Quality as a First Class Entity (icsme15) [doc. symposium]

Analyzing the Eclipse API Usage: Putting the Developer in the Loop

Why you need a Developer Relations team for your API

mobile app development.pdf

Webinarism.ru got RMA grant

Always Mind Your [Developer] Surroundings - API City 2018

UX research at Napster: A Product Manager’s perspective

apidays LIVE Hong Kong - Why you need a DevRel team for your API by Anna Tsol...

apidays LIVE Australia 2021 - OpenAPI Generator - The Babel Fish of the API W...

Six Principles of Software Design to Empower Scientists

Más de Pronovix

Your relationship with a developer begins before they even know your product's name. In fact, before they know they need a product like yours. In this talk, Matthew will make the case that developer marketing, developer experience, and developer education are part of a continuum. And that if you're thinking of documentation as something that happens only after someone has signed-up for your API, then you're leaving it too late. He'll draw on pedagogical and marketing research to propose a model for the developer learning journey where traditional API documentation is just one stop along the way. Attend this talk and you'll come away with practical ideas for how to start educating developers earlier in their product evaluation and learning journey.

By the time they're reading the docs, it's already too late

Pronovix

Optimizing Dev Portals with Analytics and Feedback

Pronovix

Building our a developer portal may seem easy at the onset with off the shelf options, but when you're building a custom portal to match the needs of your company, it's not as easy. In this session, we'll talk about our process in determining the right places to start with success metrics and features through an early stage feedback back before having customers. You'll see our intention is to tell a story with multiple facets for multiple people, developers, product managers, C suite decision makers etc... Stories around API usage, health, cost, errors and support to provide our users with an overall of their business performance through our APIs.

Success metrics when launching your first developer portal

Pronovix

AI is entering the world of APIs, where API documentation plays a critical role. One of the fundamental challenges is the need to share understanding about an API and keep the knowledge up to date. AI can potentially speed up API integrations dramatically, but it greatly depends on API documentation. Let's explore the emerging approach to employing AI in APIs, discuss its impact on API documentation, and see how changing our way of working with APIs will lead to self-integrating applications.

Documentation, APIs & AI

Pronovix

As content producers, we invest considerable time and effort in developing, packaging, and delivering content that we think our users need. After publishing the content, we hope that users find our content useful. And we often wonder how users really navigate and consume our content. Web page analytics can help us gauge the information needs of our customers, assess their content consumption behavior, and find opportunities to improve our content and how we deliver it. Kumar explores the basics of web analytics, pitfalls of relying too much on web analytics for important decisions, the typical web analytics process, and he will share some guidelines for interpreting web analytics numbers.

Making sense of analytics for documentation pages

Pronovix

The main goal of API documentation is to help developers understand how to use an API. With GraphQL, developers often assume it's self-documenting capabilities are sufficient for anyone that consumes their GraphQL API. But did you ever validate this? Good API documentation offers both static and interactive ways to learn how to consume the API. API's that support GraphQL often only come with interactive documentation, in the shape of a GraphiQL Playground. However, the first time you (or your users) use a GraphQL API can be very frustrating as GraphQL APIs typically only have an interactive playground. it increases the complexity for newcomers to GraphQL as it assumes you’re already familiar with GraphQL. But with GraphQL, you’re not limited to just an interactive playground, as you can create static or interactive documentation next to having this playground. This talk explores which forms of documentation you can use and how they add value to your GraphQL API.

GraphQL Isn't An Excuse To Stop Writing Docs

Pronovix

Web3 is one of the fastest-growing spaces on the web right now, with thousands of new projects emerging every week. Each project aims to fill a gap in the space by providing a new technology How do we keep up with documentation, and what should be prioritized for these projects as they scale? Web3, also referred to as the read-write-own web, is a new form of the internet that utilizes technologies such as blockchain networks, cryptocurrency, crypto wallets, and digital assets like NFTs. The Web3 space is growing by the thousands every week, with new projects and technologies constantly emerging. As writers, it can be challenging to navigate through the space, make sense of every piece of new content, and understand what should be written about for others to read, and what will be irrelevant next week. Many of these new technologies are using pieces of code known as smart contracts or interacting with the APIs of multiple applications at once. What documentation are end-users looking for, and what is the most beneficial format for them to read and comprehend all of this new information? In this talk, I'll discuss what I've learned as a Senior Technical Writer for Filebase, a decentralized cloud storage provider at the heart of hundreds of Web3 projects, and what our customers have benefited from the most when it comes to documentation.

API Documentation For Web3

Pronovix

API docs frequently fail to address developers’ needs by omitting common usage scenarios and use cases. Let’s take a look at good and bad practices for documenting API use cases, and take steps to ensure that developers get from our API and docs what they really want. You wrote an API specification, documented your endpoints, and published SDKs. Here’s a question, though: Does your API actually solve your users’ problems? API providers often fail to address common use cases to solve users’ needs, or their assumptions don’t match the reality. This may end up in frustration and loss of users. In this talk, we will take a peek into developers’ mindset. I will show how to better understand the developers’ needs by researching the usage patterns, existing libraries and 3rd party experience layers, provide examples of good and bad practices, and suggest actionable steps to improve developer experience for your API.

Why your API doesn’t solve my problem: A use case-driven API design

Pronovix

unREST among the docs

Pronovix

Nobody likes ambiguity—especially when it comes to the stability of APIs and the expectations for availability long term. Avoid common pitfalls and explore a critical area where trust is built with developers through thoughtful policy and the development of best-in-class documentation. A good deprecation policy involves a lot of forward thinking and an awareness of how developers or end users are currently leveraging your capabilities, and how a given API or feature deprecation could affect them in the future. The hard-earned trust that you’ve built and maintained with these individuals is at risk with any type of policy or documentation that is unclear. The road to developing a clear, trustworthy deprecation policy is a multi-faceted initiative with input from product, engineering, customer success and other cross-functional teams, as well as external market awareness. Knowing which voices to have in the room, what the industry standards are, and formulating appropriate communication timelines will ensure a world class policy is developed and documented before it’s needed. Join us as we dive into the nuances of this process and how to avoid the common pitfalls that come from lacking a strategic, thoughtful approach to documenting a deprecation policy for your APIs.

Developing a best-in-class deprecation policy for your APIs

Pronovix

At MongoDB, we now generate REST API references for MongoDB Atlas from annotations in the product’s source. Our team’s writers proposed, planned, led, and implemented this project–and learned a lot along the way. We’ll share how we got buy-in from engineering and product stakeholders, coordinated the project across teams, implemented swagger-core annotations in Java, and drove positive change to benefit our team, the company, and our users.

Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone

Pronovix

It turns out there is no single answer. Developers may have unique goals, motivations, constraints, and challenges, and all of these influence how they approach the problem in front of them. However, more than a decade ago, three development styles were identified - systematic, pragmatic, and opportunistic - and the academic literature suggests that these still exist today. Two of the three approaches, the systematic and the opportunistic pattern, can be considered as opposite extremes, while the pragmatic approach is situated in between and is similar to both. It is not a personality trait - people may approach a situation one way or another depending on their circumstances, goals, and motivations (however, they may also have a preferred approach, which is usually their characteristic). Understanding the differences between these patterns (and the different needs) helps us to design in a way that serves most of the users, and even helps them to get into a state of flow by providing the optimal level of challenge to solve their problem.

What do developers do when it comes to understanding and using APIs?

Pronovix

It's time to take the bias out of code, UI, docs, configurations, or our everyday language by ensuring we choose our words carefully to avoid harmful subtext or exclusion. We can do our part and take steps by examining assets from code to config files to API specifications to standards. Heard of suss? You can suss out more information or you can find someone's information to be suss. "Suss" shows the flexibility of language. It’s an ongoing process to change how we use certain words. It's important to choose words carefully to convey the correct meaning and avoid harmful subtext or exclusion. Let's explore some of the tools and triage methods that it takes from an engineering viewpoint to make bias-free choices. How can you ensure that biased words do not sneak into code, UI, docs, configurations, or our everyday language? First, let's walk through how to take an inventory of assets from code to config files to API specifications to standards. Next, by placing those findings into categories, prioritize the work to substitute with inclusive alternatives. Let's examine some examples using both API and code assets. Next is a demonstration of how to automate analyzing your source code or documentation with a linter, looking for patterns based on rules that are fed into the tool. What's in the future for these efforts? Inclusive language should expand beyond English and North America efforts. To do so, let's organize the work with automation tooling, as engineers do.

Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations

Pronovix

How to create documentation and write code for an international audience, not just the people who speak and think like you. Make your APIs more useful for everyone on the planet. Much of the documentation supplied by both Open Source and Close Souce projects assume the community have a good understanding of the English language and often North American culture as well. This creates barriers for many solution providers, who are the gateway to potentially huge markets for your project. This talk discusses some of the cultural differences, particularly for people from Asia, in using English language API documentation. It suggests some strategies to help diverse audiences understand you APIs and create solutions using them. The talk will cover not only differences in language but also other cultural differences that are often not obvious. For example: Different expectations about publication formats, release processes, levels of support during the development process Meeting and communications styles Software development workflows, processes, and tools Supporting people who are visually impaired will also be briefly discussed. As well as discussing these issues, specific suggestions will be provided to make API docs accessible for as many people as possible. This talk is based on Alec's work with customers in Europe, North America, Middle East, Asia, and Australasia. The last five have been spent as a developer evangelist working with PaperCut partners in China, Japan, Korea, US and Europe.

Creating API documentation for international communities

Pronovix

APIs in a modern enterprise are rarely uniform or all of the same type. The multitude of API types can be due to organic growth, mergers and acquisitions, or any number of other reasons. Regardless of their origin, APIs of all types need to be fully documented to facilitate a developer’s journey as they interact with your API ecosystem in order to develop useful applications. In this talk I will show examples of how we have augmented developer portals to document APIs that are not of the REST variety, such as AsyncAPI, GraphQL, SOAP, gRPC, and more, such that all API documentation can seamlessly live side-by-side.

One Developer Portal to Document Them All

Pronovix

We are a software engineering team creating API docs. Docs are authored using Instructional Design principles to narrate use-cases and practical API implementations. This talk shares why & how we've applied software development practices to evolve our document tooling, creation, & delivery methods. Our APIs describe asynchronous protocols used for embedded software (firmware) components in a digital 2-way radio communications system. The API is protocol data unit (PDU) based and its definition is described in a proprietary format; consequently, well-known API formats, such as Swagger/OpenAPI, or tools, such as doxygen, are not used. Our product training and technical writing teams are very experienced in Instructional Design methods, but these teams have only written documentation for an end-user audience. Understanding software development processes is equally important as understanding two-way radio networks in order to successfully integrate with the APIs. This is the rationale for having a software engineering team develop the skillsets to write API documentation for a developer audience. With a solid foundation of API documentation in place, regular examination of engineering efficiency and developer experience is appropriate. Repeated actions can be replaced by automation. Content can be modular and re-usable. Formats can be streamlined for easier consumption. Docs can be made portable and lightweight for faster delivery.

Docs-as-Code: Evolving the API Documentation Experience

Pronovix

Ever wonder how some products are just lovable and easy to use while other are not? The good products have optimized onboarding into their ecosystem where you get the information served at the right time. That’s thanks to developer journey and we will teach you how to get it right! We will go through the basics such as how to analyze existing and non-existing developer touchpoints, set metrics and optimize them to increase the conversion.

Developer journey - make it easy for devs to love your product

Pronovix

Deliberate Complexity Conferences - 19 JULY 2022 Alicia Juarrero - Complexity is not complicatedness Professor Alicia Juarrero, a leading complexity theory philosopher and academic, as well as the founder and president of VectorAnalytica, a technology company that specializes in large scale scientific data capture and real time analysis tools. Alicia's work in complexity theory is widely quoted by thought leaders in the technology space and referenced in many recent complexity-informed approaches for managing highly dynamic systems, as well as in knowledge management.

Complexity is not complicatedness

Pronovix

How cognitive biases and ranking can foster an ineffective architecture and d...

Pronovix

APIs: Semi-permeable, osmotic interfaces

Pronovix

Más de Pronovix (20)

By the time they're reading the docs, it's already too late

Optimizing Dev Portals with Analytics and Feedback

Success metrics when launching your first developer portal

Documentation, APIs & AI

Making sense of analytics for documentation pages

GraphQL Isn't An Excuse To Stop Writing Docs

API Documentation For Web3

Why your API doesn’t solve my problem: A use case-driven API design

unREST among the docs

Developing a best-in-class deprecation policy for your APIs

Annotate, Automate & Educate: Driving generated OpenAPI docs to benefit everyone

What do developers do when it comes to understanding and using APIs?

Inclusive, Accessible Tech: Bias-Free Language in Code and Configurations

Creating API documentation for international communities

One Developer Portal to Document Them All

Docs-as-Code: Evolving the API Documentation Experience

Developer journey - make it easy for devs to love your product

Complexity is not complicatedness

How cognitive biases and ranking can foster an ineffective architecture and d...

APIs: Semi-permeable, osmotic interfaces

Último

A Domino Admins Adventures (Engage 2024)

Gabriella Davis

Sara Mae O’Brien Scott and Tatiana Baquero Cakici, Senior Consultants at Enterprise Knowledge (EK), presented “AI Fast Track to Search-Focused AI Solutions” at the Information Architecture Conference (IAC24) that took place on April 11, 2024 in Seattle, WA. In their presentation, O’Brien-Scott and Cakici focused on what Enterprise AI is, why it is important, and what it takes to empower organizations to get started on a search-based AI journey and stay on track. The presentation explored the complexities of enterprise search challenges and how IA principles can be leveraged to provide AI solutions through the use of a semantic layer. O’Brien-Scott and Cakici showcased a case study where a taxonomy, an ontology, and a knowledge graph were used to structure content at a healthcare workforce solutions organization, providing personalized content recommendations and increasing content findability. In this session, participants gained insights about the following: Most common types of AI categories and use cases; Recommended steps to design and implement taxonomies and ontologies, ensuring they evolve effectively and support the organization’s search objectives; Taxonomy and ontology design considerations and best practices; Real-world AI applications that illustrated the value of taxonomies, ontologies, and knowledge graphs; and Tools, roles, and skills to design and implement AI-powered search solutions.

IAC 2024 - IA Fast Track to Search Focused AI Solutions

Enterprise Knowledge

Partners Life - Insurer Innovation Award 2024

The Digital Insurer

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Bajaj Allianz Life Insurance Company - Insurer Innovation Award 2024

The Digital Insurer

How to Troubleshoot Apps for the Modern Connected Worker

ThousandEyes

Imagine a world where information flows as swiftly as thought itself, making decision-making as fluid as the data driving it. Every moment is critical, and the right tools can significantly boost your organization’s performance. The power of real-time data automation through FME can turn this vision into reality. Aimed at professionals eager to leverage real-time data for enhanced decision-making and efficiency, this webinar will cover the essentials of real-time data and its significance. We’ll explore: FME’s role in real-time event processing, from data intake and analysis to transformation and reporting An overview of leveraging streams vs. automations FME’s impact across various industries highlighted by real-life case studies Live demonstrations on setting up FME workflows for real-time data Practical advice on getting started, best practices, and tips for effective implementation Join us to enhance your skills in real-time data automation with FME, and take your operational capabilities to the next level.

From Event to Action: Accelerate Your Decision Making with Real-Time Automation

Safe Software

BooK Now Call us at +918448380779 to hire a gorgeous and seductive call girl for sex. Take a Delhi Escort Service. The help of our escort agency is mostly meant for men who want sexual Indian Escorts In Delhi NCR. It should be noted that any impersonator will get 100 attention from our Young Girls Escorts in Delhi. They will assume the position of reliable allies. VIP Call Girl With Original Photos Book Tonight +918448380779 Our Cheap Price 1 Hour not available 2 Hours 5000 Full Night 8000 TAG: Call Girls in Delhi, Noida, Gurgaon, Ghaziabad, Connaught Place, Greater Kailash Delhi, Lajpat Nagar Delhi, Mayur Vihar Delhi, Chanakyapuri Delhi, New Friends Colony Delhi, Majnu Ka Tilla, Karol Bagh, Malviya Nagar, Saket, Khan Market, Noida Sector 18, Noida Sector 76, Noida Sector 51, Gurgaon Mg Road, Iffco Chowk Gurgaon, Rajiv Chowk Gurgaon All Delhi Ncr Free Home Deliver

08448380779 Call Girls In Greater Kailash - I Women Seeking Men

Delhi Call girls

What is a good lead in your organisation? Which leads are priority? What happens to leads? When sales and marketing give different answers to these questions, or perhaps aren't sure of the answers at all, frustrations build and opportunities are left on the table. Join us for an illuminating session with Cian McLoughlin, HubSpot Principal Customer Success Manager, as we look at that crucial piece of the customer journey in which leads are transferred from marketing to sales.

04-2024-HHUG-Sales-and-Marketing-Alignment.pptx

HampshireHUG

Presentation on how to chat with PDF using ChatGPT code interpreter

naman860154

Finology Group – Insurtech Innovation Award 2024

The Digital Insurer

Enterprise Knowledge’s Urmi Majumder, Principal Data Architecture Consultant, and Fernando Aguilar Islas, Senior Data Science Consultant, presented "Driving Behavioral Change for Information Management through Data-Driven Green Strategy" on March 27, 2024 at Enterprise Data World (EDW) in Orlando, Florida. In this presentation, Urmi and Fernando discussed a case study describing how the information management division in a large supply chain organization drove user behavior change through awareness of the carbon footprint of their duplicated and near-duplicated content, identified via advanced data analytics. Check out their presentation to gain valuable perspectives on utilizing data-driven strategies to influence positive behavioral shifts and support sustainability initiatives within your organization. In this session, participants gained answers to the following questions: - What is a Green Information Management (IM) Strategy, and why should you have one? - How can Artificial Intelligence (AI) and Machine Learning (ML) support your Green IM Strategy through content deduplication? - How can an organization use insights into their data to influence employee behavior for IM? - How can you reap additional benefits from content reduction that go beyond Green IM?

Driving Behavioral Change for Information Management through Data-Driven Gree...

Enterprise Knowledge

[2024]Digital Global Overview Report 2024 Meltwater.pdf

hans926745

Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...

Neo4j

2024: Domino Containers - The Next Step. News from the Domino Container commu...

Martijn de Jong

Handwritten Text Recognition for manuscripts and early printed texts

Maria Levchenko

Scaling API-first – The story of a global engineering organization

Radu Cotescu

Evaluating the top large language models.pdf

ChristopherTHyatt

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

Feedback cycles and their role in improving overall developer experiences

1. P. 1 Hey there! Serah Njambi Kiburu Senior Developer Advocate @serahkiburu

2. P. 2 The F between D and X: Feedback Cycles and their Role in Improving Overall Developer Experiences DEVELOPER EXPERIENCE 1 DEVELOPER JOURNEYS 2 SPOTIFY FOR DEVELOPERS 3 VALUE OF ADOPTION 4 FEEDBACK: ROLE, MODES, CYCLES 5

3. SPOTIFY FOR DEVELOPERS

4. OLE HEJLSKOV ALVARO NAVARRO PJ HAGERTY JO FRANCHETTI GU JIAN THORBIÖRN FRITZON SERAH KIBURU JOSH BROWN

5. Web API RESTful API to fetch metadata about music artists, albums, tracks, and podcasts. Interact with user data and playlists. Web Playback SDK Client-side Javascript library that allows you to create a new player in Spotify Connect and play audio from Spotify in the browser. Commercial Hardware Library to integrate speakers and other devices with Spotify Connect. Embeds Provides embeddable views of tracks, artists, albums, playlist, and podcasts to use within your web page. Ads API build, manage, and report on Ad Studio campaigns

6. THE VALUE OF ADOPTION

7. Imitation is the finest form of flattery? Design by Isabel Castillo Guijarro

8. Design by Isabel Castillo Guijarro Adoption is has to be the finest form of flattery - Spotify Edition

9. INSTAFEST.APP

10. EVERY NOISE AT ONCE

11. MAGIC PLAYLIST

12. JQBX

13. IPOD.JS

14. DUBOLT

15. RADIO NEWIFY

16. P. 16 The F between D and X: Feedback Cycles and their Role in Improving Overall Developer Experiences DEVELOPER EXPERIENCE 1 DEVELOPER JOURNEYS 2 SPOTIFY FOR DEVELOPERS 3 VALUE OF ADOPTION 4 FEEDBACK: MODES, ROLE, CYCLES 5

17. Developer Journeys ____________________________ What are the myriad of ways that developers perceive and use the tech resources available to them (platforms, tools, documentation, opportunities and communities)? Design by Isabel Castillo Guijarro

18. P. 18 The F between D and X: Feedback Cycles and their Role in Improving Overall Developer Experiences DEVELOPER EXPERIENCE 1 DEVELOPER JOURNEYS 2 SPOTIFY FOR DEVELOPERS 3 VALUE OF ADOPTION 4 FEEDBACK: MODES, ROLE, CYCLES 5

19. Developer Relations: How to Build and Grow a Successful Developer Program. Apress, 2022. Caroline Lewko and James Parton.

20. Facets of Developer Experience work 1. Interfacing with community of users to triage issues, understand use cases, discuss ideas, foster innovation, recognize efforts, maintain feedback loops 2. Documentation to facilitate discovery, decision-making, onboarding 3. Standardization in the way APIs are designed and developed 4. Ease of experimentation via consoles, tutorials, code snippets, sandboxes 5. Ease of use via reference docs, error codes, changelogs, versioning 6. Use case amplification as sources of inspiration and clarity around use

21. P. 21 The F between D and X: Feedback Cycles and their Role in Improving Overall Developer Experiences DEVELOPER JOURNEYS 1 DEVELOPER EXPERIENCE 2 SPOTIFY FOR DEVELOPERS 3 VALUE OF ADOPTION 4 FEEDBACK: ROLE, MODES, CYCLES 5

22. FEEDBACK: CYCLES

23. Feedback Cycles: Theory of Feedback and Feedback Facilitation in the Carpentries, 2020. Serah Kiburu, Lou Woodley, Kari Jordan. The linear feedback model

24. Feedback Cycles: Theory of Feedback and Feedback Facilitation in the Carpentries, 2020. Serah Kiburu, Lou Woodley, Kari Jordan. The linear feedback model

25. Feedback Cycles: Theory of Feedback and Feedback Facilitation in the Carpentries, 2020. Serah Kiburu, Lou Woodley, Kari Jordan. Feedback cycles, ideally.

26. FEEDBACK: MODES

27. 1.1:1 Interviews or shadowing ____________________________ Check-ins with individual developers or teams to hear about their experiences firsthand Design by Isabel Castillo Guijarro

28. 2.OFFICE HOURS AND DEVELOPER DAYS ____________________________ Periodic scheduled check-ins onlines or as meetups to hear from developers and offer realtime support Design by Isabel Castillo Guijarro

29. 3. FEEDBACK CHANNELS ____________________________ Dedicated spaces like forms, issue repositories, Slack or Discord channels and forum pages for people to interact with owners and maintainers of the APIs they use regularly

30. 4. ADVOCATES AND COUNCILS ____________________________ Working in roles like developer advocates to constantly think about DX and Developer Journeys, interface with and advocate for end users, and / or set up community councils so your users can be heard and responded to regularly Design by Isabel Castillo Guijarro

31. www.devrelbook.com/ Feedback Cycle and Facilitation models in an Online Open Source Community by Serah Kiburu, Lou Woodley, Kari Jordan docsfordevelopers.com/

32. THANK YOU developer.spotify.com @serahkiburu

Feedback cycles and their role in improving overall developer experiences

Recomendados

Recomendados

Más contenido relacionado

Similar a Feedback cycles and their role in improving overall developer experiences

Similar a Feedback cycles and their role in improving overall developer experiences (20)

Más de Pronovix

Más de Pronovix (20)

Último

Último (20)

Feedback cycles and their role in improving overall developer experiences