Skip to content

Commit a7c2c7a

Browse files
committed
Adds upcoming code review demo event
- Adds the March Code Review Demo event to event page and calendar
1 parent a8539b6 commit a7c2c7a

File tree

1 file changed

+14
-3
lines changed

1 file changed

+14
-3
lines changed

_events/2025/2025-03-code-review-demo-reproducibility.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,16 @@ layout: event
77
duration: 60
88
repeated: false
99
category: community-learning
10-
address:
1110
time:
1211
- - start: 2025-03-27T19:00:00Z
1312
end: 2025-03-27T20:00:00Z
1413
---
1514

16-
Join us for the first demo of the US-RSE's Code Review Working Group's "Code Review Demo Series". Our first demo will be on "Reproducibility Audits" presented by Eric Scott. Please register for the event at
15+
Join us for the first demo of the US-RSE's Code Review Working Group's "Code
16+
Review Demo Series".
17+
Our first demo will be on "Reproducibility Audits" presented by Eric Scott.
18+
Please register for the event at
19+
<https://arizona.zoom.us/meeting/register/TBDaXBUVT-evkLNR83bReg#/registration>
1720

1821
<!--more-->
1922
#### Title
@@ -22,4 +25,12 @@ Code Review Demo: Reproducibility Audits
2225

2326
#### Description
2427

25-
This is the first in a series of code review demos hosted by the US-RSE code review working group. In this demo, we will discuss reproducibility audits, a broad (and shallow) type of code review focused on the following questions: Can I figure out how to get the code to run? Does the code produce the expected outputs? How readable and re-usable is the code? This type of code review can be useful before submitting a manuscript with associated analysis code, or in the context of a “ReproHack”.
28+
This is the first in a series of code review demos hosted by the US-RSE code
29+
review working group.
30+
In this demo, we will discuss reproducibility audits, a broad (and shallow)
31+
type of code review focused on the following questions: Can I figure out how to
32+
get the code to run?
33+
Does the code produce the expected outputs?
34+
How readable and re-usable is the code?
35+
This type of code review can be useful before submitting a manuscript with
36+
associated analysis code, or in the context of a “ReproHack”.

0 commit comments

Comments
 (0)