> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-open-source-committee/about/open-source-office-oso/developer-advocate-program/state-of-developer-experience-survey.md).

# State of Developer Experience Survey

{% file src="/files/X1h63LzYtp19X4X2bAGn" %}

### Executive Summary

The State of Developer Experience Survey for Cardano aimed to understand developers' and contributors' challenges, motivations, and aspirations of developers and contributors within the Cardano ecosystem. The survey gathered insights from 52 participants, representing diverse experience levels, educational backgrounds, and language proficiencies. Below are the key takeaways:

* The Cardano ecosystem attracts a diverse range of developers, from novices to experienced professionals, who are strongly motivated to contribute and grow within it.
* Addressing challenges related to developer tools, documentation, and technical complexities will be critical for improving productivity and onboarding new developers.
* Language support and multilingual resources are vital for fostering inclusivity and reducing barriers for non-native English speakers. Two-thirds of respondents are willing to volunteer to translate resources into their native languages.
* The community’s willingness to contribute to open-source projects and translation efforts highlights the potential for collaborative growth and innovation.

The insights from this survey will guide the developer advocates and Intersect’s open source committee (OSC) in designing initiatives that address developers' needs, reduce barriers to entry, and empower the community to contribute effectively.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/about/open-source-office-oso/developer-advocate-program/state-of-developer-experience-survey.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.