We're an international team of academic Software Engineering researchers investigating technical debt and debt annotation practices. Technical debt (also known as tech debt or code debt) describes what happens when development teams take actions to expedite the delivery of a piece of functionality or a project that later needs to be refactored. In other words, it’s the result of prioritizing speedy delivery over perfect code.
We aim to gather information on how you interpret the priority of source code fragments that contain technical debt. By participating in this experiment, you'll help us create a better understanding of technical debt annotation and management procedures. Your insights will be used to support the prioritization of maintenance activities in software systems. The survey will only take 10 to 15 minutes; you can find the study here ( https://tueapse.qualtrics.com/jfe/form/SV_39T0IWub1qC8cmy?Source=Google). *Why do I believe this is relevant for this community?* Previously, we also studied this specific community and this experiment is a continuation of work that has been published (See https://cassee.dev/files/satd-and-polarity.pdf <https://cassee.dev/files/satd-and-polarity.pdf>). Your responses will help us better understand technical debt, and allow us to design better tools for the management of Technical Debt. Thanks! I greatly appreciate it if you could participate in the experiment. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/b3fad24f-adbc-4429-a137-bc57209ed173n%40googlegroups.com.
