home.social
  1. 🧵 highlights:

    6. Contributing to the planning for an RSE Competencies Toolkit (github.com/RSEToolkit/rse-comp) during their workshop.

    7. Learning more about the different backgrounds and approaches of RSEs and RSE teams through the Emerging Voices talks and other events.

    4/4

  2. 🧵 highlights:

    4. Expanding my knowledge of through talks on mutation testing, performant code, templates, and more (and also finding UCL ARC’s great guide on Python tooling: github-pages.arc.ucl.ac.uk/pyt).

    5. Meeting other RSEs interested in developing software as a medical device and making a plan for sharing knowledge and experiences.

    3/n

  3. 🧵 highlights:

    2. Learning about airqualitystripes.info/ and discussing in RSE projects

    3. Meeting members of the RSE community, learning about the R development process and tools like {reprex}, working on a >20 year old (!) issue, and picking everyone’s brains about software engineering best practices in R.

    2/n

  4. 🧵 I attended my first conference () this past week! A few highlights:

    1. Having the opportunity to present some of our team’s work on requirements capture (slides: gmschroeder.com/software/rseco). (Shown here sneaking in one of my favourite data visualisations - one of cartographer Harold Fisk’s maps of the evolution of the Mississippi River - as an analogy for complex, evolving research projects).

    1/n