Skip to content

Commit 4e6bee7

Browse files
authored
Fixed a typo
1 parent d372bcb commit 4e6bee7

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

content/posts/2025-04_JD.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Let's Get Them a Room!"
2+
title: "Let's Get Them in a Room!"
33
date: 2025-04-25T14:38:30-05:00
44
# bookComments: false
55
# bookSearchExclude: false
@@ -13,6 +13,6 @@ First, we drafted a description of the meeting and put it on our website (we hav
1313

1414
Our efforts were met with success! We had a total of 12 people at our meeting and at least 3 of those were new faces. The amazing thing about this group of people was that the situation was different for almost everyone in the room. Some people were of the type “long wolf RSE” that didn't have any other RSE colleagues, while others worked in teams, big as well as small. Some people developed web applications, some worked with LLMs, and some worked on scientific code and HPC resources. So naturally, the experiences of each person differed greatly.
1515

16-
To give the meeting some structure, we created a short agenda to make sure everyone was on the same page. We introduced our efforts up to this point, talked about the RSE movement in general (to make sure everyone knew about US-RSE!), and then went around the room for everyone to introduce themselves and their work. Afterwards, we posed a few questions to get a discussion started. We encouraged everyone to share their career path and thoughts on what ASU could provide to make their work better. It was an engaging and very interesting discussion. We talked about the difference between software engineering and research software engineering, the different projects people worked on, and how RSEs at ASU could support each other and connect.
16+
To give the meeting some structure, we created a short agenda to make sure everyone was on the same page. We introduced our efforts up to this point, talked about the RSE movement in general (to make sure everyone knew about US-RSE!), and then went around the room for everyone to introduce themselves and their work. Afterwards, we posed a few questions to get a discussion started. We encouraged everyone to share their career path and thoughts on what ASU could provide to make their work better. It was an engaging and very interesting discussion. We talked about the differences between software engineering and research software engineering, the different projects people worked on, and how RSEs at ASU could support each other and connect.
1717

1818
In summary, this in person meeting was a great step forward for the RSE community at ASU. More people now know about our efforts, we have more contacts, and word-of-mouth can spread a little farther than before.

0 commit comments

Comments
 (0)