- The document discusses different approaches that developers take to learning APIs: the systematic approach, where developers want to be in control and fully understand what they are doing; the opportunistic approach, where developers quickly experiment and reuse examples; and the pragmatic approach, which combines elements of the first two. - It also discusses the concept of "flow" in software development and lists some triggers for getting into a state of flow such as clear goals, immediate feedback, and a rich environment. - The document concludes by asking questions about how to maximize the chance that developers experience flow when using documentation.

1. I am Emese
Hello!
- Psychologist, UX researcher
- Family of developers

2. - Give them what they need
- No errors,
- No exceptions
- Good design in invisible
- Understand their tasks, goals
- 2007, Steven Clarke
- 3 approaches to software
development
The happy path

3. Generally
- A well-educated approach
- Building elegant, maintainable solutions
API learning
- review concepts and architecture documentation to
- take time to prepare the development environment
- form hypotheses about possible approaches
- follow the proposed processes and suggestions closely
The systematic approach
“I want to know what I am doing”, “I want to be in control”
devportal code

4. Generally
- curious explorers
- just a sufficient understanding to be able to solve their problem
- varying expertise (e.g. citizen developers)
API learning
- quickly scan through the documentation, start experimenting
- reuse code examples/other people’s solutions
- Web searches, a lot of open browser tabs
The opportunistic approach
“Let’s see how it can be used”
web code
devp code

5. Generally
- Combining the elements of the systematic and the opportunistic
approaches
API learning
- Learn enough to start the task and then refer back to the
documentation (or other resources) as needed
The pragmatic approach
devp code

6. “
Providing everything developers
might need is not enough.

7. My way to get loving statistics:
A personal story

8. Flow: the source code of intrinsic motivation
Feel our best - perform our best
…full involvement (totally absorbed), intense
concentration, embodiment, enjoyment, creativity,
silenced inner critic..

9. The questions to ask…
1. What types of information do
developers need?
2. What kind of mindset do they come
to a devportal with?
3. How to maximize the chance that
developers will experience flow?

10. Challenge
Skills
Arousal
Anxiety
Worry
Apathy
Boredom
Relaxation
Control
FLOW
Some of the triggers/correlates of flow:
- Intensely focused attention
- Clear goals
- Immediate feedback
- High consequences
- Risk
- Rich environment
Getting into the zone

11. Any questions?
You can find me at
◉ emese.hallgato@pronovix.com
Thanks!
11