GT DevX session at the GDR SciLog 2026 conference
This year, for the second GT-DevX session during the GDR conference, and the first since the transition to the GDR SciLog, we want to explore DevX from the perspective of artificial intelligence and agentic tools.
These tools, often highlighted for their ability to address productivity challenges, are now an integral part of software development.
The question then arises: what is their impact on the daily work of different profiles of developers, and how can we envision what DevX might look like in the future?
Through these discussions, our objective remains the same as for previous events: to foster a community around discussions, the exchange of experiences, and potential future collaborations on the topic of developer experience.
Program
Tuesday, June 2, 2026 — Polytech Lille — Room 2
| Time | Title | Authors |
|---|---|---|
| 11:00 | Opening and presentation of the session program | Valentin Bourcier |
| 11:10 | Towards a Science of Developer eXperience (DevX) | Benoît Combemale |
| 11:30 | Brainstorming session begins | |
| 12:00 | Grouping ideas into themes | |
| 12:10 | Summary and conclusion of the session. |
Questions and themes addressed at previous events
December 15th, 2025
Topics covered:
- Discoverability/Usability
- Examples and presentations of tools to improve DevX (differential debugger, LaTeX DSL, XTDD)
- Reciprocity between mental health and DevX
Questions raised:
- What procedures should be implemented when creating tools to facilitate DevX?
- What is the definition of discoverability and usability, and how do we measure them?
- Is this sufficient to evaluate DevX, and how do we proceed? Surveys, other models?
- What approach can be used to quantify the psychological impact?
- How can we reconcile the needs of businesses with the experience of developers (reciprocity)?
December 4th, 2024
The objective was to define the conceptual framework of the DevX (Developer Experience) working group.
The discussion went beyond the notion of technical tools to encompass the overall human experience in the software development process.
1. Definition and Scope
Beyond code: DevX isn't limited to developers, but extends to all stakeholders involved in the software lifecycle (testers, analysts, engineers, and citizens).
Holistic approach: DevX includes tools, but also methodologies, workflows, social interactions, and psychological aspects (satisfaction, feelings, retention).
The goal is to reduce cognitive friction to maintain a "flow" state.
2. Main challenges
Reducing friction: Creating environments where information is contextual and intuitive to facilitate decision-making.
Accessibility: Making development more accessible, including to non-IT experts (citizens).
Efficiency and Productivity: Improving efficiency through methods, paradigms, or metaprogramming, while preserving developer well-being.
3. Scientific and Technical Challenges
It is important to define how to measure developer experience using metrics (efficiency, satisfaction) and how to assess the real impact of tools. But DevX evaluation also appears to be interdisciplinary, integrating cognitive psychology (understanding needs related to emotions or perceived difficulty), as well as the principles of User Experience (UX) and Human-Computer Interaction (HCI) applied to developers.
4. Key Questions Emerging from the Meeting
The discussion highlighted several areas of uncertainty and open questions that will guide future work:
Questions on Definition and Scope:
- How can DevX be differentiated and integrated with related fields (traditional UX, classical software engineering)?
Questions on Measurement and Evaluation:
- How can DevX be evaluated scientifically? What metrics should be used beyond time efficiency (e.g., measuring happiness, cognitive retention, mental workload)?
- How can participants be recruited for empirical studies and these metrics validated?
- How can we determine if a specific problem is worth solving with a tool (cost/benefit analysis)?
Technical and Methodological Questions:
- What is the precise role of AI and LLMs in this experience? How do they interact with developer cognition?
- How can frameworks be built to integrate the various disparate artifacts and tools into a coherent experience?
- How do we move from analyzing friction to actually creating solutions (playgrounds for testing ideas)?
Organizational Questions:
- How do we effectively connect these different academic and industrial silos around a shared vision and standardized evaluation protocols?
Next Steps and Mobilization
Upcoming planned activities include a bimonthly seminar, scientific workshops and regular exchanges.