<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Code: Towards Intelligent Collaboration Tools</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Vladimir Kovalenko</string-name>
          <email>vladimir.kovalenko@jetbrains.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Intelligent Collaboration Tools, Data-Driven Software Engineering</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>(virtual)</institution>
          ,
          <addr-line>NL</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>JetBrains Research, JetBrains N.V.</institution>
          ,
          <addr-line>Huidekoperstraat 26, 1017 ZM Amsterdam, Noord-Holland</addr-line>
          ,
          <country country="NL">The Netherlands</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <abstract>
        <p>Think of a software engineer at work. What is on their screen: a terminal window? An IDE? In practice, it is just as likely to be a messenger or a bug tracker. We have made impressive progress with enabling individual developer tools to boost productivity through smart and eficient code analysis. Refactor a large project? A few keystrokes will do. Explore the structure of a complex system? No problem, click here, hope your screen is big enough. IDEs are incredibly powerful. In contrast, the collaboration tools of today - think issue trackers, code review tools, messenger workspaces - still resemble bulletin board systems. Most of their beauty and complexity lies in reliability, performance, and UX, rather than in features that truly model, support, and enhance the process of collaborative work. While there is plenty of room for new data-driven approaches in real-world collaboration tools, these tools are less popular as a context for such approaches proposed by the research community. In the keynote talk1, I am looking to highlight the collaboration tools as particularly interesting targets for data-driven enhancement.</p>
      </abstract>
      <kwd-group>
        <kwd>1</kwd>
        <kwd>“Software engineers mostly code”</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        https://vovak.me/ (V. Kovalenko)
Unlike integrated development environments (IDEs) that ofer incredibly powerful and complex
features enabling manipulation, refactoring, and analysis of large software projects with minimal
input from the user, and thus saving their time and energy, the collaboration tools of today –
issue trackers, code review systems, messenger workspaces, etc. – are relatively simple, and
do not extensively model the processes they support or ofer many “smart” features to their
users. While some approaches, such as expert recommendation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], have found their way into
mainstream collaboration tools such as Github and Gerrit, these examples are still rather rare.
      </p>
      <p>The room for improvement of the tools, along with the bias towards coding activities (Section
1), call for action to improve the collaboration tools. The list below presents some of the
promising research directions.</p>
      <p>• Gaining a better understanding of users’ behaviour, issues, and needs in collaboration
tools. This way, we can maximize the value of new techniques and features for end users.
• Trying academic approaches to data-driven support in collaborative engineering in
practice by extending existing tools.
• Devising techniques to ensure long-term health of projects and team dynamics.
• Treating the process and data in collaboration tools as an artifact: enabling the tools to
highlight potentially ineficient process patterns and suggest improvements;
• Augmenting the tools with extensive analytics engines to help their users comprehend
and analyze complex systems and processes.</p>
      <p>At the Intelligent Collaboration Tools Lab (ICTL),1 we work in these and related directions.
We are open to collaboration.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Singer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Lethbridge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Vinson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Anquetil</surname>
          </string-name>
          ,
          <article-title>An examination of software engineering work practices</article-title>
          ,
          <source>in: CASCON First Decade High Impact Papers</source>
          ,
          <year>2010</year>
          , pp.
          <fpage>174</fpage>
          -
          <lpage>188</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>A. N.</given-names>
            <surname>Meyer</surname>
          </string-name>
          , T. Fritz,
          <string-name>
            <given-names>G. C.</given-names>
            <surname>Murphy</surname>
          </string-name>
          , T. Zimmermann,
          <article-title>Software developers' perceptions of productivity</article-title>
          ,
          <source>in: Proceedings of the 22nd ACM SIGSOFT International Symposium on Foundations of Software Engineering</source>
          ,
          <year>2014</year>
          , pp.
          <fpage>19</fpage>
          -
          <lpage>29</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>M. K.</given-names>
            <surname>Gonçalves</surname>
          </string-name>
          ,
          <string-name>
            <surname>C. R. de Souza</surname>
          </string-name>
          , V. M.
          <article-title>González, Collaboration, information seeking and communication: An observational study of software developers' work practices</article-title>
          .,
          <source>J. Univers. Comput. Sci</source>
          .
          <volume>17</volume>
          (
          <year>2011</year>
          )
          <fpage>1913</fpage>
          -
          <lpage>1930</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>M. D'Ambros</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Lanza</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Robbes</surname>
          </string-name>
          ,
          <article-title>An extensive comparison of bug prediction approaches</article-title>
          ,
          <source>in: 2010 7th IEEE Working Conference on Mining Software Repositories (MSR</source>
          <year>2010</year>
          ), IEEE,
          <year>2010</year>
          , pp.
          <fpage>31</fpage>
          -
          <lpage>41</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>A.</given-names>
            <surname>Svyatkovskiy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Hadjitofi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Riechert</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. V.</given-names>
            <surname>Franco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Allamanis</surname>
          </string-name>
          ,
          <article-title>Fast and memory-eficient neural code completion</article-title>
          ,
          <source>in: 2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR)</source>
          , IEEE,
          <year>2021</year>
          , pp.
          <fpage>329</fpage>
          -
          <lpage>340</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>H. A.</given-names>
            <surname>Çetin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Doğan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Tüzün</surname>
          </string-name>
          ,
          <article-title>A review of code reviewer recommendation studies: Challenges and future directions</article-title>
          ,
          <source>Science of Computer Programming</source>
          (
          <year>2021</year>
          )
          <fpage>102652</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>