This project is about collecting data on developers and creative coder's feelings about coding. It covers various information - from their coding experience to their outlook on coding and the community surrounding it.
Currently, the data collection is done through a Google survey form. Nine of eleven questions are required and two of them are optional short answer questions. Out of the nine required questions, three are focused on identifying feelings.
Here is a list of feelings about coding:
- Indifferent
- Lost
- Intimidated
- Anxious
- Frustrated
- Challenged
- Interested
- Excited
- Fulfilled
Here are the words for describing the perception of the coding community:
- Discouraging
- Intimidating
- Uncaring
- Helpful
- Supportive
- Encouraging
The goal of this project is about building emotional awareness - making developers aware of their feelings involved with coding, both as a sole and social activity.
Why is that important to know?
On an individual level, identifying emotions will help with emotional regulation. By identifying positive feelings, those feelings can be used as signals for interests. It is also useful for people to identify unwanted feelings. Once they unpack those feelings and figure out the underlaying issues, they can move on and learn how to manage them afterwards. Having this skill will make anyone a more productive and focused person.
On a communal level, we want to foster a kinder environment. Having the skill to identify and regulate emotions is vital for achieving that. How can someone care about how others feel when do even know or care about his/her own feelings?
To concretely demonstrate everyone's different perception about coding, we need to collect and visual the data to show a clear picture of the emotional state within a coding community.
Finally, this is about making people more open to examine and share their feelings. It is one of the best way to make genuine friends and establish deeper connections with others!
This project started because a discussion happened in Open Source Studio class at ITP, NYU.
Here is a short guideline for sharing your own dataset:
- When you submit data as a pull request, you agree to applying a CCO "No Rights Reserved" license. Thereby agree to place submitted data in the public domain for others to build upon, reuse for any purposes.
- Submit data as a error-free JSON file with .json file extension. Please validate your file on JSONLint before submitting. If JSONLint shows errors for you file, please fix the error(s) and validate it as valid JSON.
CC0 - “No Rights Reserved” CC0 enables scientists, educators, artists and other creators and owners of copyright- or database-protected content to waive those interests in their works and thereby place them as completely as possible in the public domain, so that others may freely build upon, enhance and reuse the works for any purposes without restriction under copyright or database law.
