the daily life of software along with heir expences
Answers
Answer:
What is a good workday for a software developer? What is a typical workday? We seek to answer these two questions to learn
how to make good days typical at work. We developed conceptual frameworks to help
define and characterize developer workdays from two new perspectives: good and typical. Our analysis confirms some findings in
previous work, including the fact that developers actually spend little time on development and developers’ aversion for meetings and
interruptions. It also discovered new findings, such as that only 1.7% of survey responses mentioned emails as a reason for a bad
workday, and that meetings and interruptions are only unproductive during development phases; during phases of planning, specification
and release, they are common and constructive. One key finding is the importance of agency, developers’ control over their workday and
whether it goes as planned or is disrupted by external factors. We present actionable recommendations for researchers and managers to
Explanation: