The aim of this experiment is to investigate the scale of usability for an application that is designed for developers, such as yourself, to understand their development process. Before you decide whether you want to take part, it is important for you to understand why the research is being done and what your participation will involve. You should only participate if you want to; choosing not to take part will not disadvantage you in any way, and you are welcome to withdraw at any time. If you do so, then it will not be possible for you to be debriefed about the purposes of the experiment. Please take time to read the following information carefully and ask us if there is anything that is not clear or if you would like more information. For questions, you can send an email to Inesh Bose: [email protected]
The application "Code Fitness" was created as an MSci Research Project with the target to help individual and/or teams of developers understand the state of their project easily through a centralised dashboard that would present information that they are interested in - similar to a fitness app like Google Fit that allows users to toggle statistics - so that their (development) journey can be realised accordingly. You are asked to make use of this dashboard during the development of your project(s) and provide feedback at regular intervals. You are free to not answer questions that are not required, but the data will help. All responses are anonymous and in compliance with GDPR and the University of Glasgow SoCS Project Ethics.
- I understand and wish to participate in the experiment
The questions in this section focus on your demographics. These questions are designed in order to understand you, as a user, and to mitigate any bias. This section has no required responses.
- Web developer (fullstack, backend, frontend)
- Native apps developer (desktop, mobile)
- System / data engineer / DevOps (background, architectural)
- Project manager / designer (low code interaction)
-
Other...
- Individual
- Team (<= 8 people, in-person)
- Team (<= 8 people, remote)
- Team ( > 8 people )
-
Other...
| Frequently | Occassionally | Rarely | Never | |
|---|---|---|---|---|
| Version Control | ||||
| Issue Management (GitHub, Trello, Asana) | ||||
| Discord / Slack / Teams | ||||
| Feature branching & PR/MR reviews | ||||
| Visual Studio Code | ||||
| CLI / Bash / Linux |
- GitHub
- GitLab SaaS (gitlab.com)
- GitLab self-managed (private instances like stgit.dcs.gla.ac.uk)
- Bitbucket
- SourceForge
- Gitea / Gogs
-
Other...
This section would help you set up the application and take confirmations for the required steps. Please notify and alert the researcher on completion, and if you face any issues.
https://code.visualstudio.com/
- Already using
- Already installed
- Done
-
Other...
- Already using
- Already installed
- Done
-
Other...
https://wakatime.com/vs-code (API key available on https://wakatime.com/api-key)
- Already using
- Already installed
- Done
-
Other...
GitHub version: https://marketplace.visualstudio.com/items?itemName=2504266b-student-gla-ac-uk.code-fitness stgit version: https://marketplace.visualstudio.com/items?itemName=2504266b-student-gla-ac-uk.code-fitness-stgit
- Installed GitHub version
- Installed stgit version
https://wakatime.com/integrations https://wakatime.com/plugins
Reminder: all data from these platforms would only be private to you and useful for detailed visualisations
- Chrome extension
- Zoom plugin
-
Other...
Confirm the dashboard works by opening Command Palette on your VSCode (Ctrl+Shift+P / ⇧⌘P), selecting "Code Fitness: Open dashboard" and visualising the generated graphs after the initial load
- I confirm I'm able to access the dashboard and setup properly
With this, you should be introduced and setup with the VSCode extension.
You would be told about the number of weeks that you are required to provide the weekly feedback. Please complete the first instance of this survey at https://forms.gle/JHfVdNigHeF9sLCQ9
To reiterate, the aim of the experiment is to evaluate the usability of a daily food portion count tracker application (called Code Fitness). This meant navigating through the pages, interacting with elements, visualisation and appeal. Your responses would help point out and understand any frustrations or problems that might have occurred during your experience.
If you would like to know and see more about this project, everything (including the source code) can be found on this GitHub repository: https://github.com/ineshbose/code-fitness. This repository acts as the single source of truth for all information regarding Code Fitness. This would also mean participant feedback and data analysis, therefore if you would like to aid this practice, you can confirm your responses being held in this public repository anonymously. By default, your data will not be public and on the repository, if you do not agree. It will help more developers gather insight and refer to data for making better applications for the world in the future.
For more questions and concerns, you can send an email to Inesh Bose: [email protected]
- I am OK with my responses being public (but anonymous)
Short-answer text
- Completed