Becoming a Better Curator of Your Code

30-minute Talk - date TBD at time TBD in room TBD

Writing code that functions correctly is only part of the development process. The majority of our time is spent reading, maintaining and refactoring our code.

In this talk we will discuss how when we see our work as code curation we actually enable our job to be much easier and productive.

Introduction (~5 minutes) - We will start the talk with an introduction to the role of a curator and how it applies to software engineers.

The ways you can be a better code curator (~20 minutes) - this is the main section in which we will discuss techniques you can use to be a better curator. Some of those are:

  • Promote the use of conventions and style guides for your team
  • Strive to always write readable code
  • The first goal of writing tests should be to document the code functionality
  • Encourage discussion on feature implementation
  • Encourage discussion during code reviews
  • Boy Scout rule - leave the code in a better shape than which you found it
  • Embrace new and mature technologies, and try to incorporate them into your code when applicable

On average I will allocate about 2 minutes for discussion each of the above points.

Conclusion (~5 minutes) - We will conclude the talk with lessons we learned about being a code curator and discuss how we can bring the curator mindset to an organization.

Presented by: