https://discuss.lfnw.org/t/the-linux-developer-experience/160

As developers, we tend to focus our efforts on our code, our projects and our final "product". Creating content for other developers is a necessary part of the experience.

Ensuring the content is usable and useful is essential!

In this presentation, I will offer examples of how to improve the documentation processes, describe the Documentation Development Life Cycle, and recommend collaboration procedures for documentation.

Also, I would love to present some of the useful and not so useful items found in documentation. One example is making sure the $ prompt is not included in the "copy code" snippet. Another example is guiding developers with instructions but also including a script.

In one of my blog posts, I describe POSIX and the need for Linux documentation to be written or at least validated on Linux systems.

I will discuss the difference between a command and a brand. Examples will be presented.

Additionally, this presentation would be a great place to present tools, utilities and applications available in the FOSS Content Creator toolbox. Some examples are GIMP, scrot, and simplescreenrecorder.

At this point in the presentation, I will provide an introduction to tools used to conduct Linux Developer Experience testing. Some of these tools include analyzing bash history of testing participants, click heat maps, the potential of using pre-trained emotion models (Deep Learning/AI) to analyze reactions using computer vision. Often, User Experience testing records participants. The availability of Linux toolkits and utilities, expands the possibilities for developer testing over simple recordings.

Finally, I will discuss how to offer full disclosure of these participant experience methods and how to inform participants regarding the Developer Experience Testing Participation and how their data will be used.

If there is time, Q and A around documentation and developer experience is always a great way to interact with the attendees.