Appendix 2 - Theory and Practice

This research was also informed by an internal Anaconda UX framework organised around segments, personas and scenarios. Because this report will be read outside Anaconda, we describe how that framework relates to PyScript's approach without reproducing its confidential detail. Its segments describe practitioner types as functional roles within organisational structures, and map closely to PyScript's archetypes (appendix 1), which describe postures towards creating with code. Its personas work just as PyScript's do, giving the two frameworks a shared vocabulary. Its most valuable addition is scenarios: three descriptions of what practitioners try to accomplish regardless of role or background - Setting Up (their environment, tooling and initial access to assets), Building and Development (creating, testing and iterating on technical work) and Sharing and Collaboration (distributing outcomes, working with others, managing access). Every practitioner in this report navigates a variation of all three, and they are a welcome lens on a practitioner's journey that PyScript's research will adopt.

Related is the notion of "AI-native" development, a term coined by Gartner to describe systems, products and engineering practices that integrate AI as a core, foundational component rather than a bolted-on feature. Gartner's specific forecasts are informed speculation and we treat them as such, but the term is the current language of our commercial users, and this report engages with what it names: how practitioners now build with AI-native tooling, and how well our APIs, services and documentation are represented inside those tools. Theme E presents the practitioner evidence for this and next step #4 proposes the response. It is where the open-source practitioner focus of this report and Anaconda's commercial interests most clearly converge.