[1/3] Enabling the Study of Software Development Behavior With Cross-Tool Logs (Category Management)

I finally read it. studyfeathered 2020 The year, where the authors from Google spoke about the creation of their system InSession, which allows you to conduct a comprehensive analysis of the behavior of engineers by integrating logs from a variety of development tools. The value of the research is that developers are one of the most expensive parts of software development, so even small improvements in productivity can bring significant results. InSession differed from other similar tools in that it collected not only data from the IDE, but also did not require installation on working machines engineers. (Data collected from existing cloud tools).

As for the system itself, it consisted of the following key parts: 1. Events (Events) An event is a separate use of a tool or system by or on behalf of a developer. Each type of log had its own importer, which transformed the data into a common event format. The events themselves were of different types. Front-end events: initiated by the developer actively (For example, pressing the interface button) Backend events: occurring asynchronously on behalf of the developer (For example, cron assignments) Instant Events: With Uncertain Endpoint Long-term events: with set start and end times 2. Artifacts For most events, additional meta-information was collected, which the authors called artifacts. They were two types. Task-identifying artifactsIdentify a specific development task for grouping related events Information artifactsProvide contextual information about the event 3. Sessions In fact, events were brought together in the session with the help of groups that

• It happens on the same day.
• During the time interval (10 minute) Have the same task identifying artifacts (or have no) 4. Metrics. The system displays seven key metrics of developer behavior: Coding time – time of writing or maintaining code Review time - time for code review
• Escort time. (shepherding) time to finalize the code based on feedback from code review Research time - time to study documentation Development time - time for development activities of any type (What is not covered by other categories)
• E-mail hours
• Time spent in meetings

When it comes to data sources for InSession, there are many tools that include Buganizer - Error Tracking System Code Search - a tool for searching and viewing code

• Cider - Web IDE Blaze - distributed assembly system Critique - a code review tool Gmail and Calendar – limited metadata
• Even more so. 90 command-line

Continuation of this interesting article in next post.

#Engineering #Software #Bigtech #Productivity #Management #Leadership #Processes