From bcfcb17b2713e73664c98de9b5f4fe32afb73993 Mon Sep 17 00:00:00 2001
From: github-actions
Date: Fri, 31 Jul 2026 04:23:22 +0000
Subject: [PATCH 01/11] Automated push to update jobs files 2026-07-31
---
_data/jobs.yml | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/_data/jobs.yml b/_data/jobs.yml
index 4573dcaf2..5ae5e42dc 100644
--- a/_data/jobs.yml
+++ b/_data/jobs.yml
@@ -69,16 +69,6 @@
name: Sr. Engineer, Research Software
posted: 2026-04-28
url: https://ayarlabs.com/careers/?gnk=job&gni=8a78839e9db1e919019dc4823f3e23e8&lang=en
-- expires: 2026-05-31
- location: Oak Ridge National Laboratory, Oak Ridge, TN
- name: Research Software Engineer
- posted: 2026-04-22
- url: https://jobs.ornl.gov/job/Oak-Ridge-Research-Software-Engineer-TN-37830/1382098300/
-- expires: 2026-05-31
- location: Oak Ridge National Laboratory, Oak Ridge, TN
- name: Lead Research Software Engineer
- posted: 2026-04-22
- url: https://jobs.ornl.gov/job/Oak-Ridge-Lead-Research-Software-Engineer-TN-37830/1382092600/
- expires: 2026-07-31
location: Harvard University, Cambridge, MA
name: Senior Research Software Engineer
From 21a3bed64d7d43572d604eb265ac6ee80d0dab86 Mon Sep 17 00:00:00 2001
From: TinasheMTapera <15770644+TinasheMTapera@users.noreply.github.com>
Date: Thu, 6 Aug 2026 18:06:05 -0400
Subject: [PATCH 02/11] rebases are dumb
---
.gitignore | 3 +++
_posts/newsletters/quarto/_data | 1 +
2 files changed, 4 insertions(+)
create mode 120000 _posts/newsletters/quarto/_data
diff --git a/.gitignore b/.gitignore
index 37cec15ff..e4da0ab73 100644
--- a/.gitignore
+++ b/.gitignore
@@ -8,3 +8,6 @@ Gemfile.lock
.DS_Store
vendor/
_vendor/
+
+.uvr
+.vscode
\ No newline at end of file
diff --git a/_posts/newsletters/quarto/_data b/_posts/newsletters/quarto/_data
new file mode 120000
index 000000000..404baebc6
--- /dev/null
+++ b/_posts/newsletters/quarto/_data
@@ -0,0 +1 @@
+../../../_data
\ No newline at end of file
From 3f8a4c35743c13866d5746e3208654093e8778d0 Mon Sep 17 00:00:00 2001
From: TinasheMTapera <15770644+TinasheMTapera@users.noreply.github.com>
Date: Thu, 6 Aug 2026 18:06:58 -0400
Subject: [PATCH 03/11] summer newsletter
---
.../newsletter/Newsletter_Content_Triage.csv | 314 ++
_data/newsletter/articles.bib | 477 ++
_data/newsletter/articles.yml | 1137 ++++
_data/newsletter/blog.yml | 0
_data/newsletter/blogs.bib | 269 +
_data/newsletter/blogs.yml | 362 ++
_data/newsletter/events-opportunities.yml | 206 +
_data/newsletter/media.bib | 203 +
_data/newsletter/media.yml | 308 ++
_data/newsletter/usrse.bib | 951 ++++
_posts/newsletters/2026-08-05-newsletter.md | 503 ++
_posts/newsletters/quarto/.Rprofile | 47 +
_posts/newsletters/quarto/.gitignore | 7 +
_posts/newsletters/quarto/.r-version | 1 +
.../quarto/Newsletter_Preproc.html | 4669 +++++++++++++++++
.../newsletters/quarto/Newsletter_Preproc.qmd | 175 +
_posts/newsletters/quarto/_conference.md | 20 +-
_posts/newsletters/quarto/_events.md | 4 +-
.../pandoc-ext/multibib/_extension.yaml | 6 +
.../pandoc-ext/multibib/multibib.lua | 156 +
_posts/newsletters/quarto/_headline.md | 94 +-
_posts/newsletters/quarto/_news.md | 90 +-
_posts/newsletters/quarto/_orgmember.md | 3 +-
_posts/newsletters/quarto/_preamble.md | 24 +-
_posts/newsletters/quarto/_quarto.yml | 6 +
_posts/newsletters/quarto/_reads.md | 41 +-
_posts/newsletters/quarto/params.yml | 34 +-
.../newsletters/quarto/render_new_edition.sh | 33 +
_posts/newsletters/quarto/template.md | 437 +-
_posts/newsletters/quarto/template.qmd | 14 +-
_posts/newsletters/quarto/uvr.lock | 761 +++
_posts/newsletters/quarto/uvr.toml | 14 +
_posts/newsletters/render_new_edition.sh | 25 -
33 files changed, 11058 insertions(+), 333 deletions(-)
create mode 100644 _data/newsletter/Newsletter_Content_Triage.csv
create mode 100644 _data/newsletter/articles.bib
create mode 100644 _data/newsletter/articles.yml
create mode 100644 _data/newsletter/blog.yml
create mode 100644 _data/newsletter/blogs.bib
create mode 100644 _data/newsletter/blogs.yml
create mode 100644 _data/newsletter/events-opportunities.yml
create mode 100644 _data/newsletter/media.bib
create mode 100644 _data/newsletter/media.yml
create mode 100644 _data/newsletter/usrse.bib
create mode 100644 _posts/newsletters/2026-08-05-newsletter.md
create mode 100644 _posts/newsletters/quarto/.Rprofile
create mode 100644 _posts/newsletters/quarto/.gitignore
create mode 100644 _posts/newsletters/quarto/.r-version
create mode 100644 _posts/newsletters/quarto/Newsletter_Preproc.html
create mode 100644 _posts/newsletters/quarto/Newsletter_Preproc.qmd
create mode 100644 _posts/newsletters/quarto/_extensions/pandoc-ext/multibib/_extension.yaml
create mode 100644 _posts/newsletters/quarto/_extensions/pandoc-ext/multibib/multibib.lua
create mode 100644 _posts/newsletters/quarto/_quarto.yml
create mode 100755 _posts/newsletters/quarto/render_new_edition.sh
create mode 100644 _posts/newsletters/quarto/uvr.lock
create mode 100644 _posts/newsletters/quarto/uvr.toml
delete mode 100755 _posts/newsletters/render_new_edition.sh
diff --git a/_data/newsletter/Newsletter_Content_Triage.csv b/_data/newsletter/Newsletter_Content_Triage.csv
new file mode 100644
index 000000000..28630d276
--- /dev/null
+++ b/_data/newsletter/Newsletter_Content_Triage.csv
@@ -0,0 +1,314 @@
+Submission,"What Section(s) of the Newsletter Would this Content Fit Into?",Content,Staging,"Submitted By",Message,"Submission Date","Event Date","Content Expiration Date",Link,Location
+"I think these two papers might be of interest to share in the newsletter
+• E. A. Jensen, D. S. Katz, ""Awareness of FAIR and FAIR4RS among in...","Interesting Reads-Videos-Podcasts",,Published,d.katz@ieee.org,https://usrse.slack.com/archives/C030B3KA4B0/p1745247524009699,"4/21/25, 11:23 AM",,,,
+"April 27th, 2026 at 8:29 PM UTC","Community News, Interesting Reads-Videos-Podcasts","We're excited to announce the publication of our NSF NCAR Community Software Facility Discovery Workshop Report.
+
+This report is a comprehensive write-up from the
+The CSF Discovery Workshop: Scientific software better practices, tools, and culture, which was hosted at NSF NCAR in August 2025
+
+This workshop gathered insights on:
+- Large-scale co-development successes and lessons learned
+- Better practices for collaborative development
+- How to balance competing demands
+- Strategies for setting projects up for long-term success
+- Tools that support co-development
+- Opportunities for professional development for RSEs
+- Approaches to leading through cultural change
+
+Thank you to everyone who participated and provided inputs. We hope this can be a great resource to the RSE community.
+
+https://opensky.ucar.edu/islandora/object/technotes%3A45415",Published,mickelso@ucar.edu,,"4/27/26, 4:29 PM",,,,
+"June 5th, 2026 at 2:59 PM UTC","Community News, Interesting Events-Opportunities",":seedling: Our community is full of people doing fascinating research and software work, and we want to put a face to it. Starting this month, we'll be featuring a group of different members in a regular spotlight: what they work on, a tool they can't live without, and how they found their way into RSE work. :yellow_heart::usrse_main_logo:
+
+We'd love to feature *YOU.* It takes about 5 minutes to fill out, and nothing gets posted without your okay:
+:point_right: https://forms.gle/dXqVsHKiHnot2u449
+
+Email Pengyin Shan for any questions!",Published,pengyins@illinois.edu,,"6/5/26, 10:59 AM",,,,
+"June 4th, 2026 at 6:52 PM UTC","Interesting Events-Opportunities, Interesting Reads-Videos-Podcasts","We hope you will join us for the June LINCC Tech Talk session that will take place on Thursday, June 11, at 10am Pacific/1pm Eastern on Zoom (https://ls.st/lincc-talks). We will hear about EzTaoX by Weixiang Yu.
+
+*EzTaoX: Scalable and Flexible Multiband Modeling of AGN Light Curves in the Rubin Era*
+Active galactic nuclei (AGNs) exhibit stochastic variability correlated across a wide range of wavelengths on timescales ranging from days to years. Modeling and understanding AGN variability are critical for probing accretion flows in AGNs, studying supermassive black hole growth, and identifying AGNs in large photometric surveys. The Vera C. Rubin Observatory Legacy Survey of Space and Time (LSST) will monitor tens of millions of AGNs over a 10-year baseline, with an average cadence of three days across six bands. However, existing tools for AGN light-curve modeling are not well suited to the scale, cadence, and multiband nature of Rubin data. In this talk, I will present EzTaoX, a community software package for scalable and flexible Gaussian process (GP) modeling of multiband AGN light curves. I will highlight the technical advances of EzTaoX relative to existing tools and demonstrate several key science applications. Finally, I will discuss recent updates to EzTaoX enabled through the LINCC Frameworks Incubator Program.
+
+LINCC Tech Talks are held on the second Thursday of every month. Events are also advertised at our web page and also provided in calendar form; and the #lincc-tech-talks LSST-DA Slack channel is always available for discussions before, during, and after the talks.",Deferred,olynn@andrew.cmu.edu,,"6/4/26, 2:53 PM",,,,
+"May 28th, 2026 at 2:07 PM UTC","Community News, Interesting Reads-Videos-Podcasts","A blog post on the changing work and continuing value of RSEs in the age of GenAI has been published: S. Druskat, M. Barker, I. Cosden, C. Geng, R. Haines, D. S. Katz, J. Shingleton, B. van Werkhoven, ""Research Software Engineers in the Age of GenAI: Same Value, Changing Practice,"" https://doi.org/10.5281/zenodo.20320178 & https://www.researchsoft.org/blog/2026-05-28/",Published,d.katz@ieee.org,,"5/28/26, 10:07 AM",,,,
+"May 28th, 2026 at 2:03 PM UTC","Community News","The report from the Research Software Engineering in the Age of Generative AI: Building a Community Vision workshop is now available on Zenodo, alongside the reflection: Research Software in an Age of AI-Assisted Development: Reflections from Edinburgh",Published,d.katz@ieee.org,,"5/28/26, 10:03 AM",,,,
+"May 21st, 2026 at 8:05 PM UTC","Interesting Events-Opportunities",https://acl.gov/caregiver-ai-competition,Published,jc.subida@northwestern.edu,,"5/21/26, 4:05 PM",,,,
+"May 20th, 2026 at 10:56 AM UTC","Interesting Reads-Videos-Podcasts","I have overhauled my workshop on managing research software projects and posted it at https://third-bit.com/mrsp/. All the material is CC licensed, there are explicit callouts about managing AI, and I would be very grateful for feedback - thank you in advance.",Published,gvwilson@third-bit.com,,"5/20/26, 6:56 AM",,,,
+"April 23rd, 2026 at 11:45 PM UTC",Introduction-Headline,":tada: We’re proud to celebrate *4,011* US-RSE members today. Thank you to everyone who continues to grow, strengthen, and inspire our research software engineering community!
+
+Check our truly amazing journey: https://us-rse.org/join/
+
+(use the image in https://www.linkedin.com/posts/us-rse_rse-rseng-research-activity-7453206497439825920[…]m=member_desktop&rcm=ACoAAAan3poBQGen6B1TxRvoJA41oRmj-uD42Zc)",Published,pengyins@illinois.edu,,"4/23/26, 7:45 PM",,,,
+"June 8th, 2026 at 9:13 AM UTC","Community News",https://charlas-rse-espanol.github.io/,Published,s.minano@ucl.ac.uk,,"6/8/26, 5:13 AM",,,,
+"April 23rd, 2026 at 4:21 PM UTC","Interesting Events-Opportunities","The IDEAS Productivity project is hosting an upcoming webinar in their HPC Best Practices Series, entitled ""Research Software Sharing, Publication, & Distribution Checklists"" on May 20, from 1:00 - 2:00pm (Eastern Time).
+
+These checklists aim to provide advice and suggestions for good practices applied to different kinds of research software output beyond conventional software management plans. They are designed to integrate into existing workflows and have a tiered structure to help projects reach important minimum standards and go beyond, pushing forward the leading edge in reproducible computing.
+
+There is no cost to attend, but registration is required. For more information, please see the event webpage.",Deferred,bernholdtde@ornl.gov,,"4/23/26, 12:21 PM",,,,
+"April 23rd, 2026 at 12:07 PM UTC","Interesting Reads-Videos-Podcasts","Wilhelm Hasselbring, Daniel S. Katz, and Rob van Nieuwpoort just published an article in Computing in Science & Engineering (CiSE) about Technology Research Software. We suggest that this type of research software is a new category that has emerged, which covers research software developed in technology research. We believe that until now, this category of technology research software has often been overlooked and neglected within the research software engineering community.
+
+W. Hasselbring, D. S. Katz and R. van Nieuwpoort. (2026)
+“Technology Research Software: An Often Overlooked Category of Research Software.”
+Computing in Science & Engineering, 28(1). pp. 94-99.
+
+Article: https://doi.org/10.1109/MCSE.2026.3662117
+
+Open access preprint: https://doi.org/10.48550/arXiv.2604.17506",Published,d.katz@ieee.org,,"4/23/26, 8:07 AM",,,,
+"April 9th, 2026 at 2:40 PM UTC","Community News","The US-RSE Mentorship Working Group is relaunching, and we invite anyone interested in mentorship to get involved. Please fill out our questionnaire at https://forms.gle/31QWyg2aC36dYHYh8, and book your calendar on *May 4, 3:00–3:50 p.m. ET for the kickoff event.* Together, we hope to support professional growth, connection, and mentorship across the US-RSE community!",Deferred,pengyins@illinois.edu,,"4/9/26, 10:40 AM",,,,
+"April 6th, 2026 at 5:16 PM UTC","Interesting Reads-Videos-Podcasts","Because I cannot say it better myself, I shall just quote the first two paragraphs of the final section of the post.
+> The company that sells AI coding tools cannot build a quality product with its own AI coding tools. The percentages were always the pitch, not the product. 80. 90. 95. 100. Nobody asked what 100% actually produces until the source code answered for them.
+> AI amplifies whatever is already there. Good discipline becomes great output. No discipline becomes technical debt at machine speed. Anthropic chose a direction. Go faster. Have Claude check Claude. And when it breaks, go faster still.",Published,mtwest2718@protonmail.com,,"4/6/26, 1:16 PM",,,,
+"March 13th, 2026 at 8:54 PM UTC",Introduction-Headline,"Here at US-RSE, we continue our commitment to Diversity, Equity, and Inclusion. Our community is strengthened by the wide range of experiences, backgrounds, and perspectives that each of our members brings. This March, we are proud to recognize and celebrate the women in Research Software Engineering whose leadership, creativity, and perseverance support and elevate our work.
+
+If you are a woman RSE, we are celebrating you. Your skill and dedication advance research, support teams, and open doors for others who may be building their own paths in technical fields. Your presence and contributions encourage colleagues and future RSEs, sometimes through direct mentorship and sometimes simply by being visible in spaces where representation has not always been guaranteed.
+
+Women in science, engineering, and computing have faced and overcome significant obstacles throughout history. Despite these challenges, women have driven discovery, shaped computing, and changed the course of research and technology. Today, women continue to innovate and lead across academia, national labs, industry, and open source communities, bringing insight and expertise that strengthen the broader research landscape.
+
+We wish all the women in the RSE community a meaningful and joyful Women’s History Month. May this month bring recognition, celebration, and renewed energy. Thank you for your work, your resilience, and the creativity you bring to the community.
+
+-- US-RSE DEI Working Group",Published,lparsons@princeton.edu,,"3/13/26, 4:54 PM",,,,
+"March 2nd, 2026 at 6:25 PM UTC","Interesting Reads-Videos-Podcasts","A new report was released by the Computing Research Association Computing Community Catalyst as an output of a convening last April (which I contributed to): https://cra.org/ccc/wp-content/uploads/sites/2/2026/02/Grand-Challenges-for-the-Convergence-of-Computational-and-Citizen-Science-Research.pdf
+
+More context in the CRA social posts: https://www.linkedin.com/posts/computing-research-association_together-technologies-l[…]mber_desktop_web&rcm=ACoAACf-8YAB_TQMAI0CBxJlJ6uWsDaDM9MqoO4 and https://bsky.app/profile/cra-hq.bsky.social/post/3mfkjhgjw3i2z",Published,jonathan@luxaritas.com,,"3/2/26, 1:25 PM",,,,
+"June 5th, 2026 at 3:34 PM UTC","Interesting Events-Opportunities","PyOhio 2026 is the 19th annual Python Community Conference in Cleveland, Ohio. It will be held at Cleveland State University Student Center on July 25-26, 2026. Details on registration and talks are on the website: https://www.pyohio.org/2026/",Published,anurags85@gmail.com,,"6/5/26, 11:34 AM",,,,
+"June 17th, 2026 at 5:49 PM UTC",Other,"Pride Month is both a celebration and a moment for reflection for the communities we are part of. As the chairs of the DEI Working Group, we welcome everyone to celebrate Pride Month with the US‑RSE community this June and beyond. We also want to take a moment to reflect on what Pride means to me and how it shapes how we think about belonging in our professional communities.
+
+US‑RSE is a community built around shared skills, interests, and goals centered on advancing research through software engineering. While that core set of interests brings us together, we are also a collection of individuals who work across different research domains and parts of the software engineering lifecycle. Each person brings unique strengths and perspectives.
+
+A mix of viewpoints helps teams generate stronger ideas and advance research. That kind of collaboration works best when people feel a sense of belonging.
+
+At the same time, we don’t show up to these communities as just “RSEs.” Each of us brings life experiences, preferences, and unique quirks. You can’t interact with just the “software engineer” side of someone. You interact with the whole person, which means accepting them as they are.
+
+That’s where belonging comes from. It’s not just about being part of a group with shared interests. It’s about being accepted as you are.
+
+Creating that kind of belonging can be challenging in practice, especially when building trust with people who have experienced bias, exclusion, or worse.
+
+That’s why small actions matter. Sharing pronouns, using gender‑neutral language, and taking the time to learn about the people around us can make a real difference. They signal that people are seen, respected, and welcome as part of the community.
+
+For me, Pride is a reminder that this kind of belonging does not happen by accident. It is something we create together through everyday choices.
+
+Pride means different things to different people. To reflect that range of experiences, we invite members of the US‑RSE community to share what Pride means to them and how they think about belonging in their work.
+
+What does Pride mean to you? We’d love to hear your perspective. Feel free to join the conversation on Slack or share on social media using the hashtag `#RSEPride`.
+
+*Community Contributions*
+Research software often involves intensely multidisciplinary collaboration, and, depending on the size of a team, may require the ability to liaison between domains, technical-side, business-side, etc. and _advocate_ whether it's for data integrity processes or for underweighted voices. In my mind this relational communication and openness is very prosocial and qualitatively close to what Pride is all about; I think it's why I feel at home in research software and the surrounding communities.
+– _Michael P. Pascale_",Published,lparsons@princeton.edu,,"6/17/26, 1:49 PM",,,,
+"I'm happy to be able to say that this paper is now published, based on work that was mostly done at a Dagstuhl workshop, and then presented ...",,,Published,d.katz@ieee.org,https://usrse.slack.com/archives/C8ZB01CGH/p1765821363574679?thread_ts=1765821363.574679&cid=C8ZB01CGH,"1/10/26, 7:49 PM",,,,
+":mega: Heads up! The deadline for Talk-only, BYOP, and Posters is this Monday, July 20th
+ *Topic:* Better Documentation Practices for Research Software
+> *Presenter:* Miranda Mundt (Sandia National Laboratories)
+> *Time:* Wednesday, August 19, 11:00 AM - 12:00 PM MST
+> *Registration:* Click here
+The NLS³C CoP fosters collaboration among individuals interacting with software repositories across the U.S. National Labs complex. Our mission is to enhance the development culture by promoting best practices, knowledge sharing, and standards that improve quality and sustainability. We empower developers, project managers, and decision-makers through valuable resources, including monthly webinars. By cultivating a network of early adopters, we aim to drive culture change and transform the software landscape within the National Labs. Check out our wiki (limited to those under the DOE) to see what we have to offer and how you can contribute.
+
+Please forward this announcement along to anyone who might be interested. We look forward to seeing you.
+
+Jason M. Gates (Sandia National Laboratories)",Approved,jmgate@sandia.gov,https://usrse.slack.com/archives/C010P17AZ8A/p1784565610916479,"7/29/26, 1:32 AM",2026-08-19,2026-08-19,"{""originalUrl"":""https:\/\/events.gcc.teams.microsoft.com\/event\/dfd563ee-e0f8-40f7-a553-11838feb4812@7ccb5a20-a303-498c-b0c1-29007381b574"",""attachment"":{},""displayAsUrl"":false,""displayName"":""See here!""}",
+"Metadata for All with Wikidata","Interesting Events-Opportunities","We have an upcoming FORCE11 webinar that may be of interest to folks in the DEI space:
+
+*Metadata for All with Wikidata*
+
+The session will explore how open metadata and Wikidata can support discoverability, accessibility, and representation in research and scholarship, including discussions around neurodiversity, transgender musicians, and linking scholarly outputs in open knowledge systems.",Approved,lparsons@princeton.edu,https://usrse.slack.com/archives/C010P17AZ8A/p1784208177140309,"7/29/26, 1:32 AM",2026-08-26,2026-08-26,"{""originalUrl"":""https:\/\/force11.org\/post\/webinar-metadata-for-all-with-wikidata\/"",""attachment"":{},""displayAsUrl"":false,""displayName"":""LINK""}",
+"APeX Summit 2026","Interesting Events-Opportunities","The APeX Summit (Academy, Parsl, Globus Compute) is the eighth annual community meeting, bringing together researchers, developers, and cyberinfrastructure experts worldwide to discuss experiences using and developing Academy, Parsl, and Globus Compute. The summit will be held as a hybrid meeting on September 14–15, 2026, with the in-person component in Chicago. Full program details are *coming soon*.",Approved,d.katz@ieee.org,https://usrse.slack.com/archives/C010P17AZ8A/p1783960282240599,"7/29/26, 1:30 AM",2026-09-14,2026-09-16,"{""originalUrl"":""https:\/\/parsl-project.org\/parslfest\/apex2026.html"",""attachment"":{},""displayAsUrl"":false,""displayName"":""Check it out!""}","Online, In-person"
+"June 23rd, 2026 at 8:06 PM UTC","Interesting Events-Opportunities","To be held as part of SC26, Chicago, IL, USA and online
+Monday, November 16, 2026, 9:00 am - 12:30 pm CST (UTC-6)
+
+*=== Overview ===*
+
+Research software engineers (RSEs) are critical to the impact of HPC, data science, and the larger scientific community. They have existed for decades, though often not under that name. The past several years, however, have seen the development of the RSE concept, common job titles, and career paths; the creation of professional networks to connect RSEs; and the emergence of RSE groups at universities, national laboratories, and industry.
+
+This workshop will bring together RSEs and allies involved in HPC, from all over the world, to grow the RSE community by establishing and strengthening professional networks of current RSEs and RSE leaders. We'll hear about successes and challenges that RSEs and RSE groups have experienced, and discuss ways to increase awareness of RSE opportunities and improve support for RSEs.
+
+The workshop will be highly interactive, featuring panels, an invited talk, and short submitted talks.
+
+*=== Submissions ===*
+
+We encourage prospective participants to submit abstracts of proposed lightning talks (limit of 1 page, no format prescribed) on topics related to RSE issues. Possible topics include, but are not limited to:
+• Career paths: how do RSEs want to be hired, promoted and evaluated?
+• Building RSE organizations: how to find RSEs in your country/region and how to motivate them to join the network and engage?
+• Supporting RSE organizations: what can be done to help RSEs (and those supporting RSEs) at international, national, regional, and local levels?
+• Supporting RSEs in specific environments: academia, national lab, industry, …
+• Making the business case for RSEs and RSE groups: evidence, case studies, tactics?
+• How do we want funders to support RSE roles and activities?
+• Setting up, funding, sustaining, and managing RSE groups
+• Building in RSE requirements as part of wider research infrastructure
+• Providing research software engineering mentoring and training for both RSEs and researchers
+• Adapting as RSEs to new technology such as AI, quantum, neuromorphic, etc.
+The authors of accepted abstracts will be invited to present lightning talks or participate in panel discussions at the workshop. Note that SC26 is planning an in-person event and presenting in-person is strongly encouraged. A supporting digital experience will accommodate those who cannot attend in-person due to travel restrictions or health concerns.
+
+We particularly encourage submissions from first-time conference presenters, and from members of groups that have historically been underrepresented in the HPC community. The deadline for submissions is Friday, August 7, 2026, at 11:59 PM AoE (UTC-12).
+
+For more information see the workshop website: https://us-rse.org/rse-hpc-2026/.",Published,cferenba@lanl.gov,,"6/23/26, 4:06 PM",,,,
+"Abstracts are now being accepted for DASH/IHDEA 2026, with submissions due by 29 July 2026 11.59pm (Europe/Dublin timezone). Meeting registr...","Interesting Events-Opportunities",,Deferred,rebecca.ringuette.nasa@gmail.com,https://usrse.slack.com/archives/C010P17AZ8A/p1783714980916299,"7/29/26, 1:30 AM",,,,
+"The Inaugural International Research Software Conference (IRSC26) ","Interesting Events-Opportunities","The program is now available for the inaugural International Research Software Conference (IRSC26), convened by the Research Software Alliance (ReSA). The conference takes place 7-8 September 2026 in Sheffield, UK, with remote participation available. IRSC26 is co-located with RSECon26 (9-11 September 2026).",Approved,d.katz@ieee.org,https://usrse.slack.com/archives/C010P17AZ8A/p1783687283269209,"7/29/26, 1:26 AM",2026-09-09,2026-09-11,"{""originalUrl"":""https:\/\/www.researchsoft.org\/irsc\/program\/"",""attachment"":{},""displayAsUrl"":false,""displayName"":""Program Link""}",
+"GenAI in Workshops by The Carpentries","Interesting Events-Opportunities","In response to the growing number of reports we are receiving from our Instructor community about the use of generative AI chatbots by learners at workshops, The Carpentries has launched a bonus module to Instructor Training, GenAI in Workshops, in which instructors will explore what widespread genAI use means for the way they teach.
+In sessions led by expert Carpentries Instructor Trainers, participants will discuss the potential impacts of genAI chatbot use on opportunities for guided practice in a workshop, how expertise affects an individual’s ability to make successful use of genAI tools, how considerations of cognitive load should change in this new context, and how to maintain a positive learning environment in their workshops. The events are highly interactive and designed to build Instructors’ confidence to be proactive in their response to genAI use in their workshops and other teaching settings.
+Their Pricing page has more information on costs, and you can get in touch with them by email to register.",Approved,sarah.stevens@wisc.edu,https://usrse.slack.com/archives/C01833QUB7D/p1782130522303689,"7/29/26, 1:25 AM",,2026-11-05,"{""originalUrl"":""https:\/\/carpentries.org\/blog\/2026\/06\/genai-in-workshops-a-bonus-module-to-instructor-training\/"",""attachment"":{},""displayAsUrl"":false,""displayName"":""Presented by The Carpentries""}",Online
+"The recording is online for those that missed the call yesterday! Remember the deadline for pu...","Community News",,Approved,tinashemtapera@gmail.com,https://usrse.slack.com/archives/CLBDQMJH5/p1783708844454699?thread_ts=1783538116.717289&cid=CLBDQMJH5,"7/29/26, 1:24 AM",,,,
+"Research Software Engineers in HPC (RSE-HPC-2026) workshop @ SC26","Interesting Events-Opportunities","We are excited to announce the Research Software Engineers in HPC (RSE-HPC-2026) workshop, to be held as part of SC26, in Chicago, IL, USA and online, on Monday, November 16, 2026.
+
+We encourage prospective participants to submit abstracts of proposed lightning talks on topics related to RSE issues. The authors of accepted abstracts will be invited to present lightning talks or participate in panel discussions at the workshop. We particularly encourage submissions from first-time conference presenters, and from members of groups that have historically been underrepresented in the HPC community. The deadline for submissions is Friday, August 7, 2026, at 11:59 PM AoE (UTC-12).
+
+• For more information, see the workshop website.",Approved,cferenba@lanl.gov,,"7/23/26, 2:49 PM",2026-08-07,2026-08-07,"{""originalUrl"":""https:\/\/us-rse.org\/rse-hpc-2026\/"",""attachment"":{},""displayAsUrl"":false,""displayName"":""For more information, see the workshop website!""}",
+"*Improving Science Data Processing Through Modern Science Data Systems at AGU 26*","Interesting Events-Opportunities","If you are working on software systems or tools that help transform raw data into scientific discoveries, we encourage you to submit an abstract to our AGU session, *""Improving Science Data Processing Through Modern Science Data Systems.""* This session provides a space to share system designs, open-source tools, and lessons learned. We welcome contributions from across the community—including scientists, developers, engineers, and data stewards.
+
+Please follow this link to submit an abstract: https://agu.confex.com/agu/agu26/in/papers/index.cgi?sessionid=281956. The deadline to submit is *Wednesday, August 5th*",Approved,tinashemtapera@gmail.com,,"7/23/26, 2:24 PM",2026-08-05,2026-08-05,"{""originalUrl"":""https:\/\/agu.confex.com\/agu\/agu26\/in\/papers\/index.cgi?sessionid=281956"",""attachment"":{},""displayAsUrl"":false,""displayName"":""AGU""}",In-person
+"January 19th, 2026 at 5:14 AM UTC","Interesting Reads-Videos-Podcasts","Healthcare pricing remains a significant challenge for providers navigating rising costs, opaque pricing structures, and misaligned incentives. Traditional static pricing models often fail to reflect true patient-specific costs or the value delivered by care, resulting in unpredictable margins and diminished patient satisfaction.
+
+Our recent research presents a *data-driven framework* for optimizing healthcare pricing using advanced machine learning techniques. We examine three distinct strategies — *static pricing*, *dynamic pricing*, and *value-based pricing* — and benchmark them through predictive models built with XGBoost, Random Forest, and Neural Networks.
+
+Key findings show that:
+
+• *Dynamic pricing*, informed by predictive analytics, yields higher margin stability than traditional static models.
+• *Value-based pricing* provides the greatest potential for aligning financial incentives with patient outcomes, rewarding high-quality, efficient care.
+By integrating clinical outcomes, operational efficiency, and patient-specific risk profiles into pricing workflows, this approach offers a *practical roadmap* for healthcare organizations to improve profitability while enhancing transparency and customer value. This research advances the conversation on how analytics can transform pricing from a reactive cost exercise into a strategic, value-focused tool.
+
+Link :
+https://www.researchgate.net/publication/395089456_Optimizing_healthcare_pricing_strate[…]data-driven_approach_to_enhance_margins_and_customer_value",Published,divanshu.mittal@trojans.dsu.edu,,"1/19/26, 12:14 AM",,,,
+"December 8th, 2025 at 4:08 PM UTC","Community and Travel Funds","Building on the success of last year’s first Data Carpentry workshop to ever be offered in Israel, generous funding from the US-RSE Community and Travel Funds enabled the success of a Data Carpentry Metagenomics workshop in October 2025, at Tel Aviv University in Israel. The two-day, hands-on workshop was made possible by a partnership among the US-RSE, the Carpentries, the Israel Research Core Facilities, the George Washington University Libraries, Tel Aviv University, Weizmann Institute of Science (WIS) and ELIXIR.
+
+A key goal of the workshop was to empower local instructors to take on more of the teaching responsibilities. In addition to last year’s instructors Dan Kerchner, a Senior Software Developer and Bioinformatics PhD student from George Washington University in Washington, DC and Dr. Dan Ben-Avraham, head of Israel’s ELIXIR node and head of the WIS Mantoux Institute for Bioinformatics, major sections covering Bash shell and a metagenomics analysis pipeline were taught this year by WIS bioinformaticians Dr. Dayana Yahalomi and Dr. Amir Szitenberg, with support from Dr. Avital Sarusi-Portuguez.
+
+The diverse group of 24 learners from 11 institutions included MS and PhD students, postdoctoral and staff researchers in the life sciences, as well as international students and postdocs from India, Brazil, and the U.S. conducting research at institutions across Israel. Hands-on learning included project data organization for metagenomics, cloud computing, Bash shell, R coding, and applying these skills to process real-world whole-genome sequencing data through a series of command-line analysis tools to determine relative proportions of different taxa of bacteria from samples taken from Cuatro Ciénegas, a unique ecological environment in Mexico. Research computing best practices were emphasized throughout. Participants reported increased skill levels, better understanding of how coding contributes to research reproducibility, higher confidence in applying their new software engineering skills to their research, and a desire for more learning opportunities of this type. We look forward to building on the success of the US-RSE-sponsored workshop and the enthusiasm for more workshops of this type in Israel to further develop RSE skills, connections, and community.
+
+(Photos to include in the newsletter may be accessed at https://drive.google.com/drive/folders/1tv68B2n8cGuvtJAn0BttJ5UcYFQyhu8-?usp=sharing )",Published,kerchner@gwu.edu,,"12/8/25, 11:08 AM",,,,
+"April 21st, 2025 at 11:23 PM UTC","Interesting Reads-Videos-Podcasts","• E. A. Jensen, D. S. Katz, ""Awareness of FAIR and FAIR4RS among international research software funders,"" _Scientific Data_, v.12, 627, 2025. https://doi.org/10.1038/s41597-025-04820-4
+• B. U. Westner, D. R. McCloy, E. Larson, A. Gramfort, D. S. Katz, A. M. Smith, A. Delorme, V. Litvak, S. Makeig, R. Oostenveld, J.-M. Schoffelen, T. Tierney, ""Cycling on the Freeway: The Perilous State of Open-Source Neuroscience Software,"" _Imaging Neuroscience_, 2025. https://doi.org/10.1162/imag_a_00554",Published,d.katz@ieee.org,,"4/21/25, 7:23 PM",,,,
+"May 16th, 2025 at 12:39 PM UTC","Interesting Reads-Videos-Podcasts","There's a new report ""Identifying Gaps in Research Software Policy” (https://doi.org/10.5281/zenodo.15411757) out from the ReSA & RDA PRO4RS Working Group (https://www.rd-alliance.org/groups/rda-resa-policies-in-research-organisations-for-research-software-pro4rs/members/all-members/).
+
+It defines a common framework for research software policy & identifies areas where policies are lacking. The report concludes that there is no single solution that covers all necessary policy aspects. Research organizations can incorporate research software in broader policies and/or create a policy focused on research software.",Published,d.katz@ieee.org,,"5/16/25, 8:39 AM",,,,
+"June 29th, 2025 at 6:10 PM UTC","Introduction-Headline, Interesting Reads-Videos-Podcasts",https://medium.com/@akshaymittal_90606/from-cloud-chaos-to-developer-delight-a-practical-guide-to-building-your-first-internal-ff3d12834ad0,Published,akshaycanodia@gmail.com,,"6/29/25, 2:10 PM",,,,
+"June 29th, 2025 at 6:08 PM UTC","Interesting Reads-Videos-Podcasts",https://medium.com/@akshaymittal_90606/from-cloud-chaos-to-developer-delight-a-practical-guide-to-building-your-first-internal-ff3d12834ad0,Published,akshaycanodia@gmail.com,,"6/29/25, 2:08 PM",,,,
+"June 20th, 2025 at 8:24 PM UTC","Interesting Events-Opportunities","The O*NET Data Collection Program, sponsored by the U.S. Department of Labor, is seeking your input as a potential expert for *Computer and Information Research Scientists and Computer Programmers*. We believe that this is an important project and encourage our members to participate. As the nation’s most comprehensive source of occupational data, O*NET is a *free resource* and provides *instant access* to detailed descriptions on more than 900 occupations that drive the U.S. economy. Visitors include counselors, human resource professionals, researchers, developers, and students, to name a few. Visit O*NET Data Collection to learn more.
+*Occupation:* Computer and Information Research Scientists
+
+*Description:* Conduct research into fundamental computer and information science as theorists, designers, or inventors. Develop solutions to problems in the field of computer hardware and software.
+*Occupation:* Computer Programmers
+*Description:* Create, modify, and test the code and scripts that allow computer applications to run. Work from specifications drawn up by software and web developers or other individuals. May develop and write computer programs to store, locate, and retrieve specific documents, data, and information.
+
+A random sample of experts responding to this request will be invited to complete a set of questionnaires. Experts who are selected and agree to participate will receive a *$40 VISA gift code* and a certificate of appreciation from the U.S. Department of Labor.
+If you are interested in learning more and potentially volunteering, please visit the Computer and Information Research Scientists ONET Volunteer Information Page or the Computer Programmers ONET Volunteer Information Page. Please respond by *7/11/2025*.",Published,sandra.gesing@nd.edu,,"6/20/25, 4:24 PM",,,,
+"May 19th, 2025 at 5:14 PM UTC","Interesting Events-Opportunities","SciOS organizes the first cycle of Open Innovation Sprints, a program designed to produce actionable, community-driven outputs designed to tackle shared ecosystem-level challenges in open source and open science. These sprints are collaborative, fast-paced initiatives bringing together researchers, engineers, designers, community organizers, and users over a six to nine month period. By the end of each sprint, participants release open source solutions, supporting documentation, and sustainability plans, all ready for immediate contributions from the wider community.
+The first sprint kicked off in March and is dedicated to *expanding our collective ability to measure the impact of research software*. This sprint is heavily inspired by the CZI 2023 Software Impact Hackathon.",Published,sandra.gesing@nd.edu,,"5/19/25, 1:14 PM",,,,
+"May 19th, 2025 at 3:57 PM UTC","Organization Founding Membership, Community News, Interesting Events-Opportunities",https://www.meetup.com/acm-austin/,Published,akshaycanodia@gmail.com,,"5/19/25, 11:57 AM",,,,
+"May 19th, 2025 at 3:56 PM UTC","Interesting Reads-Videos-Podcasts",https://medium.com/p/ff3d12834ad0,Published,akshaycanodia@gmail.com,,"5/19/25, 11:56 AM",,,,
+"May 15th, 2025 at 7:00 PM UTC","Interesting Reads-Videos-Podcasts","R. Littauer, G. Wilson, J. Ainali, E. A. AlOmar, S. Arabas, Y. Bellini Saibene, K. Bubendorfer, K. Champion, C. Dillon, J. Helske, P. Huybrechts, D. S. Katz, C. Liao, D. Lippert, F. Liu, P. Marshall, D. R. McCloy, I. McInerney, M. W. Mkaouer, P. Ojha, C. Treude, E. P. White, ""10 quick tips for making your software outlive your job,"" arXiv, 2025. https://doi.org/10.48550/arXiv.2505.06484",Published,d.katz@ieee.org,,"5/15/25, 3:00 PM",,,,
+"July 16th, 2025 at 2:18 PM UTC","Interesting Events-Opportunities, Other","> Are you a scientist who programs?
+>
+> A survey study led by a University of Michigan team is being conducted about scientists programming practices, experiences, and tool usage. The survey should take no more than 10-15 minutes to complete. Participants may opt-into a raffle of five $100 cash awards.
+>
+> Scientists in any research area, career track, and stage (including student research assistants) are invited. Please follow this link to the survey to participate.
+> This study has been reviewed by the University of Michigan IRB. Questions can be directed to code-for-science@umich.edu.
+>
+> Thank you for your time.
+",Published,elleobri@umich.edu,,"7/16/25, 10:18 AM",,,,
+"May 15th, 2025 at 6:59 PM UTC","Interesting Reads-Videos-Podcasts","Y. Perez-Riverol, W. Bittremieux, W. Noble, L. Martens, A. Bilbao, M. Lazear, B. Grüning, D. S. Katz, M. MacCoss, C. Dai, J. Eng, R. Bouwmeester, M. Shortreed, E. Audain, T. Sachsenberg, J. Van Goey, G. Wallmann, B. Wen, L. Käll, W. Fondrie, ""Open-source and FAIR Research Software for Proteomics,"" Journal of Proteome Research, v.24(5), pp. 2222-2234, 2025. https://doi.org/10.1021/acs.jproteome.4c01079",Published,d.katz@ieee.org,,"5/15/25, 2:59 PM",,,,
+"How to build great web apps? How to think about design? It's what I wanted to find out from Brad Frost,
+author of 'Atomic Design', in this e...","Interesting Reads-Videos-Podcasts",,Published,code4thought@proton.me,https://usrse.slack.com/archives/C8ZB01CGH/p1746518452808609,"5/6/25, 9:28 AM",,,,
+":mega: :spack: Calling all Spack users :spack: :mega:
+
+We are running a Spack User Survey for 2025! We’d love to get your feedback so that w...","Interesting Events-Opportunities",,Published,tgamblin@llnl.gov,https://usrse.slack.com/archives/C8ZB01CGH/p1745525136517129,"4/26/25, 2:51 PM",,,,
+"April 26th, 2025 at 1:14 AM UTC","Interesting Events-Opportunities","Registration Link
+
+💭 If you’re wondering what are the most up-to-dated knowledge-centric #AI use cases in health care & life sciences (#HCLS), this event is NOT TO BE MISSED:
+
+The Knowledge Graph Conference (#KGC2025) is lining up the most engaged subject matter experts from Stanford University, Rensselaer Polytechnic Institute, EPAM Systems, AbbVie, Accenture, Schrödinger, Thoughtworks, Scripps Research, The University of Texas at Austin, Graphwise, Bristol Myers Squibb, XponentL Data and ONTOFORCE to us this year on May 6, 2025‼️
+
+Also for the first time, we co-created a satellite venue in San Diego of Southern California 🤗 ",Published,runquan@premiumdiscoverygroup.com,,"4/25/25, 9:14 PM",,,,
+"April 25th, 2025 at 7:07 PM UTC","Interesting Events-Opportunities","A career panel event co-hosted by rOpenSci and Openscapes
+https://ropensci.org/events/datasci-careers-feds/",Published,scottericr@gmail.com,,"4/25/25, 3:07 PM",,,,
+"regarding organizational membership: we have additionally Project Eureka (already also on the website), Open OnDemand as Basic member (Large-scale survey evidence from Germany
+ title-short: Who uses AI in research, and for what?
+ type: article-journal
+ url: "https://www.sciencedirect.com/science/article/pii/S0048733325002100"
+ volume: 55
+- accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Cosden
+ given: Ian A.
+ - family: Holtz
+ given: Elizabeth
+ - family: Bretheim
+ given: Joel U.
+ container-title: Future Generation Computer Systems
+ container-title-short: Future Gener. Comput. Syst.
+ doi: 10.1016/j.future.2026.108574
+ id: cosdenDesigningImplementingComprehensive2026
+ issn: 0167739X
+ issued: 2026-10
+ language: en-US
+ page: 108574
+ title: "Designing and implementing a comprehensive research software
+ engineer career ladder: A case study from Princeton University"
+ title-short: Designing and implementing a comprehensive research
+ software engineer career ladder
+ type: article-journal
+ url: "https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002086"
+ volume: 183
+- abstract: To effect change, the Software Sustainability Institute
+ works with researchers, developers, funders, and infrastructure
+ providers to identify and address key issues with research software.
+ accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Crouch
+ given: Stephen
+ - family: Hong
+ given: Neil Chue
+ - family: Hettrick
+ given: Simon
+ - family: Jackson
+ given: Mike
+ - family: Pawlik
+ given: Aleksandra
+ - family: Sufi
+ given: Shoaib
+ - family: Carr
+ given: Les
+ - family: De Roure
+ given: David
+ - family: Goble
+ given: Carole
+ - family: Parsons
+ given: Mark
+ container-title: Computing in Science & Engineering
+ container-title-short: Comput. Sci. Eng.
+ doi: 10.1109/MCSE.2013.133
+ id: crouchSoftwareSustainabilityInstitute2013
+ issn: 1558-366X
+ issue: 6
+ issued: 2013-11
+ keyword: domain engineering,Domain
+ engineering,maintainability,Programming,reliability,scientific
+ computing,Scientific computing,Software development,software
+ engineering,Software engineering,Software reliability,Training
+ page: 74-80
+ title: "The Software Sustainability Institute: Changing Research
+ Software Attitudes and Practices"
+ title-short: The Software Sustainability Institute
+ type: article-journal
+ url: "https://ieeexplore.ieee.org/document/6731384"
+ volume: 15
+- abstract: Scientists, research institutions, funders, libraries and
+ publishers must all improve software practices.
+ accessed: 2025-11-07
+ annote: |
+ Bandiera_abtest: a\
+ Cg_type: Comment\
+ Subject_term: Computer science, Software, Scientific community,
+ Research management\
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.784Z
+ author:
+ - family: Di Cosmo
+ given: Roberto
+ - family: Granger
+ given: Sabrina
+ - family: Hinsen
+ given: Konrad
+ - family: Jullien
+ given: Nicolas
+ - family: Le Berre
+ given: Daniel
+ - family: Louvet
+ given: Violaine
+ - family: Maumet
+ given: Camille
+ - family: Maurice
+ given: Clémentine
+ - family: Monat
+ given: Raphaël
+ - family: Rougier
+ given: Nicolas P.
+ container-title: Nature
+ doi: 10.1038/d41586-025-03196-0
+ id: dicosmoStopTreatingCode2025
+ issn: 1476-4687
+ issue: 8084
+ issued: 2025-10
+ keyword: Computer science,Research management,Scientific
+ community,Software
+ language: en-US
+ page: 284-286
+ publisher: Nature Publishing Group
+ title: "Stop treating code like an afterthought: Record, share and
+ value it"
+ title-short: Stop treating code like an afterthought
+ type: article-journal
+ url: "https://www.nature.com/articles/d41586-025-03196-0"
+ volume: 646
+- abstract: Research software and its creators have long played a
+ critical role in the advancement of research worldwide. This role is
+ changing in the age of “generative AI” (GenAI), but both the
+ software and the people remain of key importance. Understanding
+ these changes is essential in enabling Research Software Engineers
+ (RSEs) to continue contributing the same high value to the research
+ process and its outputs. Before GenAI, the RSE movement had learned
+ to clearly articulate the value proposition of embedding expert
+ software engineering in research to its stakeholders. This blog post
+ highlights how RSEs use GenAI to increase their capacity in both
+ software engineering and research, and visualize this evolution.
+ While GenAI is changing - perhaps considerably - how RSEs work in
+ practice, their value and the value of their work for research
+ remains steady and likely to increase.
+ accessed: 2026-05-28
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Druskat
+ given: Stephan
+ - family: Barker
+ given: Michelle
+ - family: Cosden
+ given: Ian
+ - family: Geng
+ given: Cunliang
+ - family: Haines
+ given: Robert
+ - family: Katz
+ given: Daniel S.
+ - family: Shingleton
+ given: Joseph
+ - family: Werkhoven
+ given: Ben
+ non-dropping-particle: van
+ doi: 10.5281/zenodo.20320179
+ id: druskatResearchSoftwareEngineers2026
+ issued: 2026-05-28
+ keyword: GenAI,Research,Research software,Research software engineers
+ language: en-US
+ publisher: Zenodo
+ title: "Research Software Engineers in the Age of GenAI: Same Value,
+ Changing Practice"
+ title-short: Research Software Engineers in the Age of GenAI
+ type: report
+ url: "https://zenodo.org/records/20320179"
+- abstract: Research software (also called scientific software) is
+ essential for advancing scientific endeavours. Research software
+ encapsulates complex algorithms and domain-specific knowledge and is
+ a fundamental component of all science. A pervasive challenge in
+ developing research software is technical debt, which can adversely
+ affect reliability, maintainability, and scientific validity.
+ Research software often relies on the initiative of the scientific
+ community for maintenance, requiring diverse expertise in both
+ scientific and software engineering domains. The extent and nature
+ of technical debt in research software are little studied, in
+ particular, what forms it takes, and what the science teams
+ developing this software think about their technical debt. In this
+ paper we describe our multi-method study examining technical debt in
+ research software. We begin by examining instances of self-reported
+ technical debt in research code, examining 28k code comments across
+ nine research software projects. Then, building on our findings, we
+ interview research software engineers and scientists about how this
+ technical debt manifests itself in their experience, and what costs
+ it has for research software and research outputs more generally. We
+ identify nine types of self-admitted technical debt unique to
+ research software, and four themes impacting this technical debt.
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Ernst
+ given: Neil A.
+ - family: Awon
+ given: Ahmed Musa
+ - family: Hingmire
+ given: Swapnil
+ - family: Li
+ given: Ze Shi
+ doi: 10.48550/arXiv.2603.20415
+ id: ernstNatureTechnicalDebt2026
+ issued: 2026-03-20
+ keyword: Computer Science - Software Engineering
+ status: pre-published
+ title: The Nature of Technical Debt in Research Software
+ type: webpage
+ url: "http://arxiv.org/abs/2603.20415"
+- abstract: CCC is hosting a two-day visioning workshop to explore how
+ humans and machines may team up to solve some of the most pressing
+ scientific problems through citizen science, crowdsourcing, and
+ community-engaged science.
+ accessed: 2026-03-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-04-13T15:23:11.431Z
+ author:
+ - family: Forston
+ given: Lucy
+ - family: Shanley
+ given: Lea
+ - family: Berger-Wolf
+ given: Tanya
+ - family: Crowston
+ given: Kevin
+ - family: Jackson
+ given: Corey
+ - family: Savage
+ given: Saiph
+ - family: Griffin
+ given: Haley
+ id: forstonGrandChallengesConvergence2026
+ issued: 2026
+ language: en-US
+ status: pre-published
+ title: Grand Challenges for the Convergence of Computational and
+ Citizen Science Research - CCC
+ type: webpage
+ url: "https://cra.org/ccc/events/grand-challenges-for-the-convergence-of-computational-and-citizen-science-research/"
+- abstract: "Research software has been categorized for various goals.
+ One fundamental dimension of such categorizations is the role that
+ the software plays in the research process. Recently, a new role
+ category has emerged: technology research software, which covers
+ research software developed in technology research. Until now, this
+ category of technology research software has often been overlooked
+ and neglected within the research software engineering community. In
+ this article, we explain technology research software and its
+ primary subroles. Technology readiness levels are an established
+ method of estimating the maturity of technologies, including
+ software systems. For technology research software, these readiness
+ levels define secondary subroles. To illustrate the concept of
+ technology research software and to make it more tangible, we
+ present examples of research software that, depending on its
+ specific use within or outside of research, take on the role of
+ technology research software as well as that of another research
+ software category."
+ accessed: 2026-05-28
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Hasselbring
+ given: Wilhelm
+ - family: Katz
+ given: Daniel S.
+ - family: Nieuwpoort
+ given: Rob
+ non-dropping-particle: van
+ container-title: Computing in Science & Engineering
+ container-title-short: Comput. Sci. Eng.
+ doi: 10.1109/MCSE.2026.3662117
+ id: hasselbringTechnologyResearchSoftware2026
+ issn: 1558-366X
+ issue: 1
+ issued: 2026-01
+ keyword: Research and development,Software development
+ management,Technology planning
+ page: 94-99
+ title: "Technology Research Software: An Often Overlooked Category of
+ Research Software"
+ title-short: Technology Research Software
+ type: article-journal
+ url: "https://ieeexplore.ieee.org/document/11482008"
+ volume: 28
+- abstract: Digital computers store information in the form of bits that
+ can take on one of two values 0 and 1, while quantum computers are
+ based on qubits that are described by a complex wavefunction, whose
+ squared magnitude gives the probability of measuring either 0 or 1.
+ Here, we make the case for a probabilistic computer based on p-bits,
+ which take on values 0 and 1 with controlled probabilities and can
+ be implemented with specialized compact energy-efficient hardware.
+ We propose a generic architecture for such p-computers and emulate
+ systems with thousands of p-bits to show that they can significantly
+ accelerate randomized algorithms used in a wide variety of
+ applications including but not limited to Bayesian networks,
+ optimization, Ising models, and quantum Monte Carlo.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ author:
+ - family: Kaiser
+ given: Jan
+ - family: Datta
+ given: Supriyo
+ container-title: Applied Physics Letters
+ container-title-short: Appl. Phys. Lett.
+ doi: 10.1063/5.0067927
+ id: kaiserProbabilisticComputingPbits2021
+ issn: 0003-6951, 1077-3118
+ issue: 15
+ issued: 2021-10-11
+ keyword: Computer Science - Emerging Technologies,Condensed Matter -
+ Disordered Systems and Neural Networks,Quantum Physics
+ page: 150503
+ title: Probabilistic computing with p-bits
+ type: article-journal
+ url: "http://arxiv.org/abs/2108.09836"
+ volume: 119
+- accessed: 2026-05-28
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Kamali
+ given: "Author: Soudeh"
+ - family: Colegrove
+ given: "Author: Dominique"
+ - family: Voelz
+ given: "Author: Sheri"
+ - family: Fitzgerald
+ given: "Author: Katelyn"
+ id: kamaliCommunitySoftwareFacility
+ language: en-US
+ title: "Community Software Facility Discovery Workshop Report:
+ Scientific software best practices, tools, and culture"
+ title-short: Community Software Facility Discovery Workshop Report
+ type: article-journal
+ url: "https://opensky.ucar.edu/islandora/object/technotes%3A45415"
+- abstract: "Important: This document began as a draft vision statement
+ prepared in advance of the “Research Software Engineering in the Age
+ of Generative AI” workshop, March 2026. It was intended to lead to
+ discussion in the document before and discussion in-person at the
+ workshop, including disagreement, and refinement. The current
+ version of the document is a snapshot of that draft vision statement
+ and some of the discussion. It captures a sense of the identified
+ principles, benefits, challenges, and open questions, rather than
+ having a single point of view that represents all of the workshop
+ attendees and contributors. Not all authors necessarily agree with
+ all the points in the document. A note on terminology: We use
+ AI-assisted software development throughout this document to refer
+ to tools and practices often described as Generative AI, GenAI,
+ LLM-enabled development, or AI-assisted coding. We chose this term
+ because it focuses on the activity we care about here, namely the
+ production, verification, documentation, and maintenance of research
+ software, rather than on a particular technology label or marketing
+ category. Research software, the source code, scripts, computational
+ workflows, and infrastructure that power modern research, have never
+ been more central to human discovery. And the scholarly community
+ (funders, publishers, societies, etc.) increasingly recognizes this,
+ though there is still a long way to go before such recognition is
+ widespread or leads to systemic change. At the same time, in the
+ last few years, the rise of AI-assisted tools, i.e., those that can
+ generate code and documentation by using large language and
+ multimodal trained models, and act in semi-autonomous “agentic
+ modes,” has caused significant disruption in software creation and
+ society at large. These tools raise legitimate questions about
+ training data provenance, licensing, quality, security, attribution,
+ environmental cost, and accountability that are hard to ignore. Yet
+ the conversation around AI-assisted tools too often seems to
+ oscillate between hype and dystopian predictions. Neither of these
+ extremes serve research well. This document also starts from the
+ assumption that these tools are and will continue to be used,
+ regardless of the concerns raised above, and aims to guide further
+ usage within this context. This document outlines some ideas about
+ how research software can and should be produced in the era of
+ AI-assisted research tools by Research Software Engineers,
+ computational researchers, and domain experts writing their own
+ code. It focuses on the software production function: building and
+ maintaining software that meaningfully advances research, but also
+ includes the people involved. Workshop participants discussed both,
+ including the role of RSEs and how it will change, such as
+ leveraging the ADSA/USE-RSE-led Position Statement on Generative AI
+ in the RSE Workplace and related work in this space. We believe that
+ developing a shared vision of the future of research software is
+ urgent: AI tools act as an amplifier of existing practices at every
+ level: individual coding habits, institutional incentives, and the
+ commercial priorities of the companies building these tools –
+ accelerating whatever patterns they encounter, both good and bad.
+ Applied without thought, AI-assisted tools can proliferate bugs,
+ embed and reinforce biases, and generate plausible-looking results
+ faster than our existing systems of peer review and verification can
+ check and absorb them. Applied with care and discipline, it has the
+ potential to expand access to computational methods from those with
+ software development skills to those without them, at least for
+ those who can afford it, and allow all researchers to focus on the
+ work that most requires human skill and judgment."
+ accessed: 2026-05-28
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Katz
+ given: Daniel S.
+ - family: Ahern
+ given: Samantha
+ - family: Barker
+ given: Michelle
+ - family: Cosden
+ given: Ian
+ - family: Druskat
+ given: Stephen
+ - family: Dubey
+ given: Anshu
+ - family: Elmatad
+ given: Yael
+ - family: Geng
+ given: Cunliang
+ - family: Gesing
+ given: Sandra
+ - family: Goble
+ given: Carole
+ - family: Haines
+ given: Robert
+ - family: Hartley
+ given: Kim
+ - family: Hetherington
+ given: James
+ - family: Hodges
+ given: Toby
+ - family: Littauer
+ given: Richard
+ - family: Maimone
+ given: Christina
+ - family: Mandava
+ given: Vani
+ - family: O’Brien
+ given: Elle
+ - family: Price-Whelan
+ given: Adrian
+ - family: Ram
+ given: Karthik
+ - family: Shingleton
+ given: Joseph
+ - family: Smith
+ given: Sue
+ - family: TeBlunthius
+ given: Nathan
+ - family: Van der Walt
+ given: Anelda
+ - family: Werkhove
+ given: Ben
+ non-dropping-particle: van
+ - family: Whitaker
+ given: Kirstie
+ - family: Wu
+ given: Sherry
+ doi: 10.5281/zenodo.20321134
+ id: katzResearchSoftwareAge2026
+ issued: 2026-05-27
+ keyword: generative AI,research software,research software engineering
+ publisher: Zenodo
+ title: "Research Software in an Age of AI-Assisted Development:
+ Reflections from Edinburgh"
+ title-short: Research Software in an Age of AI-Assisted Development
+ type: report
+ url: "https://zenodo.org/records/20321134"
+- abstract: "Scientific claims increasingly rely upon the interplay of
+ code, data, and computational environments. Yet the record of how
+ they are used together is often incomplete, scattered, or lost. This
+ undermines rigor, reproducibility, reusability, and efficiency.
+ Previous approaches have improved the governance of digital objects
+ but do not specify how research objects ought to be structured and
+ managed so they can be re-executed and extended. The community is
+ missing a shared vocabulary for this operational layer. Building on
+ recurrent practices and convergent patterns across disciplines, we
+ formalize seven principles: Self-containment, Tracking,
+ Actionability, Modularity, Portability, Ephemerality, and
+ Distributability (STAMPED). Together they give researchers
+ guidelines for building and assessing research objects that others
+ can trust, rerun, and build upon. We frame each principle as a
+ spectrum so that adoption is incremental and starts from existing
+ practice. We support each principle with normative requirements, an
+ interactive checklist, and a map of enabling tools. As conventions
+ mature, tooling improves, and AI agents become increasingly involved
+ in research workflows, the goals of rigor, reproducibility,
+ reusability, and efficiency are becoming more attainable. STAMPED
+ gives researchers, collaborators, reviewers, and agents a common
+ language, concrete goals, and an aligned direction for making
+ computational research more durable.
+ https://github.com/stamped-principles/stamped-paper/"
+ accessed: 2026-06-15
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.126Z
+ author:
+ - family: Macdonald
+ given: Austin
+ - family: Baker
+ given: Cody
+ - family: To
+ given: Isaac
+ - family: Halchenko
+ given: Yaroslav O
+ id: macdonaldSTAMPEDPrinciplesReproducible2026
+ issued: 2026-05-26
+ keyword: open science,provenance,reproducibility,research objects
+ number: f3h82_v1
+ status: pre-published
+ title: STAMPED principles for reproducible research objects
+ type: webpage
+ url: "https://osf.io/preprints/metaarxiv/f3h82_v1/"
+- accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Martina
+ given: Tobia
+ - family: Saad
+ given: Motaz
+ - family: Rucco
+ given: Chiara
+ - family: Longo
+ given: Antonella
+ container-title: Future Generation Computer Systems
+ container-title-short: Future Gener. Comput. Syst.
+ doi: 10.1016/j.future.2026.108587
+ id: martinaEmpiricalEvaluationLLMs2026
+ issn: 0167739X
+ issued: 2026-10
+ language: en-US
+ page: 108587
+ title: Empirical evaluation of LLMs capabilities for data pipeline
+ generation on Databricks platform
+ type: article-journal
+ url: "https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002219"
+ volume: 183
+- abstract: There has been a resurgence of interest in optical computing
+ over the past decade, both in academia and in industry, with much of
+ the excitement centered around special-purpose optical computers for
+ neural-network processing. Optical computing has been a topic of
+ periodic study for over 50 years, including for neural networks
+ three decades ago, and a wide variety of optical-computing schemes
+ and architectures have been proposed. In this paper we provide a
+ systematic explanation of why and how optics might be able to give
+ speed or energy-efficiency benefits over electronics for computing,
+ enumerating 11 features of optics that can be harnessed when
+ designing an optical computer. One often-mentioned motivation for
+ optical computing – that the speed of light \$c\$ is fast – is not a
+ key differentiating physical property of optics for computing;
+ understanding where an advantage could come from is more subtle. We
+ discuss how gaining an advantage over state-of-the-art electronic
+ processors will likely only be achievable by careful design that
+ harnesses more than one of the 11 features, while avoiding a number
+ of pitfalls that we describe.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ author:
+ - family: McMahon
+ given: Peter L.
+ container-title: Nature Reviews Physics
+ container-title-short: Nat. Rev. Phys.
+ doi: 10.1038/s42254-023-00645-5
+ id: mcmahonPhysicsOpticalComputing2023
+ issn: 2522-5820
+ issue: 12
+ issued: 2023-10-09
+ keyword: Computer Science - Emerging Technologies,Computer Science -
+ Neural and Evolutionary Computing,Physics - Applied
+ Physics,Physics - Optics,Quantum Physics
+ page: 717-734
+ title: The physics of optical computing
+ type: article-journal
+ url: "http://arxiv.org/abs/2308.00088"
+ volume: 5
+- abstract: Writing code that is resistant to being hacked is a
+ challenging task. This book takes you through the entire process in
+ easy-to-learn units, from the principles that underlie secure code,
+ to the design, coding, testing, and evaluation of the code.You can
+ use this book from start to finish as a complete curriculum on
+ software security so it can form the basis of an introductory
+ course.You can also use the book as a tutorial to learn about
+ specific topics, like buffer overflows, injections attacks, or web
+ security. Or, to learn how to use tools that will help you make your
+ code more secure.However you go through this book, it will be a
+ great learning aid and, in later times, a reference book that you
+ can pick up whenever you need to a refresher or to learn a new
+ topic.
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Miller
+ given: Barton P.
+ - family: Heymann
+ given: Elisa R.
+ id: millerIntroductionSoftwareSecurity
+ isbn: 9798195700508
+ language: en-US
+ number-of-pages: 390
+ publisher: Independently published
+ title: Introduction to Software Security
+ type: book
+- annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Mineault
+ given: Patrick
+ id: mineaultGoodResearchCode
+ language: en-US
+ title: Good Research Code handbook
+ type: article-journal
+- abstract: Calls to recognize research software engineers are not new —
+ but such professionals are needed now more than ever.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ container-title: Nature Reviews Physics
+ container-title-short: Nat. Rev. Phys.
+ doi: 10.1038/s42254-025-00852-2
+ id: PhysicsNeedsResearch2025
+ issn: 2522-5820
+ issue: 7
+ issued: 2025-07
+ keyword: Computational science
+ language: en-US
+ page: 349-349
+ publisher: Nature Publishing Group
+ title: Physics needs research software engineers
+ type: article-journal
+ url: "https://www.nature.com/articles/s42254-025-00852-2"
+ volume: 7
+- accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Posada
+ given: Edwin F.
+ - family: Holmen
+ given: John K.
+ - family: Rentschler
+ given: Asa
+ container-title: Future Generation Computer Systems
+ container-title-short: Future Gener. Comput. Syst.
+ doi: 10.1016/j.future.2026.108513
+ id: posadaOakRidgeComputing2026
+ issn: 0167739X
+ issued: 2026-09
+ language: en-US
+ page: 108513
+ title: "Oak Ridge Computing Academy: An HPC cluster deployment and
+ management pilot"
+ title-short: Oak Ridge Computing Academy
+ type: article-journal
+ url: "https://linkinghub.elsevier.com/retrieve/pii/S0167739X26001470"
+ volume: 182
+- abstract: Artificial intelligence is transforming industries and
+ society, but its high energy demands challenge global sustainability
+ goals. Biological intelligence, in contrast, offers both good
+ performance and exceptional energy efficiency. Neuromorphic
+ computing, a growing field inspired by the structure and function of
+ the brain, aims to create energy-efficient algorithms and hardware
+ by integrating insights from biology, physics, computer science, and
+ electrical engineering. This concise and accessible book delves into
+ the principles, mechanisms, and properties of neuromorphic systems.
+ It opens with a primer on biological intelligence, describing
+ learning mechanisms in both simple and complex organisms, then turns
+ to the application of these principles and mechanisms in the
+ development of artificial synapses and neurons, circuits, and
+ architectures. The text also delves into neuromorphic algorithm
+ design, and the unique challenges faced by algorithmic researchers
+ working in this area. The book concludes with a selection of
+ practice problems, with solutions available to instructors online.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ author:
+ - family: Ramanathan
+ given: Shriram
+ - family: Sengupta
+ given: Abhronil
+ id: ramanathanIntroductionNeuromorphicComputing2025
+ isbn: 978-1-009-56434-2
+ issued: 2025
+ publisher: Cambridge University Press
+ publisher-place: Cambridge
+ title: Introduction to Neuromorphic Computing
+ type: book
+ url: "https://www.cambridge.org/core/books/introduction-to-neuromorphic-computing/853942021D89F82AED182F9021E7E0F5"
+- abstract: Beginning in the 1970s, statistician-cum-logician Per
+ Martin-L\\of wrote a series of papers developing what became
+ Martin-L\\of type theory, realizing a system where the distinction
+ between mathematics and programming disappears. Inspired by this
+ vision, this paper introduces dependent type theory (of which
+ Martin-L\\of type theory is an example) to a statistical audience.
+ Examples from statistics and probability theory demonstrate how
+ dependent type theory and an algebraic perspective can unify the
+ theoretical and computational concerns of statistics, ensuring
+ rigorous, machine-checked proofs and executable software.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.785Z
+ author:
+ - family: Saul
+ given: Bradley
+ doi: 10.48550/arXiv.2510.09853
+ id: saulGreatExpectationsUnifying2025
+ issued: 2025-10-10
+ keyword: Statistics - Computation
+ status: pre-published
+ title: "Great expectations: Unifying Statistical Theory and
+ Programming"
+ title-short: Great expectations
+ type: webpage
+ url: "http://arxiv.org/abs/2510.09853"
+- abstract: Scientific advancement depends on a strong foundation of
+ data credibility. However, scientific findings in biomedical
+ research are not always reproducible. Meet the organizations that
+ are promoting best practices and helping researchers perform the
+ highest-quality science.
+ accessed: 2025-11-07
+ annote: |
+ Bandiera_abtest: a\
+ Cg_type: Advertisement Feature\
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ id: SixFactorsAffecting
+ language: en-US
+ title: Six factors affecting reproducibility in life science research
+ and how to handle them
+ type: article-journal
+ url: "https://www.nature.com/articles/d42473-019-00004-y"
+- abstract: "We present the \"Stewardship and Advancement of Programming
+ Systems and Tools\" (S4PST) project report for the calendar years
+ 2024 and 2025. S4PST is dedicated to the stewardship and advancement
+ of Programming Systems and Tools (PST) mainly targeting
+ high-performance computing (HPC) for the scientific community. The
+ project is part of the funded software stewardship organizations
+ (SSOs) selected by ASCR as part of the NGSST program, and a member
+ of CASS: the Consortiumfor the Advancement of Scientific Software."
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Teranishi
+ given: Keita
+ - family: Godoy
+ given: William
+ - family: Valero Lara
+ given: Pedro
+ - family: Schanen
+ given: Michel
+ - family: Applencourt
+ given: Thomas
+ - family: Hueckelheim
+ given: Jan
+ - family: Raffenetti
+ given: Ken
+ - family: Thakur
+ given: Rajeev
+ - family: Videau
+ given: Brice
+ - family: Zhou
+ given: Hui
+ - family: Rouson
+ given: Damian
+ - family: Bonachea
+ given: Dan
+ - family: Hargrove
+ given: Paul
+ - family: Richardson
+ given: Brad
+ - family: Rasmussen
+ given: Katherine
+ - family: Blashcke
+ given: Johannes
+ - family: Laguna
+ given: Ignacio
+ - family: Doerfert
+ given: Johannes
+ - family: Georgakoudis
+ given: Giorgis
+ - family: Parasyris
+ given: Konstantinos
+ - family: Penades
+ given: Kevin
+ - family: Cormick
+ given: Patrick
+ - family: Edelman
+ given: Alan
+ - family: Alomairy
+ given: Rabab
+ - family: Samaroo
+ given: Julian
+ - family: Arndt
+ given: Daniel
+ - family: Denny
+ given: Joel
+ - family: Lebrun-Grandie
+ given: Damien
+ - family: Lee
+ given: Seyong
+ - family: Naughton III
+ given: Thomas
+ - family: Pophale
+ given: Swaroop
+ - family: Parete-Koon
+ given: Suzanne
+ - family: Trott
+ given: Christian
+ - family: Rajamanickam
+ given: Siva
+ - family: Kelley
+ given: Brian
+ - family: Aiken
+ given: Alex
+ - family: Chandrasekaran
+ given: Sunita
+ doi: 10.2172/3016977
+ id: teranishiS4PSTStewardshipAdvancement2026
+ issued: 2026-01-12
+ language: en-US
+ number: ORNL/SPR–2026/4406
+ publisher: Oak Ridge National Laboratory (ORNL), Oak Ridge, TN (United
+ States)
+ title: "S4PST: Stewardship and Advancement for Programming Systems and
+ Tools 2024-2025 Project Report"
+ title-short: S4PST
+ type: report
+ url: "https://www.osti.gov/biblio/3016977"
+---
+
diff --git a/_data/newsletter/blog.yml b/_data/newsletter/blog.yml
new file mode 100644
index 000000000..e69de29bb
diff --git a/_data/newsletter/blogs.bib b/_data/newsletter/blogs.bib
new file mode 100644
index 000000000..a5a2fb8b5
--- /dev/null
+++ b/_data/newsletter/blogs.bib
@@ -0,0 +1,269 @@
+@online{besserHowGenerativeAI,
+ title = {How Generative {{AI}} Is Shaping Research ... | {{Open Research Europe}}},
+ author = {Besser, Stephanie and Jensen, Eric and Katz, Daniel},
+ url = {https://open-research-europe.ec.europa.eu/articles/6-56/v1},
+ urldate = {2026-04-08},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{bortVCBignameProgrammers2026,
+ title = {A {{VC}} and Some Big-Name Programmers Are Trying to Solve Open Source's Funding Problem, Permanently},
+ author = {Bort, Julie},
+ date = {2026-02-26T16:00:00+00:00},
+ url = {https://techcrunch.com/2026/02/26/a-vc-and-some-big-name-programmers-are-trying-to-solve-open-sources-funding-problem-permanently/},
+ urldate = {2026-04-08},
+ abstract = {A group of well-known open source programmers and a VC have launched the Open Source Endowment. They hope this new method will provide funding for good.},
+ langid = {american},
+ organization = {TechCrunch},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{claburnAIStillDoesnt,
+ title = {{{AI}} Still Doesn't Work Very Well in Business, Reckoning Soon},
+ author = {Claburn, Thomas},
+ url = {https://www.theregister.com/2026/03/17/ai_businesses_faking_it_reckoning_coming_codestrap/},
+ urldate = {2026-04-08},
+ abstract = {interview: Codestrap founders say we need to dial down the hype and sort through the mess},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{claburnGitHubWeGoing,
+ title = {{{GitHub}}: {{We}} Going to Train on Your Data after All},
+ shorttitle = {{{GitHub}}},
+ author = {Claburn, Thomas},
+ url = {https://www.theregister.com/2026/03/26/github_ai_training_policy_changes/},
+ urldate = {2026-04-08},
+ abstract = {: As of April 24 you'll be feeding the Octocat unless you opt out},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{CrankGPTLocalHumanpowered,
+ title = {{{CrankGPT}} — {{Local Human-powered AI}}},
+ author = {Squeez Labs},
+ url = {https://crankgpt.com/},
+ urldate = {2026-06-16},
+ abstract = {A human-powered, fully local, fully private AI solution.},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/QGJ3I4WD/crankgpt.com.html}
+}
+
+@online{DozensAmericasLargest2026,
+ title = {Dozens of {{America}}'s Largest Companies Have No Simple Way to Report Security Flaws},
+ author = {Whittaker, Zach},
+ date = {2026-06-19T12:00:34},
+ url = {https://this.weekinsecurity.com/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws/},
+ urldate = {2026-06-29},
+ abstract = {New analysis shows that around one-third of America's Fortune 100 companies do not have a vulnerability disclosure policy, bug bounty, or a dedicated email address for reporting security flaws.},
+ langid = {english},
+ organization = {\textasciitilde this week in security\textasciitilde},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:31:33.542Z},
+ file = {/Users/tit420/Zotero/storage/X3RV4UQU/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws.html}
+}
+
+@online{gesingFindingComputingData2025,
+ title = {Finding {{Computing}} and {{Data Infrastructure}} to {{Get Started}} in {{Data-Intensive Research}}},
+ author = {Gesing, Sandra and Stone, Sarah and Washington, Talitha},
+ date = {2025-11-03},
+ url = {https://academicdatascience.org/resources/community-blog/get-started-in-data-intensive-research/},
+ urldate = {2025-11-07},
+ abstract = {Helpful questions and guide for finding the right resources for your large-scale data or advanced computing project.},
+ langid = {american},
+ organization = {Academic Data Science Alliance},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/WSHTFF98/get-started-in-data-intensive-research.html}
+}
+
+@online{KindofBriefShared00:00:00+0000,
+ title = {A Kind-of Brief Shared Early History of {{US-RSE}}},
+ author = {Sochat, Vanessa and Katz, Daniel S. and Cosden, Ian A. and Maimone, Christina and Ferenbaugh, Charles and Gesing, Sandra and Carver, Jeffrey C. and Hill, Chris and Brewer, Nicole and Vaillancourt, Peter and Carroll, Mark and Elmer, Peter},
+ year = {00:00:00 +0000},
+ url = {https://us-rse.org/2022-02-06-a-brief-history-of-usrse/},
+ urldate = {2026-05-21},
+ abstract = {United States Research Software Engineer Association},
+ langid = {english},
+ organization = {US-RSE},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/DS3WJMXT/2022-02-06-a-brief-history-of-usrse.html}
+}
+
+@online{LeidenDeclarationArtificial2026,
+ title = {Leiden {{Declaration}} on {{Artificial Intelligence}} and {{Mathematics}}},
+ author = {{International Mathematical Union}},
+ date = {2026-08-05},
+ url = {https://leidendeclaration.ai/},
+ urldate = {2026-08-06},
+ abstract = {This declaration calls for action to address the challenges posed by the use of artificial intelligence within mathematics research.},
+ langid = {english},
+ organization = {Leiden Declaration on Artificial Intelligence and Mathematics},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-08-06T02:57:47.352Z},
+ file = {/Users/tit420/Zotero/storage/8SY8H9LJ/leidendeclaration.ai.html}
+}
+
+@online{ManagingResearchSoftware,
+ title = {Managing {{Research Software Projects}}},
+ author = {Wilson, Greg},
+ url = {https://third-bit.com/mrsp/},
+ urldate = {2026-05-28},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/GKTHZ5R8/mrsp.html}
+}
+
+@online{MingKwaiPrototypeOrigin,
+ title = {{{MingKwai}} Prototype, the ‘Origin of {{Chinese}} Computing,’ Finds a Home at {{Stanford}}},
+ url = {https://news.stanford.edu/stories/2025/05/mingkwai-chinese-typewriter-prototype-stanford-libraries},
+ urldate = {2025-11-07},
+ abstract = {Lost for more than half a century, the rare Chinese typewriter whose name means “clear and fast” was discovered in a New York basement and entrusted to Stanford Libraries.},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/FUNW4YLX/mingkwai-chinese-typewriter-prototype-stanford-libraries.html}
+}
+
+@online{nesbittGuidedMeditationDevelopers2026,
+ title = {Guided {{Meditation}} for {{Developers}}},
+ author = {Nesbitt, Andrew},
+ date = {2026-03-15T10:00:00+00:00},
+ url = {https://nesbitt.io/2026/03/15/guided-meditation-for-developers.html},
+ urldate = {2026-04-13},
+ abstract = {A practice for finding peace in your dependency tree.},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{NotsobriefHistoryResearch,
+ title = {A Not-so-Brief History of {{Research Software Engineers}} | {{Software Sustainability Institute}}},
+ author = {Hettrick, Simon},
+ url = {https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0},
+ urldate = {2026-05-21},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/QJB9WWQZ/not-so-brief-history-research-software-engineers-0.html}
+}
+
+@online{openaiOpenAIAcquireAstral2026,
+ title = {{{OpenAI}} to Acquire {{Astral}}},
+ author = {OpenAI},
+ date = {2026-04-08},
+ url = {https://openai.com/index/openai-to-acquire-astral/},
+ urldate = {2026-04-08},
+ abstract = {Accelerates Codex growth to power the next generation of Python developer tools},
+ langid = {american},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{RealScorelineReveals,
+ title = {The {{Real Scoreline}} Reveals Nations Facing Climate Penalties - {{University}} of {{Reading}}},
+ author = {The University of Reading},
+ url = {https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties},
+ urldate = {2026-06-16},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/926BIU3J/The-Real-Scoreline-reveals-nations-facing-climate-penalties.html}
+}
+
+@online{schreinerClaudeCodeReviews2026,
+ title = {Claude {{Code Reviews}} with {{Fable}}},
+ author = {Schreiner, Henry},
+ date = {2026-06-16T20:00:00-04:00},
+ url = {https://iscinumpy.dev/post/claude-code-reviews/},
+ urldate = {2026-06-17},
+ abstract = {Fable came out and then disappeared a couple of days later. In that short time, I managed to run a lot of repository reviews with it, and was really happy with the results. I’ve found and fixed around 400 bugs and 400+ other issues (performance, simplifications, modernizations) across dozens of my projects, making several hundred PRs with a nearly 100\% merge rate on decided PRs.},
+ langid = {english},
+ organization = {ISciNumPy.dev},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-17T16:59:48.292Z},
+ file = {/Users/tit420/Zotero/storage/RI3ZH3FE/claude-code-reviews.html}
+}
+
+@online{SilentScientistWhen2025,
+ title = {The {{Silent Scientist}}: {{When Software Research Fails}} to {{Reach Its Audience}} – {{Communications}} of the {{ACM}}},
+ shorttitle = {The {{Silent Scientist}}},
+ date = {2025-10-10},
+ url = {https://cacm.acm.org/opinion/the-silent-scientist-when-software-research-fails-to-reach-its-audience/},
+ urldate = {2025-11-07},
+ langid = {american},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/FJTWCUCL/the-silent-scientist-when-software-research-fails-to-reach-its-audience.html}
+}
+
+@online{stetskovClaudeCodesSource2025,
+ title = {Claude {{Code}}'s {{Source}}: 3,167-{{Line Function}}, {{Regex Sentiment}}},
+ shorttitle = {Claude {{Code}}'s {{Source}}},
+ author = {Stetskov, Denis},
+ date = {2025-09-19},
+ url = {https://techtrenches.dev/p/the-snake-that-ate-itself-what-claude},
+ urldate = {2026-04-08},
+ abstract = {Anthropic claimed 100\% of Claude Code is AI-written. A source leak exposed a 3,167-line function, regex sentiment analysis, and 250K wasted API calls daily},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{stetskovGreatSoftwareQuality2026,
+ title = {The {{Great Software Quality Collapse}}: {{How We Normalized Catastrophe}}},
+ shorttitle = {The {{Great Software Quality Collapse}}},
+ author = {Stetskov, Denis},
+ date = {2026-04-01},
+ url = {https://techtrenches.dev/p/the-great-software-quality-collapse},
+ urldate = {2026-04-15},
+ abstract = {The Apple Calculator leaked 32GB of RAM.},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.499Z},
+ file = {/Users/tit420/Zotero/storage/VUFBP9NQ/the-great-software-quality-collapse.html}
+}
+
+@online{substackArtificialIntelligenceCan,
+ title = {Artificial {{Intelligence}} Can {{Erase Technical Debt}}},
+ author = {Substack},
+ url = {https://substack.com/home/post/p-193978032},
+ urldate = {2026-04-15},
+ abstract = {Claude Code and I rewrote a nine year old, complex Python project I maintain, in GoLang, in 5 Days},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.499Z},
+ file = {/Users/tit420/Zotero/storage/2K2KH76T/p-193978032.html}
+}
+
+@online{udellHowMakeBest2026,
+ title = {How to Make Best Use of Git and {{GitHub}} for {{AI-assisted}} Software Development},
+ author = {Udell, Jon},
+ date = {2026-06-02T19:41:11+00:00},
+ url = {https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/},
+ urldate = {2026-06-16},
+ abstract = {I’m working on a new tool whose tagline is the title of this post: Make best use of git and GitHub for AI-assisted software development. Called Bram (“Bram runs agents mindfully”)…},
+ langid = {american},
+ organization = {How to make best use of git and GitHub for AI-assisted software development},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:18:22.799Z},
+ file = {/Users/tit420/Zotero/storage/74BXFIZD/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development.html}
+}
+
+@online{UnderstandingAdvancingResearch2025,
+ title = {Understanding and Advancing Research Software Grant Funding Models},
+ date = {2025-07-25},
+ doi = {10.12688/openreseurope.20210.1},
+ url = {https://open-research-europe.ec.europa.eu/articles/5-199/v1},
+ urldate = {2025-11-07},
+ abstract = {Read the latest article version by Daniel S. Katz, Eric A. Jensen, Michelle Barker at Open Research Europe},
+ langid = {english},
+ organization = {Open Research Europe | Open Access Publishing Platform},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/UVZXHIQE/v1.html}
+}
diff --git a/_data/newsletter/blogs.yml b/_data/newsletter/blogs.yml
new file mode 100644
index 000000000..139a8c2b2
--- /dev/null
+++ b/_data/newsletter/blogs.yml
@@ -0,0 +1,362 @@
+---
+nocite: \[@\*\]
+references:
+- accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Besser
+ given: Stephanie
+ - family: Jensen
+ given: Eric
+ - family: Katz
+ given: Daniel
+ id: besserHowGenerativeAI
+ title: How generative AI is shaping research ... \| Open Research
+ Europe
+ type: webpage
+ url: "https://open-research-europe.ec.europa.eu/articles/6-56/v1"
+- abstract: A group of well-known open source programmers and a VC have
+ launched the Open Source Endowment. They hope this new method will
+ provide funding for good.
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Bort
+ given: Julie
+ id: bortVCBignameProgrammers2026
+ issued: 2026-02-26
+ language: en-US
+ publisher: TechCrunch
+ title: A VC and some big-name programmers are trying to solve open
+ source’s funding problem, permanently
+ type: webpage
+ url: "https://techcrunch.com/2026/02/26/a-vc-and-some-big-name-programmers-are-trying-to-solve-open-sources-funding-problem-permanently/"
+- abstract: "interview: Codestrap founders say we need to dial down the
+ hype and sort through the mess"
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Claburn
+ given: Thomas
+ id: claburnAIStillDoesnt
+ language: en-US
+ title: AI still doesn’t work very well in business, reckoning soon
+ type: webpage
+ url: "https://www.theregister.com/2026/03/17/ai_businesses_faking_it_reckoning_coming_codestrap/"
+- abstract: ": As of April 24 you’ll be feeding the Octocat unless you
+ opt out"
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Claburn
+ given: Thomas
+ id: claburnGitHubWeGoing
+ language: en-US
+ title: "GitHub: We going to train on your data after all"
+ title-short: GitHub
+ type: webpage
+ url: "https://www.theregister.com/2026/03/26/github_ai_training_policy_changes/"
+- abstract: A human-powered, fully local, fully private AI solution.
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.125Z
+ author:
+ - family: Labs
+ given: Squeez
+ id: CrankGPTLocalHumanpowered
+ language: en-US
+ title: CrankGPT — Local Human-powered AI
+ type: webpage
+ url: "https://crankgpt.com/"
+- abstract: New analysis shows that around one-third of America’s
+ Fortune 100 companies do not have a vulnerability disclosure policy,
+ bug bounty, or a dedicated email address for reporting security
+ flaws.
+ accessed: 2026-06-29
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-29T15:31:33.542Z
+ author:
+ - family: Whittaker
+ given: Zach
+ id: DozensAmericasLargest2026
+ issued: 2026-06-19
+ language: en-US
+ publisher: ~this week in security~
+ title: Dozens of America’s largest companies have no simple way to
+ report security flaws
+ type: webpage
+ url: "https://this.weekinsecurity.com/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws/"
+- abstract: Helpful questions and guide for finding the right resources
+ for your large-scale data or advanced computing project.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.785Z
+ author:
+ - family: Gesing
+ given: Sandra
+ - family: Stone
+ given: Sarah
+ - family: Washington
+ given: Talitha
+ id: gesingFindingComputingData2025
+ issued: 2025-11-03
+ language: en-US
+ publisher: Academic Data Science Alliance
+ title: Finding Computing and Data Infrastructure to Get Started in
+ Data-Intensive Research
+ type: webpage
+ url: "https://academicdatascience.org/resources/community-blog/get-started-in-data-intensive-research/"
+- abstract: United States Research Software Engineer Association
+ accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Sochat
+ given: Vanessa
+ - family: Katz
+ given: Daniel S.
+ - family: Cosden
+ given: Ian A.
+ - family: Maimone
+ given: Christina
+ - family: Ferenbaugh
+ given: Charles
+ - family: Gesing
+ given: Sandra
+ - family: Carver
+ given: Jeffrey C.
+ - family: Hill
+ given: Chris
+ - family: Brewer
+ given: Nicole
+ - family: Vaillancourt
+ given: Peter
+ - family: Carroll
+ given: Mark
+ - family: Elmer
+ given: Peter
+ id: "KindofBriefShared00:00:00+0000"
+ issued: "00:00:00 +0000"
+ language: en-US
+ publisher: US-RSE
+ title: A kind-of brief shared early history of US-RSE
+ type: webpage
+ url: "https://us-rse.org/2022-02-06-a-brief-history-of-usrse/"
+- abstract: This declaration calls for action to address the challenges
+ posed by the use of artificial intelligence within mathematics
+ research.
+ accessed: 2026-08-06
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-08-06T02:57:47.352Z
+ author:
+ - literal: International Mathematical Union
+ id: LeidenDeclarationArtificial2026
+ issued: 2026-08-05
+ language: en-US
+ publisher: Leiden Declaration on Artificial Intelligence; Mathematics
+ title: Leiden Declaration on Artificial Intelligence and Mathematics
+ type: webpage
+ url: "https://leidendeclaration.ai/"
+- accessed: 2026-05-28
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.721Z
+ author:
+ - family: Wilson
+ given: Greg
+ id: ManagingResearchSoftware
+ title: Managing Research Software Projects
+ type: webpage
+ url: "https://third-bit.com/mrsp/"
+- abstract: Lost for more than half a century, the rare Chinese
+ typewriter whose name means “clear and fast” was discovered in a New
+ York basement and entrusted to Stanford Libraries.
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.785Z
+ id: MingKwaiPrototypeOrigin
+ language: en-US
+ title: MingKwai prototype, the ‘origin of Chinese computing,’ finds a
+ home at Stanford
+ type: webpage
+ url: "https://news.stanford.edu/stories/2025/05/mingkwai-chinese-typewriter-prototype-stanford-libraries"
+- abstract: A practice for finding peace in your dependency tree.
+ accessed: 2026-04-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Nesbitt
+ given: Andrew
+ id: nesbittGuidedMeditationDevelopers2026
+ issued: 2026-03-15
+ title: Guided Meditation for Developers
+ type: webpage
+ url: "https://nesbitt.io/2026/03/15/guided-meditation-for-developers.html"
+- accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Hettrick
+ given: Simon
+ id: NotsobriefHistoryResearch
+ title: A not-so-brief history of Research Software Engineers \|
+ Software Sustainability Institute
+ type: webpage
+ url: "https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0"
+- abstract: Accelerates Codex growth to power the next generation of
+ Python developer tools
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: OpenAI
+ id: openaiOpenAIAcquireAstral2026
+ issued: 2026-04-08
+ language: en-US
+ title: OpenAI to acquire Astral
+ type: webpage
+ url: "https://openai.com/index/openai-to-acquire-astral/"
+- accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T01:04:20.125Z
+ author:
+ - dropping-particle: of
+ family: Reading
+ given: The University
+ id: RealScorelineReveals
+ title: The Real Scoreline reveals nations facing climate penalties -
+ University of Reading
+ type: webpage
+ url: "https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties"
+- abstract: Fable came out and then disappeared a couple of days later.
+ In that short time, I managed to run a lot of repository reviews
+ with it, and was really happy with the results. I’ve found and fixed
+ around 400 bugs and 400+ other issues (performance, simplifications,
+ modernizations) across dozens of my projects, making several hundred
+ PRs with a nearly 100% merge rate on decided PRs.
+ accessed: 2026-06-17
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-17T16:59:48.292Z
+ author:
+ - family: Schreiner
+ given: Henry
+ id: schreinerClaudeCodeReviews2026
+ issued: 2026-06-16
+ language: en-US
+ publisher: ISciNumPy.dev
+ title: Claude Code Reviews with Fable
+ type: webpage
+ url: "https://iscinumpy.dev/post/claude-code-reviews/"
+- accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.785Z
+ id: SilentScientistWhen2025
+ issued: 2025-10-10
+ language: en-US
+ title: "The Silent Scientist: When Software Research Fails to Reach
+ Its Audience – Communications of the ACM"
+ title-short: The Silent Scientist
+ type: webpage
+ url: "https://cacm.acm.org/opinion/the-silent-scientist-when-software-research-fails-to-reach-its-audience/"
+- abstract: Anthropic claimed 100% of Claude Code is AI-written. A
+ source leak exposed a 3,167-line function, regex sentiment analysis,
+ and 250K wasted API calls daily
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Stetskov
+ given: Denis
+ id: stetskovClaudeCodesSource2025
+ issued: 2025-09-19
+ language: en-US
+ title: "Claude Code’s Source: 3,167-Line Function, Regex Sentiment"
+ title-short: Claude Code’s Source
+ type: webpage
+ url: "https://techtrenches.dev/p/the-snake-that-ate-itself-what-claude"
+- abstract: The Apple Calculator leaked 32GB of RAM.
+ accessed: 2026-04-15
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.499Z
+ author:
+ - family: Stetskov
+ given: Denis
+ id: stetskovGreatSoftwareQuality2026
+ issued: 2026-04-01
+ language: en-US
+ title: "The Great Software Quality Collapse: How We Normalized
+ Catastrophe"
+ title-short: The Great Software Quality Collapse
+ type: webpage
+ url: "https://techtrenches.dev/p/the-great-software-quality-collapse"
+- abstract: Claude Code and I rewrote a nine year old, complex Python
+ project I maintain, in GoLang, in 5 Days
+ accessed: 2026-04-15
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.499Z
+ author:
+ - family: Substack
+ id: substackArtificialIntelligenceCan
+ language: en-US
+ title: Artificial Intelligence can Erase Technical Debt
+ type: webpage
+ url: "https://substack.com/home/post/p-193978032"
+- abstract: "I’m working on a new tool whose tagline is the title of
+ this post: Make best use of git and GitHub for AI-assisted software
+ development. Called Bram (“Bram runs agents mindfully”)…"
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:18:22.799Z
+ author:
+ - family: Udell
+ given: Jon
+ id: udellHowMakeBest2026
+ issued: 2026-06-02
+ language: en-US
+ publisher: How to make best use of git; GitHub for AI-assisted
+ software development
+ title: How to make best use of git and GitHub for
+ AI-assisted software development
+ type: webpage
+ url: "https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/"
+- abstract: Read the latest article version by Daniel S. Katz, Eric A.
+ Jensen, Michelle Barker at Open Research Europe
+ accessed: 2025-11-07
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-03-16T02:12:49.786Z
+ doi: 10.12688/openreseurope.20210.1
+ id: UnderstandingAdvancingResearch2025
+ issued: 2025-07-25
+ language: en-US
+ publisher: Open Research Europe \| Open Access Publishing Platform
+ title: Understanding and advancing research software grant funding
+ models
+ type: webpage
+ url: "https://open-research-europe.ec.europa.eu/articles/5-199/v1"
+---
+
diff --git a/_data/newsletter/events-opportunities.yml b/_data/newsletter/events-opportunities.yml
new file mode 100644
index 000000000..115c0bcfa
--- /dev/null
+++ b/_data/newsletter/events-opportunities.yml
@@ -0,0 +1,206 @@
+- expires: '2026-09-02'
+ type: opportunity
+ title: 'HPC Best Practices Webinar: *Rapid Development of a High-Performance Applications
+ Using Python*'
+ when: '2026-09-02'
+ where: Online
+ preamble: |-
+ The HPC Best Practices webinar for September:
+
+ *Rapid Development of a High-Performance Applications Using Python*
+ will be presented by *Joanna Piper Morgan (Nuclear Criticality Safety Division, Lawrence Livermore National Lab)*
+ on *September 02 1:00pm - 2:00pm EDT*
+
+ *Registration*
+
+ Scientific research codes running problems that demand HPC have a human resources problem: the physicist/engineer who develops numerical methods, and the software engineer who develops HPC code for CPUs and GPUs, are the same person. This often means implementing novel numerical methods for HPC applications can take years to implement and test at scale. In this talk we describe how we used Python, Numba, and our own in house event scheduling software to separate the numerical methods developer from the software engineering. We will detail our JIT compilation structure for CPUs and GPUs (both NVIDIA and AMD), technical roadblocks, and lessons learned from this software engineering scheme in the development of the MC/DC Monte Carlo neutronics code. We will also briefly mention how this workflow (conceived and designed before the broad acceptance of LLM) fits into a research environment increasingly supported by AI tools.
+
+ *Details:* ideas-productivity.org/events/hpcbp-100-python
+ links: '[LINK](https://ideas-productivity.org/events/hpcbp-100-python)'
+ index: 1
+- expires: '2026-10-14'
+ type: opportunity
+ title: Nextflow is hosting their own "conference" and it's free virtually!
+ when: '2026-10-13'
+ where: Online
+ preamble: |-
+ Virtual Nextflow Summit is the premier global gathering of the Nextflow community—accessible from anywhere. Join researchers, developers, and industry leaders from across pharma and biotech as they share cutting-edge research, innovative solutions, and real-world applications.
+
+ Whether you're building pipelines, analyzing data, or leading teams, connect with the community, learn from the best, and walk away with fresh ideas, new skills, and the momentum to advance your work.
+ links: '[link](https://summit.nextflow.io/2026/virtual/overview)'
+ index: 2
+- expires: '2026-08-19'
+ type: event
+ title: 'NLS³C CoP Webinar: Better Documentation Practices for Research Software'
+ when: '2026-08-19'
+ where: Online
+ preamble: |-
+ Join us for the next webinar of the National Laboratories Sustainable Scientific Software Conference's Community of Practice, as Miranda Mundt introduces us to Better Documentation Practices for Research Software.
+
+ We've all been there: handed a piece of code that promises to do something remarkable, only to find not a single line explaining how. Hours disappear into reverse-engineering what a few sentences could have told us. In research, where software increasingly underpins our most important discoveries, documentation is what separates work that others can build on from work that dies with its author. And in an era where generative AI can draft a docstring or a README in seconds, the challenge has quietly shifted: the bottleneck is no longer writing the words, but knowing whether they're actually true, clear, and useful to the person on the other side. Join us for this session on writing documentation well, and discover how a modest investment in clarity today pays dividends across the life of your research.
+
+ > *Topic:* Better Documentation Practices for Research Software
+ > *Presenter:* Miranda Mundt (Sandia National Laboratories)
+ > *Time:* Wednesday, August 19, 11:00 AM - 12:00 PM MST
+ > *Registration:* Click here
+ The NLS³C CoP fosters collaboration among individuals interacting with software repositories across the U.S. National Labs complex. Our mission is to enhance the development culture by promoting best practices, knowledge sharing, and standards that improve quality and sustainability. We empower developers, project managers, and decision-makers through valuable resources, including monthly webinars. By cultivating a network of early adopters, we aim to drive culture change and transform the software landscape within the National Labs. Check out our wiki (limited to those under the DOE) to see what we have to offer and how you can contribute.
+
+ Please forward this announcement along to anyone who might be interested. We look forward to seeing you.
+
+ Jason M. Gates (Sandia National Laboratories)
+ links: '[See here!](https://events.gcc.teams.microsoft.com/event/dfd563ee-e0f8-40f7-a553-11838feb4812@7ccb5a20-a303-498c-b0c1-29007381b574)'
+ index: 3
+- expires: '2026-08-26'
+ type: event
+ title: Metadata for All with Wikidata
+ when: '2026-08-26'
+ where: Online
+ preamble: |-
+ We have an upcoming FORCE11 webinar that may be of interest to folks in the DEI space:
+
+ *Metadata for All with Wikidata*
+
+ The session will explore how open metadata and Wikidata can support discoverability, accessibility, and representation in research and scholarship, including discussions around neurodiversity, transgender musicians, and linking scholarly outputs in open knowledge systems.
+ links: '[LINK](https://force11.org/post/webinar-metadata-for-all-with-wikidata/)'
+ index: 4
+- expires: '2026-09-16'
+ type: event
+ title: APeX Summit 2026
+ when: '2026-09-14'
+ where: Online, In-person
+ preamble: The APeX Summit (Academy, Parsl, Globus Compute) is the eighth annual
+ community meeting, bringing together researchers, developers, and cyberinfrastructure
+ experts worldwide to discuss experiences using and developing Academy, Parsl,
+ and Globus Compute. The summit will be held as a hybrid meeting on September 14–15,
+ 2026, with the in-person component in Chicago. Full program details are *coming
+ soon*.
+ links: '[Check it out!](https://parsl-project.org/parslfest/apex2026.html)'
+ index: 5
+- expires: '2026-09-11'
+ type: event
+ title: The Inaugural International Research Software Conference (IRSC26)
+ when: '2026-09-09'
+ where: In Person
+ preamble: The program is now available for the inaugural International Research
+ Software Conference (IRSC26), convened by the Research Software Alliance (ReSA).
+ The conference takes place 7-8 September 2026 in Sheffield, UK, with remote participation
+ available. IRSC26 is co-located with RSECon26 (9-11 September 2026).
+ links: '[Program Link](https://www.researchsoft.org/irsc/program/)'
+ index: 6
+- expires: '2026-11-05'
+ type: event
+ title: GenAI in Workshops by The Carpentries
+ when: '2026-08-01'
+ where: Online
+ preamble: |-
+ In response to the growing number of reports we are receiving from our Instructor community about the use of generative AI chatbots by learners at workshops, The Carpentries has launched a bonus module to Instructor Training, GenAI in Workshops, in which instructors will explore what widespread genAI use means for the way they teach.
+ In sessions led by expert Carpentries Instructor Trainers, participants will discuss the potential impacts of genAI chatbot use on opportunities for guided practice in a workshop, how expertise affects an individual’s ability to make successful use of genAI tools, how considerations of cognitive load should change in this new context, and how to maintain a positive learning environment in their workshops. The events are highly interactive and designed to build Instructors’ confidence to be proactive in their response to genAI use in their workshops and other teaching settings.
+ Their Pricing page has more information on costs, and you can get in touch with them by email to register.
+ links: '[Presented by The Carpentries](https://carpentries.org/blog/2026/06/genai-in-workshops-a-bonus-module-to-instructor-training/)'
+ index: 7
+- expires: '2026-08-07'
+ type: opportunity
+ title: Research Software Engineers in HPC (RSE-HPC-2026) workshop @ SC26
+ when: '2026-08-07'
+ where: Online
+ preamble: |-
+ We are excited to announce the Research Software Engineers in HPC (RSE-HPC-2026) workshop, to be held as part of SC26, in Chicago, IL, USA and online, on Monday, November 16, 2026.
+
+ We encourage prospective participants to submit abstracts of proposed lightning talks on topics related to RSE issues. The authors of accepted abstracts will be invited to present lightning talks or participate in panel discussions at the workshop. We particularly encourage submissions from first-time conference presenters, and from members of groups that have historically been underrepresented in the HPC community. The deadline for submissions is Friday, August 7, 2026, at 11:59 PM AoE (UTC-12).
+
+ • For more information, see the workshop website.
+ links: '[For more information, see the workshop website!](https://us-rse.org/rse-hpc-2026/)'
+ index: 8
+- expires: '2026-08-12'
+ type: event
+ title: 'User-Facing Tutorials as Code: Reproducible and Reliable Tutorials with
+ CI/CD'
+ when: '2026-08-12'
+ where: Online
+ preamble: User-facing tutorials typically combine code, narrative text, execution
+ results, and visualizations. However, the target audience for these tutorials
+ can vary significantly. Some tutorials serve as documentation for libraries, accessed
+ by users during asynchronous learning, while others are designed for one-off workshops
+ deployed on specific scientific platforms. This talk presents best practices for
+ maintaining reliable and reproducible executable tutorials, developed as part
+ of a Scientific Python Ecosystem Coordination (SPEC) document. These guidelines
+ distinguish between different types of tutorials and workshop materials, offering
+ targeted recommendations for each category
+ links: '[LINK](https://ideas-productivity.org/events/hpcbp-099-tutorials)'
+ index: 9
+- expires: '2026-10-09'
+ type: event
+ title: 2026 DASH / IHDEA Meeting
+ when: October 5-9, 2026
+ where: Dublin, Ireland, and virtual
+ preamble: "Save the date! \U0001F4C5\n\nThe 2026 DASH / IHDEA Meeting will take
+ place 5-9 October 2026, hosted by the Dublin Institute for Advanced Studies (DIAS)
+ in Dublin, Ireland, with virtual participation supported. \U0001F973\n\nThe DASH
+ (Data Analysis and Software in Heliophysics) and IHDEA (International Heliophysics
+ Data Environment Alliance) meetings bring together scientists and software developers
+ working on data analysis, algorithms, community software, data systems, and standards
+ across heliophysics - from the Sun to geospace and beyond. We invite the full
+ solar and heliophysics data, software, and science community to join us. More
+ details coming soon, including a call for session proposals.\n"
+ links: |
+ For more information, visit: [dash.heliophysics.net](https://dash.heliophysics.net/) and [ihdea.net](https://ihdea.net/).
+ index: 10
+- expires: '2026-12-31'
+ type: opportunity
+ title: "Supercomputing and the Future of AI: Watch the Full Virtual Exchange Series
+ On-Demand! \U0001F916"
+ when: .na.character
+ where: .na.character
+ preamble: |
+ Our exciting webinar series for K–12 classrooms, presented in partnership with Reach the World, has officially wrapped! Over the past ten weeks, more than 840 students joined us to explore the fascinating world of supercomputing, quantum computing, and artificial intelligence.
+
+ Now, all episodes are available to watch on-demand along with companion journal articles that bring the topics to life for students, educators, and curious minds of all ages. Together with Reach the World, US-RSE created this virtual exchange to offer a behind-the-scenes look at how research software engineers and data scientists use cutting-edge computing to tackle real-world challenges.
+ links: |
+ Learn more at [ReachTheWorld.org](https://reachtheworld.org/supercomputing-and-future-ai-0), and please reach out to [Sandra Gesing](mailto:sandra@us-rse.org) with any questions
+ index: 11
+- expires: '2026-12-30'
+ type: opportunity
+ title: Contribute to the future of DEI in US-RSE
+ when: .na.character
+ where: .na.character
+ preamble: |
+ The US-RSE DEI Working Group is seeking input from the community! We’re exploring new ways to foster diversity, equity, and inclusion within our organization and would love to hear your ideas. What would make US-RSE a more inclusive and welcoming space for you and others?
+
+ Let’s work together to make US-RSE a place where everyone feels they belong.
+ links: |
+ If you have suggestions, big or small, please share them in the #dei-discussion Slack channel or reach out directly to the [DEI Working Group](mailto:wg-dei@us-rse.org). Your feedback will help guide our future initiatives and ensure they reflect the needs of our diverse community.
+ index: 12
+- expires: '2026-09-25'
+ type: opportunity
+ title: Gateways 2026 Call for Participation and Registration Open
+ when: .na.character
+ where: .na.character
+ preamble: |
+ The Gateways 2026 Conference Call for Participation and registration are now live! For a decade, the Gateways conference has served as a central meeting place for creators and users of science gateways. This year’s conference highlights the growing integration of Artificial Intelligence alongside continued advances in community development, education, and interoperability.
+ Join the community in Washington, DC, September 23–25, 2026, to share solutions, tackle challenges, and build connections that will power the next generation of research.
+
+ Key dates and deadlines:
+ - Tutorials — May 22, 2026
+ - Papers — June 8, 2026
+ - Talk-only, BYOP, and Posters — July 20, 2026
+
+ Can't attend the full conference? Free Virtual Tutorials sessions will be held September 1–3 and September 8–11, 2026.
+ links: |
+ Conference details: [Click here](https://sciencegateways.org/gateways2026)
+ Registration: [Click here](https://na.eventscloud.com/ereg/newreg.php?eventid=874568&)
+ index: 13
+- expires: '2026-08-30'
+ type: opportunity
+ title: IJPP Special Issue on High-Productivity Programming Systems for HPC Applications
+ when: .na.character
+ where: .na.character
+ preamble: |
+ The International Journal of Parallel Programming (IJPP) is accepting submissions for a special issue on “High-Productivity Programming Systems for HPC Applications.” The issue focuses on programming languages, models, and software systems that improve productivity while addressing the performance, power, scalability, and reliability challenges of modern and future high-performance computing systems.
+
+ Topics of interest include exascale programming systems, parallel programming models, performance tuning, power management, fault tolerance, self-aware software systems, and approaches for exploiting massive parallelism in HPC applications.
+
+ Researchers and practitioners in HPC, scientific computing, and research software engineering are encouraged to submit.
+
+ Submission deadline (extended): August 30, 2026.
+ links: 'Journal and submission information: [Click here](https://link.springer.com/journal/10766/updates/27768048)'
+ index: 14
diff --git a/_data/newsletter/media.bib b/_data/newsletter/media.bib
new file mode 100644
index 000000000..bf0ac0662
--- /dev/null
+++ b/_data/newsletter/media.bib
@@ -0,0 +1,203 @@
+@audio{ByteSizedCreateYour2026,
+ title = {[{{EN}}] {{ByteSized}}: Create Your Web-Site with {{GitHub Pages}} - {{J Cohen}}, {{S Gibson}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-05-19},
+ url = {https://www.buzzsprout.com/1326658/episodes/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson},
+ urldate = {2026-05-21},
+ abstract = {English Edition:\ In this ByteSized episode \& online class we're talking about GitHub Pages and how it can help you to create a web-site for your research project (reasonably) quickly. With me are Sarah Gibson and Jeremy Cohen.\ I'd li...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/2EWWF4FT/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson.html}
+}
+
+@video{casscommunityAITeamworkTooling2026,
+ entrysubtype = {video},
+ title = {{{AI}} Teamwork and Tooling for Research Software Engineers},
+ namea = {{CASS Community}},
+ nameatype = {collaborator},
+ date = {2026-03-04},
+ url = {https://www.youtube.com/watch?v=Xq93CVDCuds},
+ urldate = {2026-04-08},
+ abstract = {Presentations by Olivia Newton (University of Montana) and Andrew Schmeder (LBNL) on March 3 in the Consortium for the Advancement of Scientific Software (CASS; https://cass.community/) User/Developer Experience working group. The speakers discuss research software engineers, how they work in teams with AI tools, and what performance they can expect from AI t},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@video{clusterraBioChemreadySlurmCluster2026,
+ entrysubtype = {video},
+ title = {{{BioChem-ready}} {{Slurm Cluster}} in Minutes — {{Clusterra Walkthrough}}},
+ namea = {{Clusterra}},
+ nameatype = {collaborator},
+ date = {2026-04-25},
+ url = {https://www.youtube.com/watch?v=a1-GGm3tAbI},
+ urldate = {2026-06-29},
+ abstract = {A 1:49 walkthrough of the Clusterra console: from an empty AWS account to a running Slurm cluster, a submitted job, and a live JupyterLab notebook — all in your own AWS, same day.},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:29:59.361Z}
+}
+
+@audio{ComputingNotYou2026,
+ title = {[{{EN}}] {{Computing}}, but Not as You Know It: {{Field Programmable Gate Arrays}} ({{FPGA}}) - with {{Michael McLeod}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Computing}}, but Not as You Know It},
+ author = {Schmidt, Peter},
+ date = {2026-05-05},
+ url = {https://www.buzzsprout.com/1326658/episodes/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-mcleod},
+ urldate = {2026-05-21},
+ abstract = {English Edition: In a follow up about "unusual" computers I want to focus on field programmable gate arrays - FPGAs. With my guest and former colleague at UCL, Michael McLeod, we talk about what they are, where they are used and what's so special ...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/HFYACMW9/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-m.html}
+}
+
+@audio{DoesSpecDrivenDevelopment2026,
+ title = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile? {{With Graham Lee}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile?},
+ author = {Schmidt, Peter},
+ date = {2026-06-02},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee},
+ urldate = {2026-06-16},
+ abstract = {English Edition: Will spec-driven development replace agile processes? My guest Graham Lee\ (https://chironcodex.com/ ) and I discuss if there is still a place for agile software engineering in a world of AI assisted coding.Links:https://mart...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/QWCZ298A/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee.html}
+}
+
+@audio{ManagingPackagesPixi2026,
+ title = {[{{EN}}] {{Managing Packages}} with {{Pixi}} - {{Raniere}} de {{Silva}} and {{Wolf Vollprecht}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-05-12},
+ url = {https://www.buzzsprout.com/1326658/episodes/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht},
+ urldate = {2026-05-21},
+ abstract = {English Edition:\ there is a (relatively) new kid on the block - of open source package managers. It's called Pixi: and in this episode I talk to Raniere de Silva (GESIS) and Wolf Vollprecht (Prefix - the company behind Pixi), what the tool br...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/8C38H95J/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht.html}
+}
+
+@unpublished{ruchtiUSRSE25Rapid2025,
+ title = {{{USRSE}} 25 Rapid Access Micro Talks},
+ author = {Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula and Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula},
+ date = {2025-10-08},
+ doi = {10.5281/zenodo.17297728},
+ url = {https://zenodo.org/records/17297728},
+ urldate = {2026-04-09},
+ abstract = {Slide set of the accepted rapid access micro talks at USRSE 25.},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-09T23:30:44.373Z},
+ file = {/Users/tit420/Zotero/storage/G5VLTKTU/Ruchti et al. - 2025 - USRSE 25 rapid access micro talks.pdf}
+}
+
+@audio{schmidtByteSizedFunFloating2026,
+ title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-31},
+ url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
+ urldate = {2026-04-13},
+ abstract = {English Edition: how are real numbers e.g. 0.1 represented on computers? What can go wrong with using their representation in calculations? And does it matter? These and other questions are the subject of this ByteSized episode with my guests Prof...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/PTLJK4KV/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli.html}
+}
+
+@audio{schmidtByteSizedFunFloating2026a,
+ title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-31},
+ url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
+ urldate = {2026-04-13},
+ abstract = {English Edition: how are real numbers e.g. 0.1 represented on computers? What can go wrong with using their representation in calculations? And does it matter? These and other questions are the subject of this ByteSized episode with my guests Prof...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/TPXCRML4/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli.html}
+}
+
+@audio{schmidtByteSizedHowGet2026,
+ title = {[{{EN}}] {{ByteSized}}: How to Get Your (Digital) Ducks in a Row - with {{Richard Acton}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-03},
+ url = {https://www.buzzsprout.com/1326658/episodes/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton},
+ urldate = {2026-03-16},
+ abstract = {English Edition (ByteSized): In this first episode of the new ByteSized dRTP season, sponsored by the STEP-UP programme from the EPSRC (UK) you'll meet Richard Acton. Richard created a tool to help you keep track of all the steps you should take t...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-13T15:23:08.156Z},
+ file = {/Users/tit420/Zotero/storage/44JQ455Z/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton.html}
+}
+
+@audio{schmidtNextBrainExploringHuman2026,
+ title = {[{{EN}}] {{NextBrain}}: Exploring the Human Brain - {{Eugenio Iglesias}}, {{James Hughes}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{NextBrain}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-17},
+ url = {https://www.buzzsprout.com/1326658/episodes/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes},
+ urldate = {2026-04-13},
+ abstract = {English Edition:\ NextBrain is a next generation atlas of the human brain. Juan Eugenio Iglesias Gonzales from Massachusetts General in Boston, US, has been leading this project. My colleague James Hughes (University College London) and I were...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/MV3BC6VR/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes.html}
+}
+
+@audio{schmidtRevealingStructureCrystals2026,
+ title = {[{{EN}}] {{Revealing}} the Structure of Crystals and Proteins with {{CrystFEL}} - {{Thomas White}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-10},
+ url = {https://www.buzzsprout.com/1326658/episodes/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white},
+ urldate = {2026-03-16},
+ abstract = {English Edition:\ Meet Thomas White from DESY (German Electron Synchrotron) who is the creator and maintainer of the tool CrystFEL. The tool to help understand and analyse the structure of materials such as crystals and proteins. Thomas and I ...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-13T15:23:08.155Z},
+ file = {/Users/tit420/Zotero/storage/DSPJ2H3G/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white.html}
+}
+
+@audio{schmidtTeamPortraitResearch2026,
+ title = {[{{EN}}] {{Team Portrait}}: {{Research Software Engineering}} in {{Newcastle}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Team Portrait}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-24},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/18761138-en-team-portrait-research-software-engineering-in-newcastle},
+ urldate = {2026-04-13},
+ abstract = {English Edition:\ for this episode we're going "up North", to visit the Research Software Engineering team of the University of Newcastle. The team has been hosting the UK RSE Conference in 2022 and 2024 and here is a chance to meet at least s...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/ZST9FS63/18761138-en-team-portrait-research-software-engineering-in-newcastle.html}
+}
+
+@audio{WhatHappenedAgile2026,
+ title = {[{{EN}}] {{What}} Happened to Agile Development? - {{A}} Review with {{Dave Thomas}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{What}} Happened to Agile Development?},
+ author = {Schmidt, Peter},
+ date = {2026-06-16},
+ url = {https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas},
+ urldate = {2026-06-16},
+ abstract = {English Edition:\ I want to come back to agile development practices with my guest Dave Thomas, or Pragmatic Dave as he is also known in the trade. Dave is one of the authors of the manifesto for agile development - and we talk about what has ...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/NBJV5ZD6/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas.html}
+}
+
+@audio{WhenBitsRot2026,
+ title = {[{{EN}}] {{When Bits Rot}} - with {{C McKean}}, {{L Talboom}}, {{A Page-Mitchell}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-06-09},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell},
+ urldate = {2026-06-16},
+ abstract = {English Edition: floppy disks, hard drives, CDs, DVDs, SSD drives - no matter what you choose to store your data on - ultimately they all decay. With my guests Callum McKean, Leontien Talboom and Adrian Page-Mitchell, we're going to talk about wha...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/YGL4ZLC9/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell.html}
+}
diff --git a/_data/newsletter/media.yml b/_data/newsletter/media.yml
new file mode 100644
index 000000000..0e78d0c0a
--- /dev/null
+++ b/_data/newsletter/media.yml
@@ -0,0 +1,308 @@
+---
+nocite: \[@\*\]
+references:
+- abstract: "English Edition:\\ In this ByteSized episode \\&
+ online class we’re talking about GitHub Pages and how it can help
+ you to create a web-site for your research project (reasonably)
+ quickly. With me are Sarah Gibson and Jeremy Cohen.\\ I’d li..."
+ accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: ByteSizedCreateYour2026
+ issued: 2026-05-19
+ language: en-US
+ title: "\\[EN\\] ByteSized: Create your web-site with GitHub Pages - J
+ Cohen, S Gibson - Code for Thought"
+ title-short: \[EN\] ByteSized
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson"
+- abstract: "Presentations by Olivia Newton (University of Montana) and
+ Andrew Schmeder (LBNL) on March 3 in the Consortium for the
+ Advancement of Scientific Software (CASS; https://cass.community/)
+ User/Developer Experience working group. The speakers discuss
+ research software engineers, how they work in teams with AI tools,
+ and what performance they can expect from AI t"
+ accessed: 2026-04-08
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ id: casscommunityAITeamworkTooling2026
+ issued: 2026-03-04
+ title: AI teamwork and tooling for research software engineers
+ type: motion_picture
+ url: "https://www.youtube.com/watch?v=Xq93CVDCuds"
+- abstract: "A 1:49 walkthrough of the Clusterra console: from an empty
+ AWS account to a running Slurm cluster, a submitted job, and a live
+ JupyterLab notebook — all in your own AWS, same day."
+ accessed: 2026-06-29
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-29T15:29:59.361Z
+ id: clusterraBioChemreadySlurmCluster2026
+ issued: 2026-04-25
+ title: BioChem-ready Slurm Cluster in
+ minutes — Clusterra Walkthrough
+ type: motion_picture
+ url: "https://www.youtube.com/watch?v=a1-GGm3tAbI"
+- abstract: "English Edition: In a follow up about \"unusual\" computers I
+ want to focus on field programmable gate arrays - FPGAs. With my
+ guest and former colleague at UCL, Michael McLeod, we talk about
+ what they are, where they are used and what’s so special ..."
+ accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: ComputingNotYou2026
+ issued: 2026-05-05
+ language: en-US
+ title: "\\[EN\\] Computing, but not as you know it: Field Programmable
+ Gate Arrays (FPGA) - with Michael McLeod - Code for Thought"
+ title-short: \[EN\] Computing, but not as you know it
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-mcleod"
+- abstract: "English Edition: Will spec-driven development replace agile
+ processes? My guest Graham Lee\\ (https://chironcodex.com/ )
+ and I discuss if there is still a place for agile software
+ engineering in a world of AI assisted coding.Links:https://mart..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: DoesSpecDrivenDevelopment2026
+ issued: 2026-06-02
+ language: en-US
+ title: \[EN\] Does Spec-Driven Development replace agile? With Graham
+ Lee - Code for Thought
+ title-short: \[EN\] Does Spec-Driven Development replace agile?
+ type: song
+ url: "https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee"
+- abstract: "English Edition:\\ there is a (relatively) new kid on
+ the block - of open source package managers. It’s called Pixi: and
+ in this episode I talk to Raniere de Silva (GESIS) and Wolf
+ Vollprecht (Prefix - the company behind Pixi), what the tool br..."
+ accessed: 2026-05-21
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-06-15T23:59:08.722Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: ManagingPackagesPixi2026
+ issued: 2026-05-12
+ language: en-US
+ title: \[EN\] Managing Packages with Pixi - Raniere de Silva and Wolf
+ Vollprecht - Code for Thought
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht"
+- abstract: Slide set of the accepted rapid access micro talks at USRSE
+ 25.
+ accessed: 2026-04-09
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-04-09T23:30:44.373Z
+ author:
+ - family: Ruchti
+ given: Carol
+ - family: Ogundipe
+ given: Michael
+ - family: Ward
+ given: Brian
+ - family: Hillegas
+ given: Curt
+ - family: Mizrachi
+ given: Eli
+ - family: Brownell
+ given: Dave
+ - family: Tapera
+ given: Tinashe Michael
+ - family: Soules
+ given: Jeff
+ - family: Lackie
+ given: Paula
+ - family: Ruchti
+ given: Carol
+ - family: Ogundipe
+ given: Michael
+ - family: Ward
+ given: Brian
+ - family: Hillegas
+ given: Curt
+ - family: Mizrachi
+ given: Eli
+ - family: Brownell
+ given: Dave
+ - family: Tapera
+ given: Tinashe Michael
+ - family: Soules
+ given: Jeff
+ - family: Lackie
+ given: Paula
+ doi: 10.5281/zenodo.17297728
+ id: ruchtiUSRSE25Rapid2025
+ issued: 2025-10-08
+ title: USRSE 25 rapid access micro talks
+ type: manuscript
+ url: "https://zenodo.org/records/17297728"
+- abstract: "English Edition: how are real numbers e.g. 0.1 represented
+ on computers? What can go wrong with using their representation in
+ calculations? And does it matter? These and other questions are the
+ subject of this ByteSized episode with my guests Prof..."
+ accessed: 2026-04-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtByteSizedFunFloating2026
+ issued: 2026-03-31
+ language: en-US
+ title: "\\[EN\\] ByteSized: Fun with floating points - U Ruede, A Herten
+ and E di Napoli - Code for Thought"
+ title-short: \[EN\] ByteSized
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli"
+- abstract: "English Edition: how are real numbers e.g. 0.1 represented
+ on computers? What can go wrong with using their representation in
+ calculations? And does it matter? These and other questions are the
+ subject of this ByteSized episode with my guests Prof..."
+ accessed: 2026-04-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtByteSizedFunFloating2026a
+ issued: 2026-03-31
+ language: en-US
+ title: "\\[EN\\] ByteSized: Fun with floating points - U Ruede, A Herten
+ and E di Napoli - Code for Thought"
+ title-short: \[EN\] ByteSized
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli"
+- abstract: "English Edition (ByteSized): In this first episode of the
+ new ByteSized dRTP season, sponsored by the STEP-UP programme from
+ the EPSRC (UK) you’ll meet Richard Acton. Richard created a tool to
+ help you keep track of all the steps you should take t..."
+ accessed: 2026-03-16
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-04-13T15:23:08.156Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtByteSizedHowGet2026
+ issued: 2026-03-03
+ language: en-US
+ title: "\\[EN\\] ByteSized: How to get your (digital) ducks in a row -
+ with Richard Acton - Code for Thought"
+ title-short: \[EN\] ByteSized
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton"
+- abstract: "English Edition:\\ NextBrain is a next generation atlas
+ of the human brain. Juan Eugenio Iglesias Gonzales from
+ Massachusetts General in Boston, US, has been leading this project.
+ My colleague James Hughes (University College London) and I were..."
+ accessed: 2026-04-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtNextBrainExploringHuman2026
+ issued: 2026-03-17
+ language: en-US
+ title: "\\[EN\\] NextBrain: Exploring the human brain - Eugenio
+ Iglesias, James Hughes - Code for Thought"
+ title-short: \[EN\] NextBrain
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes"
+- abstract: "English Edition:\\ Meet Thomas White from DESY (German
+ Electron Synchrotron) who is the creator and maintainer of the tool
+ CrystFEL. The tool to help understand and analyse the structure of
+ materials such as crystals and proteins. Thomas and I ..."
+ accessed: 2026-03-16
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-04-13T15:23:08.155Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtRevealingStructureCrystals2026
+ issued: 2026-03-10
+ language: en-US
+ title: \[EN\] Revealing the structure of crystals and proteins with
+ CrystFEL - Thomas White - Code for Thought
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white"
+- abstract: "English Edition:\\ for this episode we’re going \"up
+ North\", to visit the Research Software Engineering team of the
+ University of Newcastle. The team has been hosting the UK RSE
+ Conference in 2022 and 2024 and here is a chance to meet at least
+ s..."
+ accessed: 2026-04-13
+ annote: |
+ Read_Status: Read\
+ Read_Status_Date: 2026-05-21T02:36:15.500Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: schmidtTeamPortraitResearch2026
+ issued: 2026-03-24
+ language: en-US
+ title: "\\[EN\\] Team Portrait: Research Software Engineering in
+ Newcastle - Code for Thought"
+ title-short: \[EN\] Team Portrait
+ type: song
+ url: "https://codeforthought.buzzsprout.com/1326658/episodes/18761138-en-team-portrait-research-software-engineering-in-newcastle"
+- abstract: "English Edition:\\ I want to come back to agile
+ development practices with my guest Dave Thomas, or Pragmatic Dave
+ as he is also known in the trade. Dave is one of the authors of the
+ manifesto for agile development - and we talk about what has ..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: WhatHappenedAgile2026
+ issued: 2026-06-16
+ language: en-US
+ title: \[EN\] What happened to agile development? - A review with Dave
+ Thomas - Code for Thought
+ title-short: \[EN\] What happened to agile development?
+ type: song
+ url: "https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas"
+- abstract: "English Edition: floppy disks, hard drives, CDs, DVDs, SSD
+ drives - no matter what you choose to store your data on -
+ ultimately they all decay. With my guests Callum McKean, Leontien
+ Talboom and Adrian Page-Mitchell, we’re going to talk about wha..."
+ accessed: 2026-06-16
+ annote: |
+ Read_Status: To Read\
+ Read_Status_Date: 2026-06-16T16:05:28.241Z
+ author:
+ - family: Schmidt
+ given: Peter
+ id: WhenBitsRot2026
+ issued: 2026-06-09
+ language: en-US
+ title: \[EN\] When Bits Rot - with C McKean, L Talboom, A
+ Page-Mitchell - Code for Thought
+ type: song
+ url: "https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell"
+---
+
diff --git a/_data/newsletter/usrse.bib b/_data/newsletter/usrse.bib
new file mode 100644
index 000000000..a14e31db6
--- /dev/null
+++ b/_data/newsletter/usrse.bib
@@ -0,0 +1,951 @@
+@article{armstrongCharacterizingSecurityCulture2026,
+ title = {Characterizing the Security Culture of the Research Software Engineering Community: {{An}} Empirical Study},
+ shorttitle = {Characterizing the Security Culture of the Research Software Engineering Community},
+ author = {Armstrong, Matthew and Carver, Jeffrey C. and Milewicz, Reed and Meinel, Michael and Felderer, Michael},
+ date = {2026-10},
+ journaltitle = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
+ volume = {183},
+ pages = {108571},
+ issn = {0167739X},
+ doi = {10.1016/j.future.2026.108571},
+ url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002050},
+ urldate = {2026-05-21},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@article{armstrongPreparingResearchSoftware2026,
+ title = {Preparing Research Software Engineers to Become Security Champions: {{Development}} and Evaluation of a Security Awareness Workshop},
+ shorttitle = {Preparing Research Software Engineers to Become Security Champions},
+ author = {Armstrong, Matthew and Carver, Jeffrey C. and Milewicz, Reed},
+ date = {2026-10},
+ journaltitle = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
+ volume = {183},
+ pages = {108572},
+ issn = {0167739X},
+ doi = {10.1016/j.future.2026.108572},
+ url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002062},
+ urldate = {2026-05-21},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@report{barkerResearchSoftwareEngineering2026,
+ title = {Research {{Software Engineering}} in the {{Age}} of {{Generative AI}}: {{Building}} a {{Community Vision}}},
+ shorttitle = {Research {{Software Engineering}} in the {{Age}} of {{Generative AI}}},
+ author = {Barker, Michelle and Katz, Daniel S. and Hartley, Kim and Ahern, Samantha and Chue Hong, Neil and Cosden, Ian and Daniels, Ryan and Druskat, Stephan and Dubey, Anshu and Elmatad, Yael and Geng, Cunliang and Gesing, Sandra and Haines, Robert and Hetherington, James and Hodges, Toby and Howison, James and Kopec-Harding, Kamilla and Littauer, Richard and Maimone, Christina and Mandava, Vani and Marwaha, Rohan and O'Brien, Elle and Price-Whelan, Adrian and Ram, Karthik and Shingleton, Joseph and Smith, Sue and TeBlunthuis, Nathan and Van der Walt, Anelda and Van Tuyl, Steve and family=Werkhoven, given=Ben, prefix=van, useprefix=true and Whitaker, Kirstie and Wilson, Greg and Wu, Sherry and Yehudi, Yo},
+ date = {2026-05-28},
+ institution = {Zenodo},
+ doi = {10.5281/zenodo.20320884},
+ url = {https://zenodo.org/records/20320884},
+ urldate = {2026-05-28},
+ abstract = {The Research Software Engineering in the Age of Generative AI: Building a Community Vision workshop, held in March in Edinburgh, UK, brought together participants to explore how Generative AI may reshape the research software ecosystem, and to help inform a broader community vision for the future of the field.~ Before the workshop, attendees contributed to a draft vision statement that workshop organisers used to identify areas of agreement and difference. A version of this, published as Research Software in an Age of AI-Assisted Development: Reflections from Edinburgh, is intended to provide principles that will guide the community during this time of rapid change. In the workshop, the participants also discussed emerging practices, identified opportunities and risks, and proposed a range of high-impact pilot activities to support the safe, reproducible, and effective use of AI in research software and workflows. The areas focused on included: Suggesting policies and narratives for research-performing institutions Developing a framework to discover, document and address costs, benefits, and risks Understanding future incentives around publishing, preserving and crediting software Verifying and validating research software Defining pathways for the evolution of the research software engineers (RSE) role Identifying and developing necessary training Developing a playbook for RSE managers and open-source software project leaders Making GenAI accessible to all Collaborating together across people, community, and disciplines, not just with AI Across these areas, participants identified 46 different activities, ranging from writing sprints and community-of-practice activities that could begin soon, to longer-term research studies to investigate how verification practices, collaboration patterns, and training needs are changing as AI tools become embedded in research workflows. These projects shared a common focus on community-maintained practices, actionable guidance, and sustained coordination.},
+ keywords = {community,generative AI,research software,research software engineering},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/9GNVA3UV/Barker et al. - 2026 - Research Software Engineering in the Age of Generative AI Building a Community Vision.pdf}
+}
+
+@online{besserHowGenerativeAI,
+ title = {How Generative {{AI}} Is Shaping Research ... | {{Open Research Europe}}},
+ author = {Besser, Stephanie and Jensen, Eric and Katz, Daniel},
+ url = {https://open-research-europe.ec.europa.eu/articles/6-56/v1},
+ urldate = {2026-04-08},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{bortVCBignameProgrammers2026,
+ title = {A {{VC}} and Some Big-Name Programmers Are Trying to Solve Open Source's Funding Problem, Permanently},
+ author = {Bort, Julie},
+ date = {2026-02-26T16:00:00+00:00},
+ url = {https://techcrunch.com/2026/02/26/a-vc-and-some-big-name-programmers-are-trying-to-solve-open-sources-funding-problem-permanently/},
+ urldate = {2026-04-08},
+ abstract = {A group of well-known open source programmers and a VC have launched the Open Source Endowment. They hope this new method will provide funding for good.},
+ langid = {american},
+ organization = {TechCrunch},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@audio{ByteSizedCreateYour2026,
+ title = {[{{EN}}] {{ByteSized}}: Create Your Web-Site with {{GitHub Pages}} - {{J Cohen}}, {{S Gibson}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-05-19},
+ url = {https://www.buzzsprout.com/1326658/episodes/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson},
+ urldate = {2026-05-21},
+ abstract = {English Edition:\ In this ByteSized episode \& online class we're talking about GitHub Pages and how it can help you to create a web-site for your research project (reasonably) quickly. With me are Sarah Gibson and Jeremy Cohen.\ I'd li...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/2EWWF4FT/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson.html}
+}
+
+@article{carverSustainingResearchSoftware2021,
+ title = {Sustaining {{Research Software}} via {{Research Software Engineers}} and {{Professional Associations}}},
+ author = {Carver, Jeffrey C. and Cosden, Ian A. and Hill, Chris and Gesing, Sandra and Katz, Daniel S.},
+ date = {2021-06},
+ journaltitle = {2021 IEEE/ACM International Workshop on Body of Knowledge for Software Sustainability (BoKSS)},
+ shortjournal = {2021 IEEEACM Int. Workshop Body Knowl. Softw. Sustain. BoKSS},
+ pages = {23--24},
+ doi = {10.1109/BoKSS52540.2021.00016},
+ url = {https://ieeexplore.ieee.org/document/9470770},
+ urldate = {2026-05-21},
+ abstract = {Research software is a class of software developed to support research. Today a wealth of such software is created daily in universities, government, and commercial research enterprises worldwide. The sustainability of this software faces particular challenges due, at least in part, to the type of people who develop it. These Research Software Engineers (RSEs) face challenges in developing and sustaining software that differ from those faced by the developers of traditional software. As a result, professional associations have begun to provide support, advocacy, and resources for RSEs. These benefits are critical to sustaining RSEs, especially in environments where their contributions are often undervalued and not rewarded. This paper focuses on how professional associations, such as the United States Research Software Engineer Association (US-RSE), can provide this support.},
+ keywords = {career paths,Conferences,Faces,Government,Knowledge engineering,people,research software,Software,software sustainability,Sustainable development},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/MBQI2WMD/Carver et al. - 2021 - Sustaining Research Software via Research Software Engineers and Professional Associations.pdf;/Users/tit420/Zotero/storage/PETA3B2D/9470770.html}
+}
+
+@video{casscommunityAITeamworkTooling2026,
+ entrysubtype = {video},
+ title = {{{AI}} Teamwork and Tooling for Research Software Engineers},
+ namea = {{CASS Community}},
+ nameatype = {collaborator},
+ date = {2026-03-04},
+ url = {https://www.youtube.com/watch?v=Xq93CVDCuds},
+ urldate = {2026-04-08},
+ abstract = {Presentations by Olivia Newton (University of Montana) and Andrew Schmeder (LBNL) on March 3 in the Consortium for the Advancement of Scientific Software (CASS; https://cass.community/) User/Developer Experience working group. The speakers discuss research software engineers, how they work in teams with AI tools, and what performance they can expect from AI t},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@article{chenAIThreateningScience2026,
+ title = {{{AI}} Is Threatening Science Jobs. {{Which}} Ones Are Most at Risk?},
+ author = {Chen, Edward},
+ date = {2026-02-20},
+ journaltitle = {Nature},
+ volume = {651},
+ number = {8104},
+ pages = {19--20},
+ publisher = {Nature Publishing Group},
+ issn = {1476-4687},
+ doi = {10.1038/d41586-026-00444-9},
+ url = {https://www.nature.com/articles/d41586-026-00444-9},
+ urldate = {2026-04-08},
+ abstract = {Data-analysis and modelling positions are already becoming obsolete, but hands-on experimentalists can breathe easy for now.},
+ langid = {english},
+ keywords = {Careers,Machine learning},
+ annotation = {Bandiera\_abtest: a\\
+Cg\_type: News\\
+Subject\_term: Machine learning, Careers\\
+Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/C2QM72QE/Chen - 2026 - AI is threatening science jobs. Which ones are most at risk.pdf}
+}
+
+@article{chugunovaWhoUsesAI2026,
+ title = {Who Uses {{AI}} in Research, and for What? {{Large-scale}} Survey Evidence from {{Germany}}},
+ shorttitle = {Who Uses {{AI}} in Research, and for What?},
+ author = {Chugunova, Marina and Harhoff, Dietmar and Hölzle, Katharina and Kaschub, Verena and Malagimani, Sonal and Morgalla, Ulrike and Rose, Robert},
+ date = {2026-03-01},
+ journaltitle = {Research Policy},
+ shortjournal = {Res. Policy},
+ volume = {55},
+ number = {2},
+ pages = {105381},
+ issn = {0048-7333},
+ doi = {10.1016/j.respol.2025.105381},
+ url = {https://www.sciencedirect.com/science/article/pii/S0048733325002100},
+ urldate = {2026-04-08},
+ abstract = {The integration of AI into scientific work holds significant potential to accelerate innovation. We surveyed researchers in two leading German research organizations to examine AI adoption, barriers, and perceived impact on research. Researchers are widely using AI tools – often for primary and creative tasks – and many expect the technology to be transformative for research. Effective use appears linked to both hands-on experience and engagement with learning resources. A persistent gender gap in AI use is closely associated with differences in familiarity, suggesting a potential focus for organizational efforts. Legal uncertainty and privacy concerns also emerge as major barriers, with researchers calling for clear, high-level regulatory guidance. Overall, our findings suggest directions where institutional actions might be explored to promote more equitable and effective AI adoption.},
+ keywords = {AI,Innovation,Research,Survey evidence,Technology adoption},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/CZAR663R/Chugunova et al. - 2026 - Who uses AI in research, and for what Large-scale survey evidence from Germany.pdf;/Users/tit420/Zotero/storage/F8U86Q9C/S0048733325002100.html}
+}
+
+@online{claburnAIStillDoesnt,
+ title = {{{AI}} Still Doesn't Work Very Well in Business, Reckoning Soon},
+ author = {Claburn, Thomas},
+ url = {https://www.theregister.com/2026/03/17/ai_businesses_faking_it_reckoning_coming_codestrap/},
+ urldate = {2026-04-08},
+ abstract = {interview: Codestrap founders say we need to dial down the hype and sort through the mess},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{claburnGitHubWeGoing,
+ title = {{{GitHub}}: {{We}} Going to Train on Your Data after All},
+ shorttitle = {{{GitHub}}},
+ author = {Claburn, Thomas},
+ url = {https://www.theregister.com/2026/03/26/github_ai_training_policy_changes/},
+ urldate = {2026-04-08},
+ abstract = {: As of April 24 you'll be feeding the Octocat unless you opt out},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@video{clusterraBioChemreadySlurmCluster2026,
+ entrysubtype = {video},
+ title = {{{BioChem-ready}} {{Slurm Cluster}} in Minutes — {{Clusterra Walkthrough}}},
+ namea = {{Clusterra}},
+ nameatype = {collaborator},
+ date = {2026-04-25},
+ url = {https://www.youtube.com/watch?v=a1-GGm3tAbI},
+ urldate = {2026-06-29},
+ abstract = {A 1:49 walkthrough of the Clusterra console: from an empty AWS account to a running Slurm cluster, a submitted job, and a live JupyterLab notebook — all in your own AWS, same day.},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:29:59.361Z}
+}
+
+@audio{ComputingNotYou2026,
+ title = {[{{EN}}] {{Computing}}, but Not as You Know It: {{Field Programmable Gate Arrays}} ({{FPGA}}) - with {{Michael McLeod}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Computing}}, but Not as You Know It},
+ author = {Schmidt, Peter},
+ date = {2026-05-05},
+ url = {https://www.buzzsprout.com/1326658/episodes/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-mcleod},
+ urldate = {2026-05-21},
+ abstract = {English Edition: In a follow up about "unusual" computers I want to focus on field programmable gate arrays - FPGAs. With my guest and former colleague at UCL, Michael McLeod, we talk about what they are, where they are used and what's so special ...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/HFYACMW9/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-m.html}
+}
+
+@article{cosdenDesigningImplementingComprehensive2026,
+ title = {Designing and Implementing a Comprehensive Research Software Engineer Career Ladder: {{A}} Case Study from {{Princeton University}}},
+ shorttitle = {Designing and Implementing a Comprehensive Research Software Engineer Career Ladder},
+ author = {Cosden, Ian A. and Holtz, Elizabeth and Bretheim, Joel U.},
+ date = {2026-10},
+ journaltitle = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
+ volume = {183},
+ pages = {108574},
+ issn = {0167739X},
+ doi = {10.1016/j.future.2026.108574},
+ url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002086},
+ urldate = {2026-05-21},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@online{CrankGPTLocalHumanpowered,
+ title = {{{CrankGPT}} — {{Local Human-powered AI}}},
+ author = {Squeez Labs},
+ url = {https://crankgpt.com/},
+ urldate = {2026-06-16},
+ abstract = {A human-powered, fully local, fully private AI solution.},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/QGJ3I4WD/crankgpt.com.html}
+}
+
+@article{crouchSoftwareSustainabilityInstitute2013,
+ title = {The {{Software Sustainability Institute}}: {{Changing Research Software Attitudes}} and {{Practices}}},
+ shorttitle = {The {{Software Sustainability Institute}}},
+ author = {Crouch, Stephen and Hong, Neil Chue and Hettrick, Simon and Jackson, Mike and Pawlik, Aleksandra and Sufi, Shoaib and Carr, Les and De Roure, David and Goble, Carole and Parsons, Mark},
+ date = {2013-11},
+ journaltitle = {Computing in Science \& Engineering},
+ shortjournal = {Comput. Sci. Eng.},
+ volume = {15},
+ number = {6},
+ pages = {74--80},
+ issn = {1558-366X},
+ doi = {10.1109/MCSE.2013.133},
+ url = {https://ieeexplore.ieee.org/document/6731384},
+ urldate = {2026-05-21},
+ abstract = {To effect change, the Software Sustainability Institute works with researchers, developers, funders, and infrastructure providers to identify and address key issues with research software.},
+ keywords = {domain engineering,Domain engineering,maintainability,Programming,reliability,scientific computing,Scientific computing,Software development,software engineering,Software engineering,Software reliability,Training},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/ALBPHA5I/6731384.html}
+}
+
+@article{dicosmoStopTreatingCode2025,
+ title = {Stop Treating Code like an Afterthought: Record, Share and Value It},
+ shorttitle = {Stop Treating Code like an Afterthought},
+ author = {Di Cosmo, Roberto and Granger, Sabrina and Hinsen, Konrad and Jullien, Nicolas and Le Berre, Daniel and Louvet, Violaine and Maumet, Camille and Maurice, Clémentine and Monat, Raphaël and Rougier, Nicolas P.},
+ date = {2025-10},
+ journaltitle = {Nature},
+ volume = {646},
+ number = {8084},
+ pages = {284--286},
+ publisher = {Nature Publishing Group},
+ issn = {1476-4687},
+ doi = {10.1038/d41586-025-03196-0},
+ url = {https://www.nature.com/articles/d41586-025-03196-0},
+ urldate = {2025-11-07},
+ abstract = {Scientists, research institutions, funders, libraries and publishers must all improve software practices.},
+ langid = {english},
+ keywords = {Computer science,Research management,Scientific community,Software},
+ annotation = {Bandiera\_abtest: a\\
+Cg\_type: Comment\\
+Subject\_term: Computer science, Software, Scientific community, Research management\\
+Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.784Z},
+ file = {/Users/tit420/Zotero/storage/ZDISSPC7/d41586-025-03196-0.html}
+}
+
+@audio{DoesSpecDrivenDevelopment2026,
+ title = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile? {{With Graham Lee}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile?},
+ author = {Schmidt, Peter},
+ date = {2026-06-02},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee},
+ urldate = {2026-06-16},
+ abstract = {English Edition: Will spec-driven development replace agile processes? My guest Graham Lee\ (https://chironcodex.com/ ) and I discuss if there is still a place for agile software engineering in a world of AI assisted coding.Links:https://mart...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/QWCZ298A/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee.html}
+}
+
+@online{DozensAmericasLargest2026,
+ title = {Dozens of {{America}}'s Largest Companies Have No Simple Way to Report Security Flaws},
+ author = {Whittaker, Zach},
+ date = {2026-06-19T12:00:34},
+ url = {https://this.weekinsecurity.com/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws/},
+ urldate = {2026-06-29},
+ abstract = {New analysis shows that around one-third of America's Fortune 100 companies do not have a vulnerability disclosure policy, bug bounty, or a dedicated email address for reporting security flaws.},
+ langid = {english},
+ organization = {\textasciitilde this week in security\textasciitilde},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:31:33.542Z},
+ file = {/Users/tit420/Zotero/storage/X3RV4UQU/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws.html}
+}
+
+@report{druskatResearchSoftwareEngineers2026,
+ title = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}: {{Same Value}}, {{Changing Practice}}},
+ shorttitle = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}},
+ author = {Druskat, Stephan and Barker, Michelle and Cosden, Ian and Geng, Cunliang and Haines, Robert and Katz, Daniel S. and Shingleton, Joseph and family=Werkhoven, given=Ben, prefix=van, useprefix=true},
+ date = {2026-05-28},
+ institution = {Zenodo},
+ doi = {10.5281/zenodo.20320179},
+ url = {https://zenodo.org/records/20320179},
+ urldate = {2026-05-28},
+ abstract = {Research software and its creators have long played a critical role in the advancement of research worldwide. This role is changing in the age of “generative AI” (GenAI), but both the software and the people remain of key importance. Understanding these changes is essential in enabling Research Software Engineers (RSEs) to continue contributing the same high value to the research process and its outputs.~ Before GenAI, the RSE movement had learned to clearly articulate the value proposition of embedding expert software engineering in research to its stakeholders. This blog post highlights how RSEs use GenAI to increase their capacity in both software engineering and research, and visualize this evolution. While GenAI is changing - perhaps considerably - how RSEs work in practice, their value and the value of their work for research remains steady and likely to increase.},
+ langid = {english},
+ keywords = {GenAI,Research,Research software,Research software engineers},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/UY727H52/Druskat et al. - 2026 - Research Software Engineers in the Age of GenAI Same Value, Changing Practice.pdf}
+}
+
+@online{ernstNatureTechnicalDebt2026,
+ title = {The {{Nature}} of {{Technical Debt}} in {{Research Software}}},
+ author = {Ernst, Neil A. and Awon, Ahmed Musa and Hingmire, Swapnil and Li, Ze Shi},
+ date = {2026-03-20},
+ eprint = {2603.20415},
+ eprinttype = {arXiv},
+ eprintclass = {cs},
+ doi = {10.48550/arXiv.2603.20415},
+ url = {http://arxiv.org/abs/2603.20415},
+ urldate = {2026-04-08},
+ abstract = {Research software (also called scientific software) is essential for advancing scientific endeavours. Research software encapsulates complex algorithms and domain-specific knowledge and is a fundamental component of all science. A pervasive challenge in developing research software is technical debt, which can adversely affect reliability, maintainability, and scientific validity. Research software often relies on the initiative of the scientific community for maintenance, requiring diverse expertise in both scientific and software engineering domains. The extent and nature of technical debt in research software are little studied, in particular, what forms it takes, and what the science teams developing this software think about their technical debt. In this paper we describe our multi-method study examining technical debt in research software. We begin by examining instances of self-reported technical debt in research code, examining 28k code comments across nine research software projects. Then, building on our findings, we interview research software engineers and scientists about how this technical debt manifests itself in their experience, and what costs it has for research software and research outputs more generally. We identify nine types of self-admitted technical debt unique to research software, and four themes impacting this technical debt.},
+ pubstate = {prepublished},
+ keywords = {Computer Science - Software Engineering},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/WQDC3HHH/Ernst et al. - 2026 - The Nature of Technical Debt in Research Software.pdf}
+}
+
+@online{forstonGrandChallengesConvergence2026,
+ title = {Grand {{Challenges}} for the {{Convergence}} of {{Computational}} and {{Citizen Science Research}} - {{CCC}}},
+ author = {Forston, Lucy and Shanley, Lea and Berger-Wolf, Tanya and Crowston, Kevin and Jackson, Corey and Savage, Saiph and Griffin, Haley},
+ date = {2026},
+ url = {https://cra.org/ccc/events/grand-challenges-for-the-convergence-of-computational-and-citizen-science-research/},
+ urldate = {2026-03-13},
+ abstract = {CCC is hosting a two-day visioning workshop to explore how humans and machines may team up to solve some of the most pressing scientific problems through citizen science, crowdsourcing, and community-engaged science.},
+ langid = {american},
+ pubstate = {prepublished},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-13T15:23:11.431Z},
+ file = {/Users/tit420/Zotero/storage/HM6TRMN3/Grand Challenges for the Convergence of Computational and Citizen Science Research.pdf;/Users/tit420/Zotero/storage/ML29TFTD/grand-challenges-for-the-convergence-of-computational-and-citizen-science-research.html}
+}
+
+@online{gesingFindingComputingData2025,
+ title = {Finding {{Computing}} and {{Data Infrastructure}} to {{Get Started}} in {{Data-Intensive Research}}},
+ author = {Gesing, Sandra and Stone, Sarah and Washington, Talitha},
+ date = {2025-11-03},
+ url = {https://academicdatascience.org/resources/community-blog/get-started-in-data-intensive-research/},
+ urldate = {2025-11-07},
+ abstract = {Helpful questions and guide for finding the right resources for your large-scale data or advanced computing project.},
+ langid = {american},
+ organization = {Academic Data Science Alliance},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/WSHTFF98/get-started-in-data-intensive-research.html}
+}
+
+@article{hasselbringTechnologyResearchSoftware2026,
+ title = {Technology {{Research Software}}: {{An Often Overlooked Category}} of {{Research Software}}},
+ shorttitle = {Technology {{Research Software}}},
+ author = {Hasselbring, Wilhelm and Katz, Daniel S. and family=Nieuwpoort, given=Rob, prefix=van, useprefix=true},
+ date = {2026-01},
+ journaltitle = {Computing in Science \& Engineering},
+ shortjournal = {Comput. Sci. Eng.},
+ volume = {28},
+ number = {1},
+ pages = {94--99},
+ issn = {1558-366X},
+ doi = {10.1109/MCSE.2026.3662117},
+ url = {https://ieeexplore.ieee.org/document/11482008},
+ urldate = {2026-05-28},
+ abstract = {Research software has been categorized for various goals. One fundamental dimension of such categorizations is the role that the software plays in the research process. Recently, a new role category has emerged: technology research software, which covers research software developed in technology research. Until now, this category of technology research software has often been overlooked and neglected within the research software engineering community. In this article, we explain technology research software and its primary subroles. Technology readiness levels are an established method of estimating the maturity of technologies, including software systems. For technology research software, these readiness levels define secondary subroles. To illustrate the concept of technology research software and to make it more tangible, we present examples of research software that, depending on its specific use within or outside of research, take on the role of technology research software as well as that of another research software category.},
+ keywords = {Research and development,Software development management,Technology planning},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/6BSWQ8MR/Hasselbring et al. - 2026 - Technology Research Software An Often Overlooked Category of Research Software.pdf;/Users/tit420/Zotero/storage/2UK2DMNQ/11482008.html}
+}
+
+@article{kaiserProbabilisticComputingPbits2021,
+ title = {Probabilistic Computing with P-Bits},
+ author = {Kaiser, Jan and Datta, Supriyo},
+ date = {2021-10-11},
+ journaltitle = {Applied Physics Letters},
+ shortjournal = {Appl. Phys. Lett.},
+ volume = {119},
+ number = {15},
+ eprint = {2108.09836},
+ eprinttype = {arXiv},
+ eprintclass = {cs},
+ pages = {150503},
+ issn = {0003-6951, 1077-3118},
+ doi = {10.1063/5.0067927},
+ url = {http://arxiv.org/abs/2108.09836},
+ urldate = {2025-11-07},
+ abstract = {Digital computers store information in the form of bits that can take on one of two values 0 and 1, while quantum computers are based on qubits that are described by a complex wavefunction, whose squared magnitude gives the probability of measuring either 0 or 1. Here, we make the case for a probabilistic computer based on p-bits, which take on values 0 and 1 with controlled probabilities and can be implemented with specialized compact energy-efficient hardware. We propose a generic architecture for such p-computers and emulate systems with thousands of p-bits to show that they can significantly accelerate randomized algorithms used in a wide variety of applications including but not limited to Bayesian networks, optimization, Ising models, and quantum Monte Carlo.},
+ keywords = {Computer Science - Emerging Technologies,Condensed Matter - Disordered Systems and Neural Networks,Quantum Physics},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/CS2DGY3W/Kaiser and Datta - 2021 - Probabilistic computing with p-bits.pdf;/Users/tit420/Zotero/storage/RINJGA8Z/2108.html}
+}
+
+@article{kamaliCommunitySoftwareFacility,
+ title = {Community {{Software Facility Discovery Workshop Report}}: {{Scientific}} Software Best Practices, Tools, and Culture},
+ shorttitle = {Community {{Software Facility Discovery Workshop Report}}},
+ author = {Kamali, Author: Soudeh and Colegrove, Author: Dominique and Voelz, Author: Sheri and Fitzgerald, Author: Katelyn},
+ url = {https://opensky.ucar.edu/islandora/object/technotes%3A45415},
+ urldate = {2026-05-28},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/UDUNTTC9/Kamali et al. - Community Software Facility Discovery Workshop Report Scientific software best practices, tools, an.pdf}
+}
+
+@report{katzResearchSoftwareAge2026,
+ title = {Research {{Software}} in an {{Age}} of {{AI-Assisted Development}}: {{Reflections}} from {{Edinburgh}}},
+ shorttitle = {Research {{Software}} in an {{Age}} of {{AI-Assisted Development}}},
+ author = {Katz, Daniel S. and Ahern, Samantha and Barker, Michelle and Cosden, Ian and Druskat, Stephen and Dubey, Anshu and Elmatad, Yael and Geng, Cunliang and Gesing, Sandra and Goble, Carole and Haines, Robert and Hartley, Kim and Hetherington, James and Hodges, Toby and Littauer, Richard and Maimone, Christina and Mandava, Vani and O'Brien, Elle and Price-Whelan, Adrian and Ram, Karthik and Shingleton, Joseph and Smith, Sue and TeBlunthius, Nathan and Van der Walt, Anelda and family=Werkhove, given=Ben, prefix=van, useprefix=true and Whitaker, Kirstie and Wu, Sherry},
+ date = {2026-05-27},
+ institution = {Zenodo},
+ doi = {10.5281/zenodo.20321134},
+ url = {https://zenodo.org/records/20321134},
+ urldate = {2026-05-28},
+ abstract = {Important: This document began as a draft vision statement prepared in advance of the “Research Software Engineering in the Age of Generative AI” workshop, March 2026. It was intended to lead to discussion in the document before and discussion in-person at the workshop, including disagreement, and refinement. The current version of the document is a snapshot of that draft vision statement and some of the discussion. It captures a sense of the identified principles, benefits, challenges, and open questions, rather than having a single point of view that represents all of the workshop attendees and contributors. Not all authors necessarily agree with all the points in the document. A note on terminology: We use AI-assisted software development throughout this document to refer to tools and practices often described as Generative AI, GenAI, LLM-enabled development, or AI-assisted coding. We chose this term because it focuses on the activity we care about here, namely the production, verification, documentation, and maintenance of research software, rather than on a particular technology label or marketing category. Research software, the source code, scripts, computational workflows, and infrastructure that power modern research, have never been more central to human discovery. And the scholarly community (funders, publishers, societies, etc.) increasingly recognizes this, though there is still a long way to go before such recognition is widespread or leads to systemic change. At the same time, in the last few years, the rise of AI-assisted tools, i.e., those that can generate code and documentation by using large language and multimodal trained models, and act in semi-autonomous “agentic modes,” has caused significant disruption in software creation and society at large. These tools raise legitimate questions about training data provenance, licensing, quality, security, attribution, environmental cost, and accountability that are hard to ignore. Yet the conversation around AI-assisted tools too often seems to oscillate between hype and dystopian predictions. Neither of these extremes serve research well. This document also starts from the assumption that these tools are and will continue to be used, regardless of the concerns raised above, and aims to guide further usage within this context. This document outlines some ideas about how research software can and should be produced in the era of AI-assisted research tools by Research Software Engineers, computational researchers, and domain experts writing their own code. It focuses on the software production function: building and maintaining software that meaningfully advances research, but also includes the people involved. Workshop participants discussed both, including the role of RSEs and how it will change, such as leveraging the ADSA/USE-RSE-led Position Statement on Generative AI in the RSE Workplace and related work in this space. We believe that developing a shared vision of the future of research software is urgent: AI tools act as an amplifier of existing practices at every level: individual coding habits, institutional incentives, and the commercial priorities of the companies building these tools – accelerating whatever patterns they encounter, both good and bad. Applied without thought, AI-assisted tools can proliferate bugs, embed and reinforce biases, and generate plausible-looking results faster than our existing systems of peer review and verification can check and absorb them. Applied with care and discipline, it has the potential to expand access to computational methods from those with software development skills to those without them, at least for those who can afford it, and allow all researchers to focus on the work that most requires human skill and judgment.},
+ keywords = {generative AI,research software,research software engineering},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/MABEB35L/Katz et al. - 2026 - Research Software in an Age of AI-Assisted Development Reflections from Edinburgh.pdf}
+}
+
+@online{KindofBriefShared00:00:00+0000,
+ title = {A Kind-of Brief Shared Early History of {{US-RSE}}},
+ author = {Sochat, Vanessa and Katz, Daniel S. and Cosden, Ian A. and Maimone, Christina and Ferenbaugh, Charles and Gesing, Sandra and Carver, Jeffrey C. and Hill, Chris and Brewer, Nicole and Vaillancourt, Peter and Carroll, Mark and Elmer, Peter},
+ year = {00:00:00 +0000},
+ url = {https://us-rse.org/2022-02-06-a-brief-history-of-usrse/},
+ urldate = {2026-05-21},
+ abstract = {United States Research Software Engineer Association},
+ langid = {english},
+ organization = {US-RSE},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/DS3WJMXT/2022-02-06-a-brief-history-of-usrse.html}
+}
+
+@online{LeidenDeclarationArtificial2026,
+ title = {Leiden {{Declaration}} on {{Artificial Intelligence}} and {{Mathematics}}},
+ author = {{International Mathematical Union}},
+ date = {2026-08-05},
+ url = {https://leidendeclaration.ai/},
+ urldate = {2026-08-06},
+ abstract = {This declaration calls for action to address the challenges posed by the use of artificial intelligence within mathematics research.},
+ langid = {english},
+ organization = {Leiden Declaration on Artificial Intelligence and Mathematics},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-08-06T02:57:47.352Z},
+ file = {/Users/tit420/Zotero/storage/8SY8H9LJ/leidendeclaration.ai.html}
+}
+
+@online{macdonaldSTAMPEDPrinciplesReproducible2026,
+ title = {{{STAMPED}} Principles for Reproducible Research Objects},
+ author = {Macdonald, Austin and Baker, Cody and To, Isaac and Halchenko, Yaroslav O},
+ date = {2026-05-26},
+ number = {f3h82\_v1},
+ url = {https://osf.io/preprints/metaarxiv/f3h82_v1/},
+ urldate = {2026-06-15},
+ abstract = {Scientific claims increasingly rely upon the interplay of code, data, and computational environments. Yet the record of how they are used together is often incomplete, scattered, or lost. This undermines rigor, reproducibility, reusability, and efficiency. Previous approaches have improved the governance of digital objects but do not specify how research objects ought to be structured and managed so they can be re-executed and extended. The community is missing a shared vocabulary for this operational layer. Building on recurrent practices and convergent patterns across disciplines, we formalize seven principles: Self-containment, Tracking, Actionability, Modularity, Portability, Ephemerality, and Distributability (STAMPED). Together they give researchers guidelines for building and assessing research objects that others can trust, rerun, and build upon. We frame each principle as a spectrum so that adoption is incremental and starts from existing practice. We support each principle with normative requirements, an interactive checklist, and a map of enabling tools. As conventions mature, tooling improves, and AI agents become increasingly involved in research workflows, the goals of rigor, reproducibility, reusability, and efficiency are becoming more attainable. STAMPED gives researchers, collaborators, reviewers, and agents a common language, concrete goals, and an aligned direction for making computational research more durable. https://github.com/stamped-principles/stamped-paper/},
+ pubstate = {prepublished},
+ keywords = {open science,provenance,reproducibility,research objects},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.126Z},
+ file = {/Users/tit420/Zotero/storage/TJ2BGX9N/Macdonald et al. - 2026 - STAMPED principles for reproducible research objects.pdf}
+}
+
+@audio{ManagingPackagesPixi2026,
+ title = {[{{EN}}] {{Managing Packages}} with {{Pixi}} - {{Raniere}} de {{Silva}} and {{Wolf Vollprecht}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-05-12},
+ url = {https://www.buzzsprout.com/1326658/episodes/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht},
+ urldate = {2026-05-21},
+ abstract = {English Edition:\ there is a (relatively) new kid on the block - of open source package managers. It's called Pixi: and in this episode I talk to Raniere de Silva (GESIS) and Wolf Vollprecht (Prefix - the company behind Pixi), what the tool br...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/8C38H95J/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht.html}
+}
+
+@online{ManagingResearchSoftware,
+ title = {Managing {{Research Software Projects}}},
+ author = {Wilson, Greg},
+ url = {https://third-bit.com/mrsp/},
+ urldate = {2026-05-28},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
+ file = {/Users/tit420/Zotero/storage/GKTHZ5R8/mrsp.html}
+}
+
+@article{martinaEmpiricalEvaluationLLMs2026,
+ title = {Empirical Evaluation of {{LLMs}} Capabilities for Data Pipeline Generation on {{Databricks}} Platform},
+ author = {Martina, Tobia and Saad, Motaz and Rucco, Chiara and Longo, Antonella},
+ date = {2026-10},
+ journaltitle = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
+ volume = {183},
+ pages = {108587},
+ issn = {0167739X},
+ doi = {10.1016/j.future.2026.108587},
+ url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002219},
+ urldate = {2026-05-21},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@article{mcmahonPhysicsOpticalComputing2023,
+ title = {The Physics of Optical Computing},
+ author = {McMahon, Peter L.},
+ date = {2023-10-09},
+ journaltitle = {Nature Reviews Physics},
+ shortjournal = {Nat. Rev. Phys.},
+ volume = {5},
+ number = {12},
+ eprint = {2308.00088},
+ eprinttype = {arXiv},
+ eprintclass = {physics},
+ pages = {717--734},
+ issn = {2522-5820},
+ doi = {10.1038/s42254-023-00645-5},
+ url = {http://arxiv.org/abs/2308.00088},
+ urldate = {2025-11-07},
+ abstract = {There has been a resurgence of interest in optical computing over the past decade, both in academia and in industry, with much of the excitement centered around special-purpose optical computers for neural-network processing. Optical computing has been a topic of periodic study for over 50 years, including for neural networks three decades ago, and a wide variety of optical-computing schemes and architectures have been proposed. In this paper we provide a systematic explanation of why and how optics might be able to give speed or energy-efficiency benefits over electronics for computing, enumerating 11 features of optics that can be harnessed when designing an optical computer. One often-mentioned motivation for optical computing -- that the speed of light \$c\$ is fast -- is not a key differentiating physical property of optics for computing; understanding where an advantage could come from is more subtle. We discuss how gaining an advantage over state-of-the-art electronic processors will likely only be achievable by careful design that harnesses more than one of the 11 features, while avoiding a number of pitfalls that we describe.},
+ keywords = {Computer Science - Emerging Technologies,Computer Science - Neural and Evolutionary Computing,Physics - Applied Physics,Physics - Optics,Quantum Physics},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/WMTKAFHK/McMahon - 2023 - The physics of optical computing.pdf;/Users/tit420/Zotero/storage/DXJK8RWF/2308.html}
+}
+
+@book{millerIntroductionSoftwareSecurity,
+ title = {Introduction to {{Software Security}}},
+ author = {Miller, Barton P. and Heymann, Elisa R.},
+ publisher = {Independently published},
+ abstract = {Writing code that is resistant to being hacked is a challenging task. This book takes you through the entire process in easy-to-learn units, from the principles that underlie secure code, to the design, coding, testing, and evaluation of the code.You can use this book from start to finish as a complete curriculum on software security so it can form the basis of an introductory course.You can also use the book as a tutorial to learn about specific topics, like buffer overflows, injections attacks, or web security. Or, to learn how to use tools that will help you make your code more secure.However you go through this book, it will be a great learning aid and, in later times, a reference book that you can pick up whenever you need to a refresher or to learn a new topic.},
+ isbn = {9798195700508},
+ langid = {english},
+ pagetotal = {390},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@article{mineaultGoodResearchCode,
+ title = {Good {{Research Code}} Handbook},
+ author = {Mineault, Patrick},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/VN9MWNVD/Mineault - Good Research Code handbook.pdf}
+}
+
+@online{MingKwaiPrototypeOrigin,
+ title = {{{MingKwai}} Prototype, the ‘Origin of {{Chinese}} Computing,’ Finds a Home at {{Stanford}}},
+ url = {https://news.stanford.edu/stories/2025/05/mingkwai-chinese-typewriter-prototype-stanford-libraries},
+ urldate = {2025-11-07},
+ abstract = {Lost for more than half a century, the rare Chinese typewriter whose name means “clear and fast” was discovered in a New York basement and entrusted to Stanford Libraries.},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/FUNW4YLX/mingkwai-chinese-typewriter-prototype-stanford-libraries.html}
+}
+
+@online{nesbittGuidedMeditationDevelopers2026,
+ title = {Guided {{Meditation}} for {{Developers}}},
+ author = {Nesbitt, Andrew},
+ date = {2026-03-15T10:00:00+00:00},
+ url = {https://nesbitt.io/2026/03/15/guided-meditation-for-developers.html},
+ urldate = {2026-04-13},
+ abstract = {A practice for finding peace in your dependency tree.},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{NotsobriefHistoryResearch,
+ title = {A Not-so-Brief History of {{Research Software Engineers}} | {{Software Sustainability Institute}}},
+ author = {Hettrick, Simon},
+ url = {https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0},
+ urldate = {2026-05-21},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
+ file = {/Users/tit420/Zotero/storage/QJB9WWQZ/not-so-brief-history-research-software-engineers-0.html}
+}
+
+@online{openaiOpenAIAcquireAstral2026,
+ title = {{{OpenAI}} to Acquire {{Astral}}},
+ author = {OpenAI},
+ date = {2026-04-08},
+ url = {https://openai.com/index/openai-to-acquire-astral/},
+ urldate = {2026-04-08},
+ abstract = {Accelerates Codex growth to power the next generation of Python developer tools},
+ langid = {american},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@article{PhysicsNeedsResearch2025,
+ title = {Physics Needs Research Software Engineers},
+ date = {2025-07},
+ journaltitle = {Nature Reviews Physics},
+ shortjournal = {Nat. Rev. Phys.},
+ volume = {7},
+ number = {7},
+ pages = {349--349},
+ publisher = {Nature Publishing Group},
+ issn = {2522-5820},
+ doi = {10.1038/s42254-025-00852-2},
+ url = {https://www.nature.com/articles/s42254-025-00852-2},
+ urldate = {2025-11-07},
+ abstract = {Calls to recognize research software engineers are not new — but such professionals are needed now more than ever.},
+ langid = {english},
+ keywords = {Computational science},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/BLBNPG3S/2025 - Physics needs research software engineers.pdf}
+}
+
+@article{posadaOakRidgeComputing2026,
+ title = {Oak {{Ridge Computing Academy}}: {{An HPC}} Cluster Deployment and Management Pilot},
+ shorttitle = {Oak {{Ridge Computing Academy}}},
+ author = {Posada, Edwin F. and Holmen, John K. and Rentschler, Asa},
+ date = {2026-09},
+ journaltitle = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
+ volume = {182},
+ pages = {108513},
+ issn = {0167739X},
+ doi = {10.1016/j.future.2026.108513},
+ url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26001470},
+ urldate = {2026-05-21},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z}
+}
+
+@book{ramanathanIntroductionNeuromorphicComputing2025,
+ title = {Introduction to {{Neuromorphic Computing}}},
+ author = {Ramanathan, Shriram and Sengupta, Abhronil},
+ date = {2025},
+ publisher = {Cambridge University Press},
+ location = {Cambridge},
+ url = {https://www.cambridge.org/core/books/introduction-to-neuromorphic-computing/853942021D89F82AED182F9021E7E0F5},
+ urldate = {2025-11-07},
+ abstract = {Artificial intelligence is transforming industries and society, but its high energy demands challenge global sustainability goals. Biological intelligence, in contrast, offers both good performance and exceptional energy efficiency. Neuromorphic computing, a growing field inspired by the structure and function of the brain, aims to create energy-efficient algorithms and hardware by integrating insights from biology, physics, computer science, and electrical engineering. This concise and accessible book delves into the principles, mechanisms, and properties of neuromorphic systems. It opens with a primer on biological intelligence, describing learning mechanisms in both simple and complex organisms, then turns to the application of these principles and mechanisms in the development of artificial synapses and neurons, circuits, and architectures. The text also delves into neuromorphic algorithm design, and the unique challenges faced by algorithmic researchers working in this area. The book concludes with a selection of practice problems, with solutions available to instructors online.},
+ isbn = {978-1-009-56434-2},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/JCZQ8GXY/853942021D89F82AED182F9021E7E0F5.html}
+}
+
+@online{RealScorelineReveals,
+ title = {The {{Real Scoreline}} Reveals Nations Facing Climate Penalties - {{University}} of {{Reading}}},
+ author = {The University of Reading},
+ url = {https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties},
+ urldate = {2026-06-16},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/926BIU3J/The-Real-Scoreline-reveals-nations-facing-climate-penalties.html}
+}
+
+@unpublished{ruchtiUSRSE25Rapid2025,
+ title = {{{USRSE}} 25 Rapid Access Micro Talks},
+ author = {Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula and Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula},
+ date = {2025-10-08},
+ doi = {10.5281/zenodo.17297728},
+ url = {https://zenodo.org/records/17297728},
+ urldate = {2026-04-09},
+ abstract = {Slide set of the accepted rapid access micro talks at USRSE 25.},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-09T23:30:44.373Z},
+ file = {/Users/tit420/Zotero/storage/G5VLTKTU/Ruchti et al. - 2025 - USRSE 25 rapid access micro talks.pdf}
+}
+
+@online{saulGreatExpectationsUnifying2025,
+ title = {Great Expectations: {{Unifying Statistical Theory}} and {{Programming}}},
+ shorttitle = {Great Expectations},
+ author = {Saul, Bradley},
+ date = {2025-10-10},
+ eprint = {2510.09853},
+ eprinttype = {arXiv},
+ eprintclass = {stat},
+ doi = {10.48550/arXiv.2510.09853},
+ url = {http://arxiv.org/abs/2510.09853},
+ urldate = {2025-11-07},
+ abstract = {Beginning in the 1970s, statistician-cum-logician Per Martin-L\textbackslash "of wrote a series of papers developing what became Martin-L\textbackslash "of type theory, realizing a system where the distinction between mathematics and programming disappears. Inspired by this vision, this paper introduces dependent type theory (of which Martin-L\textbackslash "of type theory is an example) to a statistical audience. Examples from statistics and probability theory demonstrate how dependent type theory and an algebraic perspective can unify the theoretical and computational concerns of statistics, ensuring rigorous, machine-checked proofs and executable software.},
+ pubstate = {prepublished},
+ keywords = {Statistics - Computation},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/NE7I7ZIL/Saul - 2025 - Great expectations Unifying Statistical Theory and Programming.pdf;/Users/tit420/Zotero/storage/G87HXPJD/2510.html}
+}
+
+@audio{schmidtByteSizedFunFloating2026,
+ title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-31},
+ url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
+ urldate = {2026-04-13},
+ abstract = {English Edition: how are real numbers e.g. 0.1 represented on computers? What can go wrong with using their representation in calculations? And does it matter? These and other questions are the subject of this ByteSized episode with my guests Prof...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/PTLJK4KV/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli.html}
+}
+
+@audio{schmidtByteSizedFunFloating2026a,
+ title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-31},
+ url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
+ urldate = {2026-04-13},
+ abstract = {English Edition: how are real numbers e.g. 0.1 represented on computers? What can go wrong with using their representation in calculations? And does it matter? These and other questions are the subject of this ByteSized episode with my guests Prof...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/TPXCRML4/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli.html}
+}
+
+@audio{schmidtByteSizedHowGet2026,
+ title = {[{{EN}}] {{ByteSized}}: How to Get Your (Digital) Ducks in a Row - with {{Richard Acton}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{ByteSized}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-03},
+ url = {https://www.buzzsprout.com/1326658/episodes/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton},
+ urldate = {2026-03-16},
+ abstract = {English Edition (ByteSized): In this first episode of the new ByteSized dRTP season, sponsored by the STEP-UP programme from the EPSRC (UK) you'll meet Richard Acton. Richard created a tool to help you keep track of all the steps you should take t...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-13T15:23:08.156Z},
+ file = {/Users/tit420/Zotero/storage/44JQ455Z/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton.html}
+}
+
+@audio{schmidtNextBrainExploringHuman2026,
+ title = {[{{EN}}] {{NextBrain}}: Exploring the Human Brain - {{Eugenio Iglesias}}, {{James Hughes}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{NextBrain}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-17},
+ url = {https://www.buzzsprout.com/1326658/episodes/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes},
+ urldate = {2026-04-13},
+ abstract = {English Edition:\ NextBrain is a next generation atlas of the human brain. Juan Eugenio Iglesias Gonzales from Massachusetts General in Boston, US, has been leading this project. My colleague James Hughes (University College London) and I were...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/MV3BC6VR/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes.html}
+}
+
+@audio{schmidtRevealingStructureCrystals2026,
+ title = {[{{EN}}] {{Revealing}} the Structure of Crystals and Proteins with {{CrystFEL}} - {{Thomas White}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-10},
+ url = {https://www.buzzsprout.com/1326658/episodes/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white},
+ urldate = {2026-03-16},
+ abstract = {English Edition:\ Meet Thomas White from DESY (German Electron Synchrotron) who is the creator and maintainer of the tool CrystFEL. The tool to help understand and analyse the structure of materials such as crystals and proteins. Thomas and I ...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-04-13T15:23:08.155Z},
+ file = {/Users/tit420/Zotero/storage/DSPJ2H3G/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white.html}
+}
+
+@audio{schmidtTeamPortraitResearch2026,
+ title = {[{{EN}}] {{Team Portrait}}: {{Research Software Engineering}} in {{Newcastle}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Team Portrait}}},
+ author = {Schmidt, Peter},
+ date = {2026-03-24},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/18761138-en-team-portrait-research-software-engineering-in-newcastle},
+ urldate = {2026-04-13},
+ abstract = {English Edition:\ for this episode we're going "up North", to visit the Research Software Engineering team of the University of Newcastle. The team has been hosting the UK RSE Conference in 2022 and 2024 and here is a chance to meet at least s...},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/ZST9FS63/18761138-en-team-portrait-research-software-engineering-in-newcastle.html}
+}
+
+@online{schreinerClaudeCodeReviews2026,
+ title = {Claude {{Code Reviews}} with {{Fable}}},
+ author = {Schreiner, Henry},
+ date = {2026-06-16T20:00:00-04:00},
+ url = {https://iscinumpy.dev/post/claude-code-reviews/},
+ urldate = {2026-06-17},
+ abstract = {Fable came out and then disappeared a couple of days later. In that short time, I managed to run a lot of repository reviews with it, and was really happy with the results. I’ve found and fixed around 400 bugs and 400+ other issues (performance, simplifications, modernizations) across dozens of my projects, making several hundred PRs with a nearly 100\% merge rate on decided PRs.},
+ langid = {english},
+ organization = {ISciNumPy.dev},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-17T16:59:48.292Z},
+ file = {/Users/tit420/Zotero/storage/RI3ZH3FE/claude-code-reviews.html}
+}
+
+@online{SilentScientistWhen2025,
+ title = {The {{Silent Scientist}}: {{When Software Research Fails}} to {{Reach Its Audience}} – {{Communications}} of the {{ACM}}},
+ shorttitle = {The {{Silent Scientist}}},
+ date = {2025-10-10},
+ url = {https://cacm.acm.org/opinion/the-silent-scientist-when-software-research-fails-to-reach-its-audience/},
+ urldate = {2025-11-07},
+ langid = {american},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.785Z},
+ file = {/Users/tit420/Zotero/storage/FJTWCUCL/the-silent-scientist-when-software-research-fails-to-reach-its-audience.html}
+}
+
+@article{SixFactorsAffecting,
+ title = {Six Factors Affecting Reproducibility in Life Science Research and How to Handle Them},
+ url = {https://www.nature.com/articles/d42473-019-00004-y},
+ urldate = {2025-11-07},
+ abstract = {Scientific advancement depends on a strong foundation of data credibility. However, scientific findings in biomedical research are not always reproducible. Meet the organizations that are promoting best practices and helping researchers perform the highest-quality science.},
+ langid = {english},
+ annotation = {Bandiera\_abtest: a\\
+Cg\_type: Advertisement Feature\\
+Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/BEP9NG58/d42473-019-00004-y.html}
+}
+
+@online{stetskovClaudeCodesSource2025,
+ title = {Claude {{Code}}'s {{Source}}: 3,167-{{Line Function}}, {{Regex Sentiment}}},
+ shorttitle = {Claude {{Code}}'s {{Source}}},
+ author = {Stetskov, Denis},
+ date = {2025-09-19},
+ url = {https://techtrenches.dev/p/the-snake-that-ate-itself-what-claude},
+ urldate = {2026-04-08},
+ abstract = {Anthropic claimed 100\% of Claude Code is AI-written. A source leak exposed a 3,167-line function, regex sentiment analysis, and 250K wasted API calls daily},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
+}
+
+@online{stetskovGreatSoftwareQuality2026,
+ title = {The {{Great Software Quality Collapse}}: {{How We Normalized Catastrophe}}},
+ shorttitle = {The {{Great Software Quality Collapse}}},
+ author = {Stetskov, Denis},
+ date = {2026-04-01},
+ url = {https://techtrenches.dev/p/the-great-software-quality-collapse},
+ urldate = {2026-04-15},
+ abstract = {The Apple Calculator leaked 32GB of RAM.},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.499Z},
+ file = {/Users/tit420/Zotero/storage/VUFBP9NQ/the-great-software-quality-collapse.html}
+}
+
+@online{substackArtificialIntelligenceCan,
+ title = {Artificial {{Intelligence}} Can {{Erase Technical Debt}}},
+ author = {Substack},
+ url = {https://substack.com/home/post/p-193978032},
+ urldate = {2026-04-15},
+ abstract = {Claude Code and I rewrote a nine year old, complex Python project I maintain, in GoLang, in 5 Days},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.499Z},
+ file = {/Users/tit420/Zotero/storage/2K2KH76T/p-193978032.html}
+}
+
+@report{teranishiS4PSTStewardshipAdvancement2026,
+ title = {{{S4PST}}: {{Stewardship}} and {{Advancement}} for {{Programming Systems}} and {{Tools}} 2024-2025 {{Project Report}}},
+ shorttitle = {{{S4PST}}},
+ author = {Teranishi, Keita and Godoy, William and Valero Lara, Pedro and Schanen, Michel and Applencourt, Thomas and Hueckelheim, Jan and Raffenetti, Ken and Thakur, Rajeev and Videau, Brice and Zhou, Hui and Rouson, Damian and Bonachea, Dan and Hargrove, Paul and Richardson, Brad and Rasmussen, Katherine and Blashcke, Johannes and Laguna, Ignacio and Doerfert, Johannes and Georgakoudis, Giorgis and Parasyris, Konstantinos and Penades, Kevin and Cormick, Patrick and Edelman, Alan and Alomairy, Rabab and Samaroo, Julian and Arndt, Daniel and Denny, Joel and Lebrun-Grandie, Damien and Lee, Seyong and Naughton III, Thomas and Pophale, Swaroop and Parete-Koon, Suzanne and Trott, Christian and Rajamanickam, Siva and Kelley, Brian and Aiken, Alex and Chandrasekaran, Sunita},
+ date = {2026-01-12},
+ number = {ORNL/SPR--2026/4406},
+ institution = {Oak Ridge National Laboratory (ORNL), Oak Ridge, TN (United States)},
+ doi = {10.2172/3016977},
+ url = {https://www.osti.gov/biblio/3016977},
+ urldate = {2026-04-08},
+ abstract = {We present the "Stewardship and Advancement of Programming Systems and Tools" (S4PST) project report for the calendar years 2024 and 2025. S4PST is dedicated to the stewardship and advancement of Programming Systems and Tools (PST) mainly targeting high-performance computing (HPC) for the scientific community. The project is part of the funded software stewardship organizations (SSOs) selected by ASCR as part of the NGSST program, and a member of CASS: the Consortiumfor the Advancement of Scientific Software.},
+ langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-05-21T02:36:15.500Z},
+ file = {/Users/tit420/Zotero/storage/UYMG4WYZ/Teranishi et al. - 2026 - S4PST Stewardship and Advancement for Programming Systems and Tools 2024-2025 Project Report.pdf}
+}
+
+@online{udellHowMakeBest2026,
+ title = {How to Make Best Use of Git and {{GitHub}} for {{AI-assisted}} Software Development},
+ author = {Udell, Jon},
+ date = {2026-06-02T19:41:11+00:00},
+ url = {https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/},
+ urldate = {2026-06-16},
+ abstract = {I’m working on a new tool whose tagline is the title of this post: Make best use of git and GitHub for AI-assisted software development. Called Bram (“Bram runs agents mindfully”)…},
+ langid = {american},
+ organization = {How to make best use of git and GitHub for AI-assisted software development},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:18:22.799Z},
+ file = {/Users/tit420/Zotero/storage/74BXFIZD/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development.html}
+}
+
+@online{UnderstandingAdvancingResearch2025,
+ title = {Understanding and Advancing Research Software Grant Funding Models},
+ date = {2025-07-25},
+ doi = {10.12688/openreseurope.20210.1},
+ url = {https://open-research-europe.ec.europa.eu/articles/5-199/v1},
+ urldate = {2025-11-07},
+ abstract = {Read the latest article version by Daniel S. Katz, Eric A. Jensen, Michelle Barker at Open Research Europe},
+ langid = {english},
+ organization = {Open Research Europe | Open Access Publishing Platform},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
+ file = {/Users/tit420/Zotero/storage/UVZXHIQE/v1.html}
+}
+
+@audio{WhatHappenedAgile2026,
+ title = {[{{EN}}] {{What}} Happened to Agile Development? - {{A}} Review with {{Dave Thomas}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{What}} Happened to Agile Development?},
+ author = {Schmidt, Peter},
+ date = {2026-06-16},
+ url = {https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas},
+ urldate = {2026-06-16},
+ abstract = {English Edition:\ I want to come back to agile development practices with my guest Dave Thomas, or Pragmatic Dave as he is also known in the trade. Dave is one of the authors of the manifesto for agile development - and we talk about what has ...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/NBJV5ZD6/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas.html}
+}
+
+@audio{WhenBitsRot2026,
+ title = {[{{EN}}] {{When Bits Rot}} - with {{C McKean}}, {{L Talboom}}, {{A Page-Mitchell}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-06-09},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell},
+ urldate = {2026-06-16},
+ abstract = {English Edition: floppy disks, hard drives, CDs, DVDs, SSD drives - no matter what you choose to store your data on - ultimately they all decay. With my guests Callum McKean, Leontien Talboom and Adrian Page-Mitchell, we're going to talk about wha...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/YGL4ZLC9/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell.html}
+}
diff --git a/_posts/newsletters/2026-08-05-newsletter.md b/_posts/newsletters/2026-08-05-newsletter.md
new file mode 100644
index 000000000..43c6b7bc9
--- /dev/null
+++ b/_posts/newsletters/2026-08-05-newsletter.md
@@ -0,0 +1,503 @@
+---
+layout: post
+title: "US-RSE Summer 2026 Newsletter"
+subtitle: "Summer is in full swing, which means US-RSE is right around the corner..."
+category: newsletter
+tags: [newsletter, August]
+date: 2026-08-05 00:00:00 -0400
+author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
+image: "/assets/img/newsletter-202606/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg" #Done
+img_alttext: "A railway traffic controller with his back to the camera, looking at several screens with train camera feed and data." #Done
+next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
+sections:
+ preamble: true #Done
+ headline: true #Done
+ conference: true #Done
+ execupdate: false #TODO
+ scupdate: false #TODO
+ orgmember: false #TODO
+ communityfunds: false #TODO
+ news: true #TODO
+ events: true #TODO
+ reads: true #TODO
+ involved: true
+ jobs: true
+
+---
+
+Hi all, it's been a minute!
+
+Welcome to the Summer 2026 edition of the US-RSE newsletter! In this issue, we are packing in several updates and highlights
+from the community, and gearing up for USRSE26! Read on for all the latest updates, including upcoming events, recent accomplishments,
+and opportunities to get involved in the RSE community.
+
+Most importantly, get excited — the conference is just around the corner!
+
+So grab a beverage and settle in as we recap all kinds of updates from the summer!
+In this issue...
+
+
+
+
+
+- [1 🤔 Arrestive Curiosity &
+ RSEs: Turning Shiny Toy Syndrome into a Feature
+ 🤔](#thinking-arrestive-curiosity--rses-turning-shiny-toy-syndrome-into-a-feature-thinking)
+- [2 📣 Mark Your Calendars for
+ USRSE’26! 📣](#mega-mark-your-calendars-for-usrse26-mega)
+- [3 🗞️ Community News
+ 🗞️](#newspaper_roll-community-news-newspaper_roll)
+- [4 Community
+ Spotlight](#community-spotlight)
+- [5 👀 Interesting Events and
+ Opportunities 👀](#eyes-interesting-events-and-opportunities-eyes)
+- [6 📚 Featured Reads, Videos,
+ and Podcasts 📚](#books-featured-reads-videos-and-podcasts-books)
+- [7 🏃 Get Involved!
+ 🏃](#running-get-involved-running)
+- [8 🧑💼 Recent Job Postings
+ 🧑💼](#office_worker-recent-job-postings-office_worker)
+
+
+
+------------------------------------------------------------------------
+
+## 🤔 Arrestive Curiosity & RSEs: Turning Shiny Toy Syndrome into a Feature 🤔
+
+
+
+This summer I met some fellow R users at the Boston R User Group meetup,
+where I finally felt safe saying, “R is the best at \[X\],” without
+starting a flame war. Of course, most of us know these debates are
+rarely about which tool is objectively best. Rather, they’re about which
+tool is best for a person, a project, or a team.
+
+Which sounds liberating, until it raises a harder question: when should
+you switch tools?
+
+Technology is full of shiny promises, current LLM trends
+notwithstanding. New tools are constantly clamouring for our attention,
+claiming they will solve the frustrations of the old ones, and it is
+hard to know when experimentation with the new is wise and when it is
+just distraction.
+
+Ignore new tools completely, and you may miss something genuinely
+useful. Chase every new one, and you lose days to tinkering.
+
+For RSEs, this tension might just be part of the territory. Many of us
+are helping scientific teams navigate changing cutting edge *questions*,
+which means we are constantly judging whether experimentation with
+cutting edge *tools* is worth the cost. That can make “shiny toy
+syndrome” feel like a liability, at first.
+
+But I think there is a more useful way to frame it: as **arrestive
+curiosity**.
+
+By that I mean the kind of curiosity that stops you in your tracks until
+you can decide whether a new tool is actually better than the one you
+already have. It can absolutely become a time sink — but it can also be
+a professional strength, if you give it some structure.
+
+Here are four questions I constantly reference in order to keep my
+curiosity productive:
+
+1. *What problem am I actually trying to solve?*
+ Before investigating a new tool, write down the need as clearly as
+ possible. Often the exercise reveals that the current workflow only
+ needs a small adjustment, not a new platform.
+
+2. *How costly is the current pain?*
+ If the problem is real, measure it. How much time, energy, or team
+ morale is it costing? If the discomfort is tolerable, a switch may
+ not be worth it.
+
+3. *Refine to absurdum.* If you are still convinced that something is
+ missing, then it is time to start looking for what is missing.
+ Surely someone has felt this acute pain, right? The internet is a
+ vast place, and there are several billion of us using it at any
+ given time. It’s more than likely that someone, somewhere, has been
+ in the exact position you’re in, with an install that is too slow, a
+ link that doesn’t work, or a workflow that is too clunky and just
+ missing that, *secret something*. Go out into dark corners of the
+ second, third, and fourth pages of Google search, ask around on
+ Reddit and Facebook groups, or find forums and communities that are
+ relevant to the problem space. Surely **someone** has faced this
+ problem, too?
+
+4. If the solution is identified, use it. If not, build it. By this
+ point, if you have found a niche problem that 1) arrests your
+ productivity, 2) causes measurable discomfort, and 3) has not been
+ solved by anyone else, then this is a problem worth solving. In
+ fact, as an RSE, this is the *perfect* problem to have, because it
+ is within this narrow gap between your vision and the status quo
+ that you can actually make valuable impact to your team. If you
+ can’t or don’t want to build the solution yourself, one of two
+ things must be true: either the problem is not worth solving, or you
+ are *not yet* the right person to solve it.
+
+In my experience, the really interesting Research Software Engineering
+is what happens when as an engineer I have become *obsessed* with a
+particular technological blocker to the success of my or my colleagues’
+scientific endeavors.
+
+It is the moment we look at the scientific engine and say, “I know we
+*could* just use \[X Tool\] to write this part of the paper, but I just
+can’t accept that this is the best way to do it. I simply can’t. There
+*must* be a better way.”
+
+This is the “arrestive,” part of “arrestive curiosity” — the part that
+keeps you up at night, ceases you in your tracks every time you think
+about it, and continues to consume all of your mental energy until you
+have either found a solution or come to terms with the fact that there
+is no solution.
+
+And if you ask me, that tendency to be obsessed with finding the best
+way to do science is what makes a good RSE a *great* RSE. So, the next
+time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I
+outlined above, and see where it takes you. You might just find that the
+perfect tool was right in front of you all along, or you might end up
+building something that changes the game for you, your team, and perhaps
+even the science itself.
+
+------------------------------------------------------------------------
+
+## 📣 Mark Your Calendars for USRSE’26! 📣
+
+
+
+Save the date for USRSE’26: **Advancing Science in the Age of AI**
+
+
+
+
+
+
+USRSE’26, to be held at the San Jose Marriott from October 19-21, 2026
+in San Jose, California, with the theme **“Advancing Science in the Age
+of AI”,** is ALMOST HERE!
+
+Chairs have been appointed to lead each of the core committees for
+USRSE’26. These chairs have begun assembling sub‑teams from the pool of
+volunteers who expressed interest in supporting the respective areas. If
+you were not selected for a chair position, please stay tuned, as chairs
+may reach out for volunteers for these committee positions.
+
+**What’s next?**
+
+- ~~**Call for Proposals:** Submit your work via papers, short talks,
+ BoFs, workshops, or posters. [View
+ More](https://us-rse.org/usrse26/participate/)~~
+- ~~**Call for Reviewers:** Play a key role in creating a dynamic and
+ varied technical program that will appeal to conference attendees from
+ all RSE backgrounds. [Apply to
+ Review](https://forms.gle/hDGsK52sJFqUA2MA7)~~
+- **Committee Formation:** Sub‑teams will be formed shortly; be on the
+ lookout for an email from a perspective committee chair with details.
+- **Stay Informed:** Regular updates will be posted at
+ [us-rse.org/usrse26](https://us-rse.org/usrse26). Please bookmark the
+ page and check back frequently for the latest information.
+
+Your continued involvement is essential to the success of USRSE’26. We
+look forward to collaborating with you to deliver a vibrant, inclusive,
+and impactful conference.
+
+#### 📧 Join Our Mailing List 📧
+
+Want to stay updated on all things US-RSE? Join our mailing list to
+receive direct news about all US-RSE conferences. Sign up
+[here](https://groups.google.com/a/us-rse.org/g/usrse-conference).
+
+#### 💬 Have Questions? 💬
+
+If you have any questions, feel free to reach out to the organizers at
+usrse26-conference@us-rse.org.
+
+#### 📅 Save the Date 📅
+
+Travel information, including hotel details and travel tips, are
+available. Stay informed at
+[us-rse.org/usrse26](https://us-rse.org/usrse26)!
+
+We’re looking forward to seeing you all in **San Jose** very, very soon!
+
+------------------------------------------------------------------------
+
+## 🗞️ Community News 🗞️
+
+
+
+### The Whole Person: Pride and Belonging in US-RSE
+
+Pride Month is both a celebration and a moment for reflection for the
+communities we are part of. As the chairs of the DEI Working Group, we
+welcome everyone to celebrate Pride Month with the US‑RSE community this
+June and beyond. We also want to take a moment to reflect on what Pride
+means to me and how it shapes how we think about belonging in our
+professional communities.
+
+US‑RSE is a community built around shared skills, interests, and goals
+centered on advancing research through software engineering. While that
+core set of interests brings us together, we are also a collection of
+individuals who work across different research domains and parts of the
+software engineering lifecycle. Each person brings unique strengths and
+perspectives.
+
+A mix of viewpoints helps teams generate stronger ideas and advance
+research. That kind of collaboration works best when people feel a sense
+of belonging.
+
+At the same time, we don’t show up to these communities as just “RSEs.”
+Each of us brings life experiences, preferences, and unique quirks. You
+can’t interact with just the “software engineer” side of someone. You
+interact with the whole person, which means accepting them as they are.
+
+That’s where belonging comes from. It’s not just about being part of a
+group with shared interests. It’s about being accepted as you
+are.Creating that kind of belonging can be challenging in practice,
+especially when building trust with people who have experienced bias,
+exclusion, or worse.
+
+That’s why small actions matter. Sharing pronouns, using gender‑neutral
+language, and taking the time to learn about the people around us can
+make a real difference. They signal that people are seen, respected, and
+welcome as part of the community.
+
+For us, Pride is a reminder that this kind of belonging does not happen
+by accident. It is something we create together through everyday
+choices.
+
+Pride means different things to different people. To reflect that range
+of experiences, we invite members of the US‑RSE community to share what
+Pride means to them and how they think about belonging in their work.
+
+What does Pride mean to you? We’d love to hear your perspective. Feel
+free to join the conversation on Slack or share on social media using
+the hashtag `#RSEPride`.
+
+##### Community Contributions
+
+> Research software often involves intensely multidisciplinary
+> collaboration, and, depending on the size of a team, may require the
+> ability to liaise between domains, technical-side, business-side, etc.
+> and advocate whether it’s for data integrity processes or for
+> underweighted voices. In my mind this relational communication and
+> openness is very prosocial and qualitatively close to what Pride is
+> all about; I think it’s why I feel at home in research software and
+> the surrounding communities. – Michael P. Pascale
+
+> I actually did not grow up playing with computers. I always was tech
+> savvy, but never imagined myself opening a terminal or writing code.
+> So when I found myself engaging with technology in research, I was
+> very intimidated, often suffixing all of my conversations with, “but I
+> don’t know anything about this stuff.” That feeling of imposter
+> syndrome went away when I joined the RSE community, and I owe my
+> career success to the culture of support and encouragement that I
+> found here. Celebrating Pride Month with the LGBTQ+ community every
+> year is a reminder of how unconditional acceptance and support enables
+> people to self-actualize and thrive. I stand with my LGBTQ+ allies in
+> celebrating them and advocating for their space in our world! -
+> Tinashe M. Tapera
+
+
+
+### **Community Shoutouts**
+
+🥳 Congratulations to members of the RSE community recognized with
+[Stanford Data Science
+(CORES)](https://datascience.stanford.edu/cores/awards) awards!
+
+- Malcolm Barrett & Alex Koufos : OpenSource@Stanford Community Prize
+- Ellianna Abrahams: Open Science Innovator Prize
+
+These awards recognize individuals who have made significant
+contributions to open science and data science, and we’re thrilled to
+see members of our community being honored for their impactful work!
+
+Additionally, The RAPTOR team from Argonne National Laboratory and
+collaborating institutions recently won the SC25 Best Reproducibility
+Advancement Award, using Chameleon Cloud to make their artifact fully
+reproducible. This marks the second consecutive year a Chameleon user
+has taken home this honor!
+
+Read the announcement
+[here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
+
+> Did you know that we have a community Code of Conduct? Anyone is able
+> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+
+### In Memoriam
+
+We mourn the loss of a dear friend and colleague, Cleve Moler, who
+passed away on May 20, 2026, at the age of 86 at his home surrounded by
+his family. Cleve was chief mathematician and cofounder of MathWorks and
+the author of the first version of MATLAB. Please join us in remembering
+their contributions to science and engineering by reading Mathworks
+official announcement
+[here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
+
+## Community Spotlight
+
+🌱 Our community is full of people doing fascinating research and
+software work, and we want to put a face to it. Starting this month,
+we’ll be featuring a group of different members in a regular spotlight:
+what they work on, a tool they can’t live without, and how they found
+their way into RSE work.
+
+We’d love to feature YOU. It takes about 5 minutes to fill out, and
+nothing gets posted without your okay:
+
+
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
+
+### **Community Calls**
+
+
+
+
+
+Our next meeting is scheduled for Thursday, July 9, 2026, 12:00PM EST.
+We hope to see you there!
+
+------------------------------------------------------------------------
+
+## 👀 Interesting Events and Opportunities 👀
+
+
+
+{% assign today = "now" | date: "%Y-%m-%d" %}
+{% for opp in site.data.newsletter.events-opportunities %}
+{% assign expires = opp.expires | date: "%Y-%m-%d" %}
+{% if opp.type == "opportunity" and expires >= today %}
+{% include opportunity-box.html
+ title=opp.title
+ when=opp.when
+ where=opp.where
+ preamble=opp.preamble
+ links=opp.links
+%}
+{% endif %}
+{% endfor %}
+
+{% for event in site.data.newsletter.events-opportunities %}
+{% assign expires_formatted = event.expires | date: "%Y-%m-%d" %}
+{% if expires_formatted >= today %}
+{% if event.type == "event" %}
+{% include event-box.html
+ title=event.title
+ when=event.when
+ where=event.where
+ preamble=event.preamble
+ links=event.links
+%}
+{% endif %}
+{% endif %}
+{% endfor %}
+
+Have an event or opportunity you want to promote? Reach out on Slack in
+the `#newsletters` channel!
+
+------------------------------------------------------------------------
+
+## 📚 Featured Reads, Videos, and Podcasts 📚
+
+
+
+### 📑 Recent Publications
+
+{% assign article_refs = site.data.newsletter.articles.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
+
+{% if article_refs.size > 0 %}
+{% for ref in article_refs %}
+{% include citation-article.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+### 📇 Blog Posts & Other Reads
+
+{% assign blog_refs = site.data.newsletter.blogs.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
+
+{% if blog_refs.size > 0 %}
+{% for ref in blog_refs %}
+{% include citation-blog.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+### 🎧 Podcast Episodes, Videos, and More
+
+{% assign media_refs = site.data.newsletter.media.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
+
+{% if media_refs.size > 0 %}
+{% for ref in media_refs %}
+{% include citation-media.html ref=ref %}
+{% endfor %}
+{% endif %}
+
+Did you read something interesting this week? Want to share your own
+publications in the community? Reach out on Slack in the `#newsletters`
+channel!
+
+------------------------------------------------------------------------
+
+## 🏃 Get Involved! 🏃
+
+
+
+US-RSE Working Groups:
+
+{% assign wgs = site.data.menus["working-groups"][0].items %}
+
The following object is masked from 'package:purrr':
+
+ flatten
+
+
library(tibble)
+library(fs)
+library(DT2)
+
+
This notebook contains helper snippets for the US-RSE newsletter. It is intended to parse data into YAML before it is used in the newsletter template.
+
The directory should be self-contained, so that it doesn’t interfere with any other US-RSE Website content. No software is installed, and no changes are being made to the US-RSE Website. The notebook is intended to be run in a local environment, not as part of CI/CD.
Warning in readLines(file, warn = readLines.warn): incomplete final line found
+on
+'/Users/tit420/projects/usrse.github.io/_posts/newsletters/quarto/_data/newsletter-events-opportunities.yml'
+
+
+
+
+
Slack Data
+
Next, we’ll grab the Slack data from the Newsletter Content Triage List. We could use the Slack API, but I think it’s actually easier to export the list content as CSV and git track it in the _data directory.
+
Importantly, the most recent file is the one we want to keep; Slack doesn’t automatically overwrite the CSV, so we have to manually delete old files.
Rows: 71 Columns: 11
+── Column specification ────────────────────────────────────────────────────────
+Delimiter: ","
+chr (9): Submission, What Section(s) of the Newsletter Would this Content F...
+date (2): Event Date, Content Expiration Date
+
+ℹ Use `spec()` to retrieve the full column specification for this data.
+ℹ Specify the column types or set `show_col_types = FALSE` to quiet this message.
+2. _How costly is the current pain?_
+If the problem is real, measure it. How much time, energy, or team morale is it costing? If the discomfort is tolerable, a switch may not be worth it.
-
+3. _Refine to absurdum._ If you are still convinced that something is missing, then it is time to start
+looking for what is missing. Surely someone has felt this acute pain, right? The internet is a vast place,
+and there are several billion of us using it at any given time. It's more than likely that someone,
+somewhere, has been in the exact position you're in, with an install that is too slow, a link that
+doesn't work, or a workflow that is too clunky and just missing that, _secret something_. Go out into dark
+corners of the second, third, and fourth pages of Google search, ask around on Reddit and Facebook groups, or
+find forums and communities that are relevant to the problem space. Surely **someone** has faced this problem, too?
-
+4. If the solution is identified, use it. If not, build it. By this point, if you have found a
+niche problem that 1) arrests your productivity, 2) causes measurable discomfort, and 3) has not been
+solved by anyone else, then this is a problem worth solving. In fact, as an RSE, this is the _perfect_
+problem to have, because it is within this narrow gap between your vision and the status quo that
+you can actually make valuable impact to your team. If you can't or don't want to build the solution yourself,
+one of two things must be true: either the problem is not worth solving, or you are _not yet_ the right person to solve it.
-Goth et al. ([2025](https://f1000research.com/articles/13-1429)) offer one recent attempt to concretize the foundational competencies and responsibilities of an RSE, including software development, building and distributing software assets, understanding the research lifecycle, and supporting reproducible, sustainable research. [Vanessa Sochat's EasyBuild talk](https://www.youtube.com/watch?v=FB2yV8TNnSw), on the other hand, emphasizes just how broad this space can be: among roughly 400 people surveyed who identified themselves to be working on "research software" in some capacity, there were more than *190 unique job titles*. That degree of diversity can be both a strength and a challenge. It shows how widely research software work appears across institutions, but it also explains why the role can be so difficult to define, hire for, promote, and reward. Another one of our US-RSE members, Dan Katz, proposes a 3-dimensional schematic
-to isolate the Super RSE role who commands "a superset of the responsibilities of the traditional RSE role, combining both service and the RSE’s own research."
+In my experience, the really interesting Research Software Engineering is what happens when as an
+engineer I have become _obsessed_ with a particular technological blocker to the success of my or my colleagues' scientific endeavors.
-
-
-
+It is the moment we look at the scientific engine and say, "I know we _could_ just use [X Tool] to write
+this part of the paper, but I just can't accept that this is the best way to do it. I simply can't. There
+_must_ be a better way."
-By identifying this RSE unicorn, Katz highlights the fact that as we define
-the breadth of the scope of the RSE, we also need to think about its
-potentially necessary boundaries.
+This is the "arrestive," part of "arrestive curiosity" — the part that keeps you up at night,
+ceases you in your tracks every time you think about it, and continues to consume all of your mental
+energy until you have either found a solution or come to terms with the fact that there is no solution.
-In a 2022 [career Q&A in *Nature*](https://www.nature.com/articles/d41586-022-01516-2), Paul Richmond predicted that RSEs could become equals in the academic environment if they receive proper recognition for their contributions. James Schloss, in his [YouTube talk](https://www.youtube.com/watch?v=t2BjZ5hSjHo) highlights some of the barriers still standing in the way: the publication economy, academic resistance to software engineering best practices, and the difficulty of competing with industry salaries for people with similar technical expertise. In fact, one of my very first suggestions for newsletter topics was to discuss the definition of the title "Research Software Engineer" itself, and I was told very firmly to avoid the topic as much as possible — not because it was inflammatory, but because it remains a particularly sensitive topic. While many are strongly attached to the name for its truthiness, just as many others are more concerned with defining the tasks, responsibilities, and competencies of the role, regardless of what it is called, because funding sources will pay a great deal of attention to those details.
-
-But friends, there is hope. 🌱
-
-Just as a small group of concerned scientists and software practitioners began with an idea, a conversation, and a Google Group, we can continue making the role visible at our own institutions. This can be through formal titles, clearer career paths, better credit, stronger communities of practice, or simply naming the work when we see it as we help research software engineering become easier to recognize and harder to ignore. This week, celebrate yourself by encouraging your colleagues, coworkers, PIs, and students to **make this role visible**. Look around. We are once again watching technology change the fabric of research itself. Rigorous science, and the software that powers it, cannot afford to be left behind. Now more than ever, research needs talented, driven, curious technology specialists who can ask new questions, solve impossible bugs, push compute clusters to their limits, and preserve the code — and the science — that so many people depend on.
-
-Our Executive Director had this to say about the importance of this community:
-
-"Reaching more than 4,000 members is not just a milestone in numbers - it reflects a growing
-community of people who care deeply about advancing research through software, collaboration, and
-support for one another. As Executive Director, I am incredibly grateful to be part of this community
-and inspired every day by the generosity, expertise, and passion our members bring to US-RSE. Thank
-you for helping build a place where research software engineers can truly belong."
-
-> [Sandra](https://us-rse.org/about/staff/)
-
-This month, we thank the scrappy and passionate group of researchers who helped crystallize the idea of the Research Software Engineer, [one quiet afternoon in Oxford, UK, in 2012](https://www.pure.ed.ac.uk/ws/portalfiles/portal/65195747/DR2012_12_1_.pdf). And the next time you notice a colleague struggling with a technical problem, be the RSE on their shoulder. Gently remind them:
-
-*Hey, I know how to do that.*
-
-> You are braver than you believe, stronger than you seem, and smarter than you think. A. A. Milne, *Winnie the Pooh*
+And if you ask me, that tendency to be obsessed with finding the best way to do science is what makes a good
+RSE a _great_ RSE. So, the next time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I outlined above, and see where it takes you.
+You might just find that the perfect tool was right in front of you all along, or you might end up building
+something that changes the game for you, your team, and perhaps even the science itself.
------------------------------------------------------------------------
\ No newline at end of file
diff --git a/_posts/newsletters/quarto/_news.md b/_posts/newsletters/quarto/_news.md
index 7ca41c102..27912b247 100644
--- a/_posts/newsletters/quarto/_news.md
+++ b/_posts/newsletters/quarto/_news.md
@@ -2,6 +2,73 @@
+### The Whole Person: Pride and Belonging in US-RSE
+
+Pride Month is both a celebration and a moment for reflection for the communities
+we are part of. As the chairs of the DEI Working Group, we welcome everyone
+to celebrate Pride Month with the US‑RSE community this June and beyond.
+We also want to take a moment to reflect on what Pride means to me and how it shapes
+how we think about belonging in our professional communities.
+
+US‑RSE is a community built around shared skills, interests, and goals centered
+on advancing research through software engineering. While that core set of
+interests brings us together, we are also a collection of individuals who work
+across different research domains and parts of the software engineering lifecycle.
+Each person brings unique strengths and perspectives.
+
+A mix of viewpoints helps teams generate stronger ideas and advance research. That
+kind of collaboration works best when people feel a sense of belonging.
+
+At the same time, we don’t show up to these communities as just
+“RSEs.” Each of us brings life experiences, preferences, and unique quirks. You
+can’t interact with just the “software engineer” side of someone. You interact with
+the whole person, which means accepting them as they are.
+
+That’s where belonging comes from. It’s not just about being part of a
+group with shared interests. It’s about being accepted as you are.Creating that
+kind of belonging can be challenging in practice, especially
+when building trust with people who have experienced bias, exclusion, or worse.
+
+That’s why small actions matter. Sharing pronouns, using gender‑neutral
+language, and taking the time to learn about the people around us can make
+a real difference. They signal that people are seen, respected, and
+welcome as part of the community.
+
+For us, Pride is a reminder that this kind of belonging does not happen
+by accident. It is something we create together through everyday choices.
+
+Pride means different things to different people. To reflect that range
+of experiences, we invite members of the US‑RSE community to share what Pride
+means to them and how they think about belonging in their work.
+
+What does Pride mean to you? We’d love to hear your perspective. Feel free to
+join the conversation on Slack or share on social media using the hashtag `#RSEPride`.
+
+##### Community Contributions
+
+> Research software often involves intensely multidisciplinary collaboration,
+> and, depending on the size of a team, may require the ability to liaise
+> between domains, technical-side, business-side, etc. and advocate whether
+> it's for data integrity processes or for underweighted voices. In my mind
+> this relational communication and openness is very prosocial and
+> qualitatively close to what Pride is all about; I think it's why I feel at
+> home in research software and the surrounding communities.\n
+> – Michael P. Pascale
+
+> I actually did not grow up playing with computers. I always was tech
+> savvy, but never imagined myself opening a terminal or writing code.
+> So when I found myself engaging with technology in research, I was
+> very intimidated, often suffixing all of my conversations with, "but
+> I don't know anything about this stuff." That feeling of imposter
+> syndrome went away when I joined the RSE community, and I owe my
+> career success to the culture of support and encouragement that I found here.
+> Celebrating Pride Month with the LGBTQ+ community every year
+> is a reminder of how unconditional acceptance and support enables people
+> to self-actualize and thrive. I stand with my LGBTQ+ allies in
+> celebrating them and advocating for their space in our world!\n
+> - Tinashe M. Tapera
+
+
### **Community Shoutouts**
@@ -22,19 +89,24 @@ consecutive year a Chameleon user has taken home this honor!
Read the announcement [here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
-### RSE's with a New York State of Mind... 🗽
+> Did you know that we have a community Code of Conduct? Anyone is able to view it in the
+`#code_of_conduct` Slack channel, under `Files`!
-The NYC Regional Group recently met up for their inaugural
-in-person hangout! Special thanks to Roger Ferger for spearheading the event!
-
-
-
+### In Memoriam
-As an added bonus, the group also now has a dedicated page on the US-RSE website! Check it out [here](https://us-rse.org/ag/rg-nyc/) to learn more about the group and how to get involved.
+We mourn the loss of a dear friend and colleague, Cleve Moler, who passed away on May 20, 2026, at the age of 86 at his home
+surrounded by his family. Cleve was chief mathematician and cofounder of MathWorks and the author of the first version of MATLAB.
+Please join us in remembering their contributions to science and engineering by reading Mathworks official announcement [here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
+
+## Community Spotlight
+
+🌱 Our community is full of people doing fascinating research and software work, and we want to put a face to it. Starting this month, we'll be featuring a group of different members in a regular spotlight: what they work on, a tool they can't live without, and how they found their way into RSE work.
+
+We'd love to feature YOU. It takes about 5 minutes to fill out, and nothing gets posted without your okay: [https://forms.gle/dXqVsHKiHnot2u449](https://forms.gle/dXqVsHKiHnot2u449)
+
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
-> Did you know that we have a community Code of Conduct? Anyone is able to view it in the
-`#code_of_conduct` Slack channel, under `Files`!
### **Community Calls**
diff --git a/_posts/newsletters/quarto/_orgmember.md b/_posts/newsletters/quarto/_orgmember.md
index 232283ae9..589796f05 100644
--- a/_posts/newsletters/quarto/_orgmember.md
+++ b/_posts/newsletters/quarto/_orgmember.md
@@ -7,7 +7,8 @@
US-RSE envisions a future where Research Software Engineers are universally respected for advancing science, technology, and society through the transformative power of research software engineering.
We’re excited to share that the momentum around our Organizational Founding Membership continues to grow! See the list below for the current members (six more are onboarding at the moment).
-Organizations that join **on or before June 30, 2026**, will be recognized in perpetuity as founding members. Founding organizations will also lock in current membership fees through December 31, 2028.
+Organizations that joined **on or before June 30, 2026**, are recognized in perpetuity as founding members, below.
+
Organizational support helps sustain and expand vital community offerings, including the annual conference, monthly calls and newsletter, job board, working groups, and new resources.
Please reach out to Sandra Gesing at [sandra@us-rse.org](mailto:sandra@us-rse.org) if you are interested in becoming an organizational founding member!
diff --git a/_posts/newsletters/quarto/_preamble.md b/_posts/newsletters/quarto/_preamble.md
index fe220c56e..9fad192ff 100644
--- a/_posts/newsletters/quarto/_preamble.md
+++ b/_posts/newsletters/quarto/_preamble.md
@@ -1,10 +1,14 @@
-Well, actually, there are thousands — **four thousand and counting**, to be exact! That's
-right, as of April 2026, US-RSE has grown to over 4,000 registered members! That means if you
-tried to count every member one by one, it would take you [over an hour](https://numbermatics.com/n/4000/) to
-count them all. 4000 is also a Harshad number, which means it's divisible by the sum of its digits (4 + 0 + 0 + 0
-= 4). So, in a way, our membership is mathematically harmonious! Also, did you know
-that the recent Artemis mission flew approximately [4000 miles above the moon's surface](https://science.nasa.gov/solar-system/skywatching/night-sky-network/night-sky-network-celebrates-artemis-ii/)?
-Okay, you get the point — that's a lot of RSEs, and we're thrilled to have each and every one of you as part of our community.
-
-So grab a beverage, sit back, and dive in to the latest news and updates from your
-4000-member-strong community of research software engineers!
\ No newline at end of file
+Hi all, it's been a minute!
+
+Welcome to the Summer 2026 edition of the US-RSE newsletter! In this issue, we are packing in several updates and highlights
+from the community, and gearing up for USRSE26! Read on for all the latest updates, including upcoming events, recent accomplishments,
+and opportunities to get involved in the RSE community.
+
+Most importantly, get excited — the conference is just around the corner!
+
+So grab a beverage and settle in as we recap all kinds of updates from the summer!
+In this issue...
+
+
+
+
diff --git a/_posts/newsletters/quarto/_quarto.yml b/_posts/newsletters/quarto/_quarto.yml
new file mode 100644
index 000000000..0cc4968d2
--- /dev/null
+++ b/_posts/newsletters/quarto/_quarto.yml
@@ -0,0 +1,6 @@
+project:
+ title: "Newsletter Helpers"
+ render:
+ - Newsletter_Helpers.qmd
+
+
diff --git a/_posts/newsletters/quarto/_reads.md b/_posts/newsletters/quarto/_reads.md
index 582201ef4..e593b0250 100644
--- a/_posts/newsletters/quarto/_reads.md
+++ b/_posts/newsletters/quarto/_reads.md
@@ -2,36 +2,43 @@
+### 📑 Recent Publications
```{=markdown}
-{% assign refs = site.data.newsletter_bib_yml.references
+{% assign article_refs = site.data.newsletter.articles.references
| where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
-{% assign professional = refs | where: "type", "article-journal" %}
-
-{% if professional.size > 0 %}
-### 📑 Recent Publications
-{% for ref in professional %}
-{% include citation-publication.html ref=ref %}
+{% if article_refs.size > 0 %}
+{% for ref in article_refs %}
+{% include citation-article.html ref=ref %}
{% endfor %}
{% endif %}
+```
+
+### 📇 Blog Posts & Other Reads
-{% assign podcasts = refs | where: "type", "motion_picture" %}
+```{=markdown}
+{% assign blog_refs = site.data.newsletter.blogs.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
-{% if podcasts.size > 0 %}
-### 🎧 Podcast Episodes
-{% for ref in podcasts %}
-{% include citation-podcast.html ref=ref %}
+{% if blog_refs.size > 0 %}
+{% for ref in blog_refs %}
+{% include citation-blog.html ref=ref %}
{% endfor %}
{% endif %}
+```
+
-{% assign other = refs | where: "type", "webpage" %}
+### 🎧 Podcast Episodes, Videos, and More
+```{=markdown}
+{% assign media_refs = site.data.newsletter.media.references
+ | where_exp: "r", "r.annote contains 'Read_Status: To Read'" %}
-{% if other.size > 0 %}
-### 📇 Blog Posts, Videos, & Other Reads
-{% for ref in other %}
-{% include citation.html ref=ref %}
+{% if media_refs.size > 0 %}
+{% for ref in media_refs %}
+{% include citation-media.html ref=ref %}
{% endfor %}
{% endif %}
+
```
Did you read something interesting this week? Want to share your own publications in the community? Reach out on Slack in the `#newsletters` channel!
diff --git a/_posts/newsletters/quarto/params.yml b/_posts/newsletters/quarto/params.yml
index fa8bca96b..68bfaef0a 100644
--- a/_posts/newsletters/quarto/params.yml
+++ b/_posts/newsletters/quarto/params.yml
@@ -1,24 +1,24 @@
layout: post
-title: "US-RSE May 2026 Newsletter"
-subtitle: "🙌 There Are Dozens of Us, DOZENS! 🙌"
+title: "US-RSE Summer 2026 Newsletter"
+subtitle: "Summer is in full swing, which means US-RSE is right around the corner..."
category: newsletter
-tags: [newsletter, May]
-date: 2026-05-20 00:00:00 -0400
+tags: [newsletter, August]
+date: 2026-08-05 00:00:00 -0400
author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
-image: "/assets/img/newsletter-202605/us-rse_4k_members.png"
-img_alttext: "Colourful poster with the words \"Celebrating 4,000+ Member Milestone\" and a progression of trees growing from a seedling to a full tree, with the number 4011 prominently displayed."
-next_meeting_date: Friday, June 12, 2026, 12:00PM EST
+image: "/assets/img/newsletter-202606/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg" #Done
+img_alttext: "A railway traffic controller with his back to the camera, looking at several screens with train camera feed and data." #Done
+next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
sections:
- preamble: true # done
- headline: true # done
- conference: true # done
- execupdate: false # done
- scupdate: false # yay!
- orgmember: true # done
- communityfunds: false # no changes, check back in june
- news: true # add community call summary
- events: true
- reads: true
+ preamble: true #Done
+ headline: true #Done
+ conference: true #Done
+ execupdate: false #TODO
+ scupdate: false #TODO
+ orgmember: false #TODO
+ communityfunds: false #TODO
+ news: true #TODO
+ events: true #TODO
+ reads: true #TODO
involved: true
jobs: true
diff --git a/_posts/newsletters/quarto/render_new_edition.sh b/_posts/newsletters/quarto/render_new_edition.sh
new file mode 100755
index 000000000..ca917d2ce
--- /dev/null
+++ b/_posts/newsletters/quarto/render_new_edition.sh
@@ -0,0 +1,33 @@
+#!/bin/bash
+set -euo pipefail
+
+preproc_nb=Newsletter_Preproc.qmd
+preproc_html=Newsletter_Preproc.html
+newsletter_template=template.qmd
+params_file=params.yml
+data_dir=_data/newsletter
+intermediate_md=intermediate.md # intermediate file (rendered quarto output without jekyll frontmatter)
+
+# run helper
+quarto render $preproc_nb --to html --output $preproc_html
+
+# render quarto to template
+quarto render $newsletter_template --metadata-file $params_file -o "$intermediate_md"
+# convert Interesting Reads bib to yaml
+pandoc $data_dir/articles.bib -s -f biblatex -t gfm > $data_dir/articles.yml
+pandoc $data_dir/blogs.bib -s -f biblatex -t gfm > $data_dir/blogs.yml
+pandoc $data_dir/media.bib -s -f biblatex -t gfm > $data_dir/media.yml
+
+# copy yaml frontmatter into rendered quarto output
+article=$(mktemp)
+
+{
+ echo "---"
+ cat $params_file
+ echo "---"
+ sed '1,4d' "$intermediate_md"
+} > "$article"
+
+release_date=$(awk '/^date:/ {print $2; exit}' "$params_file")
+mv "$article" "../${release_date}-newsletter.md"
+rm "$intermediate_md"
diff --git a/_posts/newsletters/quarto/template.md b/_posts/newsletters/quarto/template.md
index 4cd7e5bac..587d7839f 100644
--- a/_posts/newsletters/quarto/template.md
+++ b/_posts/newsletters/quarto/template.md
@@ -1,11 +1,11 @@
-# US-RSE May 2026 Newsletter
+# US-RSE June 2026 Newsletter
Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden
(Editor)
-2026-05-20
+2026-06-15
-- [1 🤩 Wait a Minute, I’m an
- RSE, I Know How to Do That!
- 🤩](#star_struck-wait-a-minute-im-an-rse-i-know-how-to-do-that-star_struck)
+- [1 🤔 Arrestive Curiosity &
+ RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature
+ 🤔](#thinking-arrestive-curiosity--rses-how-to-turn-the-shiny-toy-syndrome-bug-into-a-feature-thinking)
- [2 📣 Mark Your Calendars for
USRSE’26! 📣](#mega-mark-your-calendars-for-usrse26-mega)
- [3 🤝 Organizational Founding
@@ -13,192 +13,172 @@ Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden
🤝](#handshake-organizational-founding-membership-handshake)
- [4 🗞️ Community News
🗞️](#newspaper_roll-community-news-newspaper_roll)
-- [5 👀 Interesting Events and
+- [5 Community
+ Spotlight](#community-spotlight)
+- [6 👀 Interesting Events and
Opportunities 👀](#eyes-interesting-events-and-opportunities-eyes)
-- [6 📚 Featured Reads, Videos,
+- [7 📚 Featured Reads, Videos,
and Podcasts 📚](#books-featured-reads-videos-and-podcasts-books)
-- [7 🏃 Get Involved!
+- [8 🏃 Get Involved!
🏃](#running-get-involved-running)
-- [8 🧑💼 Recent Job Postings
+- [9 🧑💼 Recent Job Postings
🧑💼](#office_worker-recent-job-postings-office_worker)
-Well, actually, there are thousands — **four thousand and counting**, to
-be exact! That’s right, as of April 2026, US-RSE has grown to over 4,000
-registered members! That means if you tried to count every member one by
-one, it would take you [over an hour](https://numbermatics.com/n/4000/)
-to count them all. 4000 is also a Harshad number, which means it’s
-divisible by the sum of its digits (4 + 0 + 0 + 0 = 4). So, in a way,
-our membership is mathematically harmonious! Also, did you know that the
-recent Artemis mission flew approximately [4000 miles above the moon’s
-surface](https://science.nasa.gov/solar-system/skywatching/night-sky-network/night-sky-network-celebrates-artemis-ii/)?
-Okay, you get the point — that’s a lot of RSEs, and we’re thrilled to
-have each and every one of you as part of our community.
-
-So grab a beverage, sit back, and dive in to the latest news and updates
-from your 4000-member-strong community of research software engineers!
+First of all, Happy Pride Month 🌈, and Happy Juneteenth 🎉! We hope you
+are all having a wonderful summer celebrating the diversity and
+resilience of our communities.
+
+It’s been another busy month for US-RSE, as conference planning
+continues to ramp up, membership continues to grow, and the organization
+continues to expand its offerings and impact to the research software
+community. In this issue, we’ll discuss shiny toy syndrome in
+technology, celebrate the LGBTQ+ community, and share all the latest and
+greatest news from US-RSE.
-
+
In this issue:
------------------------------------------------------------------------
-## 🤩 Wait a Minute, I’m an RSE, I Know How to Do That! 🤩
+## 🤔 Arrestive Curiosity & RSEs: How to Turn the Shiny Toy Syndrome Bug into a Feature 🤔
-*I know how to do that!*
-
-It is one of the most rewarding thoughts you can have as a research
-software engineer: that moment when you notice a colleague, PI,
-collaborator, or student struggling with a software problem and realize
-you can help.
-
-Not because they are unmotivated. Not because they are bad scientists.
-But because things are not working, not moving quickly enough, or not
-being recognized for what they are: software problems that can be solved
-with the right tools, techniques, and expertise. Maybe the scientist is
-looking toward industry and thinking, “I wish we could move as quickly
-as Google, Facebook, or Microsoft.” Or, more recently, “I wish we could
-figure out how to really use all this LLM stuff.” Ever persistent, the
-scientist keeps chasing their research questions. They want to discover
-the next big thing in their field. They want to make an impact. But
-because their workflow was essentially written in 2012, and because they
-do not have the time, support, or expertise to modernize it, they are
-stuck moving at the pace of 2012.
-
-And as RSEs, we get it! Code can be fragile — and scary. If a new
-student or postdoc touches it, they might break it. If the code breaks,
-so might every paper, grant, and project built on top of it. When was
-the last time it was updated? Months ago? Years ago? So the scientist
-does not touch it. They treat it like a Rube Goldberg machine: they know
-it works, but they no longer remember how. At this point, they are too
-afraid to find out.
-
-As RSEs, we see this…and get excited.
-
-Because we know how to help. 🥹
-
-I first came across the term “RSE” in the wonderfully cute and
-informative 2019 YouTube video, [The Story of the Research
-Engineer](https://www.youtube.com/watch?v=trAfA9VWLTQ), and I instantly
-fell in love with the idea. Here was a name for the squeaky wheel that
-gets the grease: the person who helps scientists get unstuck, move
-faster, and work more sustainably. But then as now, the field was young.
-There was not much consensus about what an RSE was, where they belonged,
-or how institutions should support them.
-
-The term itself emerged in the UK [in
-2012](https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0),
-after a group of researchers and software practitioners began
-formalizing a role that many people were already doing but few
-institutions knew how to recognize. Since then, definitions have been
-proposed, refined, and debated.
-
-Ian Cosden, one of our newsletter editors and Director of *Research
-Software Engineering for Computational & Data Science* at Princeton,
-defines the role partly by what it is not. An RSE, he argues, is not
-simply a researcher, not simply a facilitator, and not simply a pure
-software engineer. The role lives in the productive space between those
-identities.
-
-
-
-
-
-
-
-Goth et al. ([2025](https://f1000research.com/articles/13-1429)) offer
-one recent attempt to concretize the foundational competencies and
-responsibilities of an RSE, including software development, building and
-distributing software assets, understanding the research lifecycle, and
-supporting reproducible, sustainable research. [Vanessa Sochat’s
-EasyBuild talk](https://www.youtube.com/watch?v=FB2yV8TNnSw), on the
-other hand, emphasizes just how broad this space can be: among roughly
-400 people surveyed who identified themselves to be working on “research
-software” in some capacity, there were more than *190 unique job
-titles*. That degree of diversity can be both a strength and a
-challenge. It shows how widely research software work appears across
-institutions, but it also explains why the role can be so difficult to
-define, hire for, promote, and reward. Another one of our US-RSE
-members, Dan Katz, proposes a 3-dimensional schematic to isolate the
-Super RSE role who commands “a superset of the responsibilities of the
-traditional RSE role, combining both service and the RSE’s own
-research.”
-
-
-
-
-
-
-By identifying this RSE unicorn, Katz highlights the fact that as we
-define the breadth of the scope of the RSE, we also need to think about
-its potentially necessary boundaries.
-
-In a 2022 [career Q&A in
-*Nature*](https://www.nature.com/articles/d41586-022-01516-2), Paul
-Richmond predicted that RSEs could become equals in the academic
-environment if they receive proper recognition for their contributions.
-James Schloss, in his [YouTube
-talk](https://www.youtube.com/watch?v=t2BjZ5hSjHo) highlights some of
-the barriers still standing in the way: the publication economy,
-academic resistance to software engineering best practices, and the
-difficulty of competing with industry salaries for people with similar
-technical expertise. In fact, one of my very first suggestions for
-newsletter topics was to discuss the definition of the title “Research
-Software Engineer” itself, and I was told very firmly to avoid the topic
-as much as possible — not because it was inflammatory, but because it
-remains a particularly sensitive topic. While many are strongly attached
-to the name for its truthiness, just as many others are more concerned
-with defining the tasks, responsibilities, and competencies of the role,
-regardless of what it is called, because funding sources will pay a
-great deal of attention to those details.
-
-But friends, there is hope. 🌱
-
-Just as a small group of concerned scientists and software practitioners
-began with an idea, a conversation, and a Google Group, we can continue
-making the role visible at our own institutions. This can be through
-formal titles, clearer career paths, better credit, stronger communities
-of practice, or simply naming the work when we see it as we help
-research software engineering become easier to recognize and harder to
-ignore. This week, celebrate yourself by encouraging your colleagues,
-coworkers, PIs, and students to **make this role visible**. Look around.
-We are once again watching technology change the fabric of research
-itself. Rigorous science, and the software that powers it, cannot afford
-to be left behind. Now more than ever, research needs talented, driven,
-curious technology specialists who can ask new questions, solve
-impossible bugs, push compute clusters to their limits, and preserve the
-code — and the science — that so many people depend on.
-
-Our Executive Director had this to say about the importance of this
-community:
-
-“Reaching more than 4,000 members is not just a milestone in numbers -
-it reflects a growing community of people who care deeply about
-advancing research through software, collaboration, and support for one
-another. As Executive Director, I am incredibly grateful to be part of
-this community and inspired every day by the generosity, expertise, and
-passion our members bring to US-RSE. Thank you for helping build a place
-where research software engineers can truly belong.”
-
-> [Sandra](https://us-rse.org/about/staff/)
-
-This month, we thank the scrappy and passionate group of researchers who
-helped crystallize the idea of the Research Software Engineer, [one
-quiet afternoon in Oxford, UK, in
-2012](https://www.pure.ed.ac.uk/ws/portalfiles/portal/65195747/DR2012_12_1_.pdf).
-And the next time you notice a colleague struggling with a technical
-problem, be the RSE on their shoulder. Gently remind them:
-
-*Hey, I know how to do that.*
-
-> You are braver than you believe, stronger than you seem, and smarter
-> than you think. A. A. Milne, *Winnie the Pooh*
+This month, I had the pleasure of meeting some fellow R users at the
+Boston R User Group meetup, where I can say I finally felt safe opening
+a conversation with a hot take like, “R is the best,” knowing it would
+likely not spark a flame war. I’m sure many of you having read that
+sentence are already compiling the several counterarguments in your
+head, mashing away your response in a text editor, choosing all your
+best and worst use cases as examples and calling on the greats of your
+respective community to back you up. But this discussion is actually not
+about flame wars; in fact, as I’m sure you’ve experienced, we as
+technologists often care less about what tool is objectively best, and
+more about what tool is best for us, our project, and our team.
+
+And while this can sound like a freeing stance on tooling in general, it
+leaves us with an acute conundrum: how do we know when to *switch*
+tools? When do we know that the tool we’re using is no longer best for
+us, and that we should switch to something else? As computing becomes
+more accessible and capable, more individuals are building tools that
+avow to *finally* and *decisively* solve the problem of \[insert other
+tools’ shortcomings here\]. Indeed, whether it was Markdown’s attempt to
+become the de facto standard for writing on the web Anaconda claim to be
+the last word in environment management for data science, or the eternal
+paradox of Apple’s latest OS somehow always having “the best feature,
+ever,” technology is rife with shiny toys that promise to solve all our
+problems. On the one hand, it can be incredibly overwhelming trying to
+keep up with the latest and greatest, and on the other, you could easily
+risk missing out on a tool that could be a game changer for you and your
+team if you don’t branch out and experiment from time to time.
+
+This decision fatigue can end up being a significant job hazard for
+people who work with technology. What if your organization is one of the
+unfortunate few that decided to go all-in on Skype, or what if you can’t
+ship a new product or publish a paper because your team has not ported
+over its legacy libraries to Python 3 yet? As RSEs, part of our
+responsibility is to help scientific teams navigate this ever-changing
+landscape of tools and technologies, and it can be very tricky to draw
+the line between productive experimentation and [shiny toy
+syndrome](https://nesslabs.com/shiny-toy-syndrome). How does one justify
+several afternoons’ worth of tinkering, only to come to the conclusion
+that the new tool actually *doesn’t* do what it says on the box - or at
+least, not to your satisfaction — and continue to be trusted with the
+responsibility of guiding your team’s technological vision?
+
+But as I thought about this more, I realized that this activity of
+tinkering and experimenting with new tools is actually a critical part
+of our job as RSEs, and that we can turn this “bug” of shiny toy
+syndrome into a “feature” of arrestive curiosity. Arrestive curiosity is
+the tendency to be so curious about new tools and technologies that you
+cannot move forward with your own work until you’ve proven a new tool is
+either better or worse for you than the one you’re currently using (Yes,
+I just came up with that term). If you’ve ever been up late at night
+trying to get a VSCode extension to run without error, trying to figure
+out why a new library can’t just install on your system, or drawing out
+your ultimate note-taking entourage of apps for never losing a thought,
+I see you! This kind of curiosity can be a disastrous time sink — but it
+can also be a powerful way to stay on top of the latest and greatest,
+and to make sure you’re using the best tools for you and your team.
+
+So, how do we cultivate arrestive curiosity without falling into the
+trap of time-wasting? Having wrestled with this for several years, I
+think I can provide a few considerations that have helped me strike this
+balance:
+
+1. *Stop being distracted by the perfect tool until you know what
+ perfect is supposed to look like.* Before seriously investigating a
+ new tool, write down exactly what problem or need you think it is
+ trying to solve for you. In the simple process of articulating this,
+ you may find that your existing workflow just needs some refinement,
+ or a simple adjustment or reframing of the problem. 95% of the time,
+ my tinkering does not pass this step.
+
+2. *Get comfortable with the discomfort of your current tools.* If
+ you’ve successfully passed the first step, then you know for a fact
+ that your current workflow needs are not being met, and a new tool —
+ or repurposing an old one — is likely the solution. But before you
+ dive into the new tool, now is the time to measure the discomfort of
+ your current workflow. How much time are you losing to this problem?
+ How much mental energy are you spending on it? How much is it
+ costing your team in productivity and morale? If the cost of your
+ current workflow is not high enough, then it may not be worth the
+ time and effort to switch to a new tool. If you can tolerate the
+ discomfort, then the tool search ends here.
+
+3. *Refine to absurdum.* If you are still convinced that something is
+ missing, then it is time to start looking for what is missing.
+ Surely someone has felt this acute pain, right? The internet is a
+ vast place, and there are several billion of us using it at any
+ given time. It’s more than likely that someone, somewhere, has been
+ in the exact position you’re in, with an install that is too slow, a
+ link that doesn’t work, or a workflow that is too clunky and just
+ missing that, *secret something*. Go out into dark corners of the
+ second, third, and fourth pages of Google search, ask around on
+ Reddit and Facebook groups, or find forums and communities that are
+ relevant to the problem space. Surely **someone** has faced this
+ problem, too?
+
+4. If the solution is identified, use it. If not, build it. By this
+ point, if you have found a niche problem that 1) arrests your
+ productivity, 2) causes measurable discomfort, and 3) has not been
+ solved by anyone else, then this is a problem worth solving. In
+ fact, as an RSE, this is the *perfect* problem to have, because it
+ is within this narrow gap between your vision and the status quo
+ that you can actually make valuable impact to your team. If you
+ can’t or don’t want to build the solution yourself, one of two
+ things must be true: either the problem is not worth solving, or you
+ are *not yet* the right person to solve it.
+
+In my experience, the really interesting Research Software Engineering
+is what happens when as an engineer I have become *obsessed* with a
+particular technological blocker to the success of my or my colleagues’
+scientific endeavors.
+
+It is the moment we look at the scientific engine and say, “I know we
+*could* just use \[X Tool\] to write this part of the paper, but I just
+can’t accept that this is the best way to do it. I simply can’t. There
+*must* be a better way.”
+
+This is the “arrestive,” part of “arrestive curiosity” — the part that
+keeps you up at night, ceases you in your tracks every time you think
+about it, and continues to consume all of your mental energy until you
+have either found a solution or come to terms with the fact that there
+is no solution.
+
+And if you ask me, that tendency to be obsessed with finding the best
+way to do science is what makes a good RSE a *great* RSE. So, the next
+time you find yourself in the throes of shiny toy syndrome, try to
+channel that energy into arrestive curiosity using the flowchart I
+outlined above, and see where it takes you. You might just find that the
+perfect tool was right in front of you all along, or you might end up
+building something that changes the game for you, your team, and perhaps
+even the science itself.
------------------------------------------------------------------------
@@ -297,7 +277,6 @@ interested in becoming an organizational founding member!
{% for org in site.data.org-members.standard %}
- [{{ org.name }}]({{ org.url }})
-- [Flatiron Institute](https://www.simonsfoundation.org/flatiron/)
{% endfor %}
@@ -314,6 +293,78 @@ interested in becoming an organizational founding member!
+### The Whole Person: Pride and Belonging in US-RSE
+
+Pride Month is both a celebration and a moment for reflection for the
+communities we are part of. As the chairs of the DEI Working Group, we
+welcome everyone to celebrate Pride Month with the US‑RSE community this
+June and beyond. We also want to take a moment to reflect on what Pride
+means to me and how it shapes how we think about belonging in our
+professional communities.
+
+US‑RSE is a community built around shared skills, interests, and goals
+centered on advancing research through software engineering. While that
+core set of interests brings us together, we are also a collection of
+individuals who work across different research domains and parts of the
+software engineering lifecycle. Each person brings unique strengths and
+perspectives.
+
+A mix of viewpoints helps teams generate stronger ideas and advance
+research. That kind of collaboration works best when people feel a sense
+of belonging.
+
+At the same time, we don’t show up to these communities as just “RSEs.”
+Each of us brings life experiences, preferences, and unique quirks. You
+can’t interact with just the “software engineer” side of someone. You
+interact with the whole person, which means accepting them as they are.
+
+That’s where belonging comes from. It’s not just about being part of a
+group with shared interests. It’s about being accepted as you
+are.Creating that kind of belonging can be challenging in practice,
+especially when building trust with people who have experienced bias,
+exclusion, or worse.
+
+That’s why small actions matter. Sharing pronouns, using gender‑neutral
+language, and taking the time to learn about the people around us can
+make a real difference. They signal that people are seen, respected, and
+welcome as part of the community.
+
+For us, Pride is a reminder that this kind of belonging does not happen
+by accident. It is something we create together through everyday
+choices.
+
+Pride means different things to different people. To reflect that range
+of experiences, we invite members of the US‑RSE community to share what
+Pride means to them and how they think about belonging in their work.
+
+What does Pride mean to you? We’d love to hear your perspective. Feel
+free to join the conversation on Slack or share on social media using
+the hashtag `#RSEPride`.
+
+##### Community Contributions
+
+> Research software often involves intensely multidisciplinary
+> collaboration, and, depending on the size of a team, may require the
+> ability to liaise between domains, technical-side, business-side, etc.
+> and advocate whether it’s for data integrity processes or for
+> underweighted voices. In my mind this relational communication and
+> openness is very prosocial and qualitatively close to what Pride is
+> all about; I think it’s why I feel at home in research software and
+> the surrounding communities. – Michael P. Pascale
+
+> I actually did not grow up playing with computers. I always was tech
+> savvy, but never imagined myself opening a terminal or writing code.
+> So when I found myself engaging with technology in research, I was
+> very intimidated, often suffixing all of my conversations with, “but I
+> don’t know anything about this stuff.” That feeling of imposter
+> syndrome went away when I joined the RSE community, and I owe my
+> career success to the culture of support and encouragement that I
+> found here. Celebrating Pride Month with the LGBTQ+ community every
+> year is a reminder of how unconditional acceptance and support enables
+> people to self-actualize and thrive. I stand with my LGBTQ+ allies in
+> celebrating them and advocating for their space in our world! -
+> Tinashe M. Tapera
+
### **Community Shoutouts**
@@ -338,22 +389,32 @@ has taken home this honor!
Read the announcement
[here](https://blog.chameleoncloud.org/posts/sc25-best-reproducibility-advancement-award/).
-### RSE’s with a New York State of Mind… 🗽
+> Did you know that we have a community Code of Conduct? Anyone is able
+> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+
+### In Memoriam
-The NYC Regional Group recently met up for their inaugural in-person
-hangout! Special thanks to Roger Ferger for spearheading the event!
+We mourn the loss of a dear friend and colleague, Cleve Moler, who
+passed away on May 20, 2026, at the age of 86 at his home surrounded by
+his family. Cleve was chief mathematician and cofounder of MathWorks and
+the author of the first version of MATLAB. Please join us in remembering
+their contributions to science and engineering by reading Mathworks
+official announcement
+[here](https://www.mathworks.com/company/aboutus/founders/clevemoler.html).
-
+## Community Spotlight
-
-
+🌱 Our community is full of people doing fascinating research and
+software work, and we want to put a face to it. Starting this month,
+we’ll be featuring a group of different members in a regular spotlight:
+what they work on, a tool they can’t live without, and how they found
+their way into RSE work.
-As an added bonus, the group also now has a dedicated page on the US-RSE
-website! Check it out [here](https://us-rse.org/ag/rg-nyc/) to learn
-more about the group and how to get involved.
+We’d love to feature YOU. It takes about 5 minutes to fill out, and
+nothing gets posted without your okay:
+
-> Did you know that we have a community Code of Conduct? Anyone is able
-> to view it in the `#code_of_conduct` Slack channel, under `Files`!
+Email [Pengyin Shan](mailto:pengyins@illinois.edu) for any questions!
### **Community Calls**
@@ -369,8 +430,8 @@ more about the group and how to get involved.
-->
-Our next meeting is scheduled for Friday, June 12, 2026, 12:00PM EST. We
-hope to see you there!
+Our next meeting is scheduled for Thursday, July 9, 2026, 12:00PM EST.
+We hope to see you there!
------------------------------------------------------------------------
@@ -428,7 +489,7 @@ the `#newsletters` channel!
{% endfor %}
{% endif %}
-{% assign podcasts = refs | where: "type", "motion_picture" %}
+{% assign podcasts = refs | where: "type", "song" %}
{% if podcasts.size > 0 %}
### 🎧 Podcast Episodes
diff --git a/_posts/newsletters/quarto/template.qmd b/_posts/newsletters/quarto/template.qmd
index 9ec816cff..8b1836672 100644
--- a/_posts/newsletters/quarto/template.qmd
+++ b/_posts/newsletters/quarto/template.qmd
@@ -5,22 +5,12 @@ format:
toc: true
toc-depth: 2
number-sections: true
+ include-before-body:
+ - _preamble.md
---
-:::{.content-visible when-meta="sections.preamble"}
-{{< include _preamble.md >}}
-:::
-
-```{=html}
-
-
-
-```
-
-In this issue:
-
--------
:::{.content-visible when-meta="sections.headline"}
diff --git a/_posts/newsletters/quarto/uvr.lock b/_posts/newsletters/quarto/uvr.lock
new file mode 100644
index 000000000..8d808a0d8
--- /dev/null
+++ b/_posts/newsletters/quarto/uvr.lock
@@ -0,0 +1,761 @@
+[r]
+version = "4.5.3"
+
+[[package]]
+name = "AsioHeaders"
+version = "1.30.2-4.1"
+source = "cran"
+raw_version = "1.30.2-1"
+url = "https://cran.r-project.org/src/contrib/AsioHeaders_1.30.2-1.tar.gz"
+checksum = "md5:5c4346bc1746a3b55e0fdf1608460b55"
+
+[[package]]
+name = "DT2"
+version = "0.1.2"
+source = "cran"
+raw_version = "0.1.2"
+url = "https://cran.r-project.org/src/contrib/DT2_0.1.2.tar.gz"
+checksum = "md5:ae46a8319bb392df9d4da40911cfe9d7"
+requires = [
+ "htmlwidgets",
+ "htmltools",
+ "jsonlite",
+ "cli",
+]
+
+[[package]]
+name = "R6"
+version = "2.6.1"
+source = "cran"
+raw_version = "2.6.1"
+url = "https://cran.r-project.org/src/contrib/R6_2.6.1.tar.gz"
+checksum = "md5:f01b1787f12797c29194d63c9afd5d70"
+
+[[package]]
+name = "base64enc"
+version = "0.1.6"
+source = "cran"
+raw_version = "0.1-6"
+url = "https://cran.r-project.org/src/contrib/base64enc_0.1-6.tar.gz"
+checksum = "md5:2c4ecc969451a673ee05eb2e725fcbaf"
+
+[[package]]
+name = "bit"
+version = "4.6.0"
+source = "cran"
+raw_version = "4.6.0"
+url = "https://cran.r-project.org/src/contrib/bit_4.6.0.tar.gz"
+checksum = "md5:f36540550af63b0db8c78429d7366998"
+
+[[package]]
+name = "bit64"
+version = "4.8.2"
+source = "cran"
+raw_version = "4.8.2"
+url = "https://cran.r-project.org/src/contrib/bit64_4.8.2.tar.gz"
+checksum = "md5:12904714853ba84b8d1808266e5ef943"
+requires = ["bit"]
+
+[[package]]
+name = "bslib"
+version = "0.12.0"
+source = "cran"
+raw_version = "0.12.0"
+url = "https://cran.r-project.org/src/contrib/bslib_0.12.0.tar.gz"
+checksum = "md5:4e10d130d9538a635ae123e52b1274bf"
+requires = [
+ "base64enc",
+ "cachem",
+ "fastmap",
+ "htmltools",
+ "jquerylib",
+ "jsonlite",
+ "lifecycle",
+ "memoise",
+ "mime",
+ "rlang",
+ "sass",
+]
+
+[[package]]
+name = "cachem"
+version = "1.1.0"
+source = "cran"
+raw_version = "1.1.0"
+url = "https://cran.r-project.org/src/contrib/cachem_1.1.0.tar.gz"
+checksum = "md5:53980eb40dd09b0cd44673d3a6fabe36"
+requires = [
+ "rlang",
+ "fastmap",
+]
+
+[[package]]
+name = "cli"
+version = "3.6.6"
+source = "cran"
+raw_version = "3.6.6"
+url = "https://cran.r-project.org/src/contrib/cli_3.6.6.tar.gz"
+checksum = "md5:eedc08ba864ae6cd640b05eff1a607ee"
+
+[[package]]
+name = "clipr"
+version = "0.8.1"
+source = "cran"
+raw_version = "0.8.1"
+url = "https://cran.r-project.org/src/contrib/clipr_0.8.1.tar.gz"
+checksum = "md5:e3618a0611ca2dfbc6475975a163ab6a"
+
+[[package]]
+name = "cpp11"
+version = "0.5.5"
+source = "cran"
+raw_version = "0.5.5"
+url = "https://cran.r-project.org/src/contrib/cpp11_0.5.5.tar.gz"
+checksum = "md5:7c4c3f58ffa7adec25b85d0d99c0d7ed"
+
+[[package]]
+name = "crayon"
+version = "1.5.3"
+source = "cran"
+raw_version = "1.5.3"
+url = "https://cran.r-project.org/src/contrib/crayon_1.5.3.tar.gz"
+checksum = "md5:bb290c70d23b2200006187ac7839116f"
+
+[[package]]
+name = "digest"
+version = "0.6.39"
+source = "cran"
+raw_version = "0.6.39"
+url = "https://cran.r-project.org/src/contrib/digest_0.6.39.tar.gz"
+checksum = "md5:2b7268922b0f86dbc8064ff8e3a1ca1b"
+
+[[package]]
+name = "dplyr"
+version = "1.2.1"
+source = "cran"
+raw_version = "1.2.1"
+url = "https://cran.r-project.org/src/contrib/dplyr_1.2.1.tar.gz"
+checksum = "md5:1c6ba2499c7a08d081bdb530423ab22c"
+requires = [
+ "cli",
+ "generics",
+ "glue",
+ "lifecycle",
+ "magrittr",
+ "pillar",
+ "R6",
+ "rlang",
+ "tibble",
+ "tidyselect",
+ "vctrs",
+]
+
+[[package]]
+name = "evaluate"
+version = "1.0.5"
+source = "cran"
+raw_version = "1.0.5"
+url = "https://cran.r-project.org/src/contrib/evaluate_1.0.5.tar.gz"
+checksum = "md5:64d96fee3845fd96d1eafaba37adf00e"
+
+[[package]]
+name = "fastmap"
+version = "1.2.0"
+source = "cran"
+raw_version = "1.2.0"
+url = "https://cran.r-project.org/src/contrib/fastmap_1.2.0.tar.gz"
+checksum = "md5:f53773acd6ba9a86413e8c2dc6441544"
+
+[[package]]
+name = "fontawesome"
+version = "0.5.3"
+source = "cran"
+raw_version = "0.5.3"
+url = "https://cran.r-project.org/src/contrib/fontawesome_0.5.3.tar.gz"
+checksum = "md5:95b072a27418b962792410dfb21c3d2b"
+requires = [
+ "rlang",
+ "htmltools",
+]
+
+[[package]]
+name = "fs"
+version = "2.1.0"
+source = "cran"
+raw_version = "2.1.0"
+url = "https://cran.r-project.org/src/contrib/fs_2.1.0.tar.gz"
+checksum = "md5:6011a5e758c21acc297ed8bbcf97e7d9"
+
+[[package]]
+name = "generics"
+version = "0.1.4"
+source = "cran"
+raw_version = "0.1.4"
+url = "https://cran.r-project.org/src/contrib/generics_0.1.4.tar.gz"
+checksum = "md5:dda54b65216fe3c53571d2adaddc7461"
+
+[[package]]
+name = "glue"
+version = "1.8.1"
+source = "cran"
+raw_version = "1.8.1"
+url = "https://cran.r-project.org/src/contrib/glue_1.8.1.tar.gz"
+checksum = "md5:24e3cd382f52015c929538a5208d11aa"
+
+[[package]]
+name = "here"
+version = "1.0.2"
+source = "cran"
+raw_version = "1.0.2"
+url = "https://cran.r-project.org/src/contrib/here_1.0.2.tar.gz"
+checksum = "md5:d2ff22b1f33c99b75ab3597ef0f79506"
+requires = ["rprojroot"]
+
+[[package]]
+name = "highr"
+version = "0.12.0"
+source = "cran"
+raw_version = "0.12"
+url = "https://cran.r-project.org/src/contrib/highr_0.12.tar.gz"
+checksum = "md5:006fcfa8e16c72ecd1adffdf0cf87e43"
+requires = ["xfun"]
+
+[[package]]
+name = "hms"
+version = "1.1.4"
+source = "cran"
+raw_version = "1.1.4"
+url = "https://cran.r-project.org/src/contrib/hms_1.1.4.tar.gz"
+checksum = "md5:f63240ba5139ec2a20bd1ac56bae8243"
+requires = [
+ "cli",
+ "lifecycle",
+ "pkgconfig",
+ "rlang",
+ "vctrs",
+]
+
+[[package]]
+name = "htmltools"
+version = "0.5.9"
+source = "cran"
+raw_version = "0.5.9"
+url = "https://cran.r-project.org/src/contrib/htmltools_0.5.9.tar.gz"
+checksum = "md5:f4a0cac920fb54b5c5ea94e175e20067"
+requires = [
+ "base64enc",
+ "digest",
+ "fastmap",
+ "rlang",
+]
+
+[[package]]
+name = "htmlwidgets"
+version = "1.6.4"
+source = "cran"
+raw_version = "1.6.4"
+url = "https://cran.r-project.org/src/contrib/htmlwidgets_1.6.4.tar.gz"
+checksum = "md5:e1ea7f9774ad7a79fcf31e52c2074fd1"
+requires = [
+ "htmltools",
+ "jsonlite",
+ "knitr",
+ "rmarkdown",
+ "yaml",
+]
+
+[[package]]
+name = "httpgd"
+version = "2.1.4"
+source = "cran"
+raw_version = "2.1.4"
+url = "https://cran.r-project.org/src/contrib/httpgd_2.1.4.tar.gz"
+checksum = "md5:1413fc3bac1e6c928d697bae90455658"
+requires = [
+ "unigd",
+ "unigd",
+ "cpp11",
+ "AsioHeaders",
+]
+
+[[package]]
+name = "janitor"
+version = "2.2.1"
+source = "cran"
+raw_version = "2.2.1"
+url = "https://cran.r-project.org/src/contrib/janitor_2.2.1.tar.gz"
+checksum = "md5:602dd5f791aa6a7d92bf029e1035d185"
+requires = [
+ "dplyr",
+ "hms",
+ "lifecycle",
+ "lubridate",
+ "magrittr",
+ "purrr",
+ "rlang",
+ "stringi",
+ "stringr",
+ "snakecase",
+ "tidyselect",
+ "tidyr",
+]
+
+[[package]]
+name = "jgd"
+version = "0.1.1"
+source = "cran"
+raw_version = "0.1.1"
+url = "https://cran.r-project.org/src/contrib/jgd_0.1.1.tar.gz"
+checksum = "md5:7a42a98bb3efbc7ed5a6c19383029852"
+
+[[package]]
+name = "jquerylib"
+version = "0.1.4"
+source = "cran"
+raw_version = "0.1.4"
+url = "https://cran.r-project.org/src/contrib/jquerylib_0.1.4.tar.gz"
+checksum = "md5:3607a34ac45ff420bc325d84eab4b0cb"
+requires = ["htmltools"]
+
+[[package]]
+name = "jsonlite"
+version = "2.0.0"
+source = "cran"
+raw_version = "2.0.0"
+url = "https://cran.r-project.org/src/contrib/jsonlite_2.0.0.tar.gz"
+checksum = "md5:3e54e6fbc0c9063936e3d01e91419c14"
+
+[[package]]
+name = "knitr"
+version = "1.51.0"
+source = "cran"
+raw_version = "1.51"
+url = "https://cran.r-project.org/src/contrib/knitr_1.51.tar.gz"
+checksum = "md5:79f32f24b572fe198baca8882d6aa87f"
+requires = [
+ "evaluate",
+ "highr",
+ "xfun",
+ "yaml",
+]
+
+[[package]]
+name = "lifecycle"
+version = "1.0.5"
+source = "cran"
+raw_version = "1.0.5"
+url = "https://cran.r-project.org/src/contrib/lifecycle_1.0.5.tar.gz"
+checksum = "md5:bce35a7a89fe4108f262db3e441cccae"
+requires = [
+ "cli",
+ "rlang",
+]
+
+[[package]]
+name = "lubridate"
+version = "1.9.5"
+source = "cran"
+raw_version = "1.9.5"
+url = "https://cran.r-project.org/src/contrib/lubridate_1.9.5.tar.gz"
+checksum = "md5:09977b7de6710ca05886412c6aa3a5a3"
+requires = [
+ "generics",
+ "timechange",
+]
+
+[[package]]
+name = "magrittr"
+version = "2.0.5"
+source = "cran"
+raw_version = "2.0.5"
+url = "https://cran.r-project.org/src/contrib/magrittr_2.0.5.tar.gz"
+checksum = "md5:4ee23a88bc1589527696d777d7e68dfc"
+
+[[package]]
+name = "memoise"
+version = "2.0.1"
+source = "cran"
+raw_version = "2.0.1"
+url = "https://cran.r-project.org/src/contrib/memoise_2.0.1.tar.gz"
+checksum = "md5:89da4ce771967d851db47132b762ce6f"
+requires = [
+ "rlang",
+ "cachem",
+]
+
+[[package]]
+name = "mime"
+version = "0.13.0"
+source = "cran"
+raw_version = "0.13"
+url = "https://cran.r-project.org/src/contrib/mime_0.13.tar.gz"
+checksum = "md5:45c3868fb2f5a7f3817d54d1c75799f9"
+
+[[package]]
+name = "pillar"
+version = "1.11.1"
+source = "cran"
+raw_version = "1.11.1"
+url = "https://cran.r-project.org/src/contrib/pillar_1.11.1.tar.gz"
+checksum = "md5:eb84af558b1ac0d743a4790e99acad6e"
+requires = [
+ "cli",
+ "glue",
+ "lifecycle",
+ "rlang",
+ "utf8",
+ "vctrs",
+]
+
+[[package]]
+name = "pkgconfig"
+version = "2.0.3"
+source = "cran"
+raw_version = "2.0.3"
+url = "https://cran.r-project.org/src/contrib/pkgconfig_2.0.3.tar.gz"
+checksum = "md5:7b9ca1d45d941238381cb55d13ff4d68"
+
+[[package]]
+name = "prettyunits"
+version = "1.2.0"
+source = "cran"
+raw_version = "1.2.0"
+url = "https://cran.r-project.org/src/contrib/prettyunits_1.2.0.tar.gz"
+checksum = "md5:2e2db8105f214b80d3d4254b8aabb255"
+
+[[package]]
+name = "progress"
+version = "1.2.3"
+source = "cran"
+raw_version = "1.2.3"
+url = "https://cran.r-project.org/src/contrib/progress_1.2.3.tar.gz"
+checksum = "md5:db78636d2dd5ee346f5caf48bfa69f5e"
+requires = [
+ "crayon",
+ "hms",
+ "prettyunits",
+ "R6",
+]
+
+[[package]]
+name = "purrr"
+version = "1.2.2"
+source = "cran"
+raw_version = "1.2.2"
+url = "https://cran.r-project.org/src/contrib/purrr_1.2.2.tar.gz"
+checksum = "md5:1b554060b57fdfe3ba6544c557b0f8d8"
+requires = [
+ "cli",
+ "lifecycle",
+ "magrittr",
+ "rlang",
+ "vctrs",
+ "cli",
+]
+
+[[package]]
+name = "rappdirs"
+version = "0.3.4"
+source = "cran"
+raw_version = "0.3.4"
+url = "https://cran.r-project.org/src/contrib/rappdirs_0.3.4.tar.gz"
+checksum = "md5:a990a3ddcfa9eb422cd406f78084fbd8"
+
+[[package]]
+name = "readr"
+version = "2.2.0"
+source = "cran"
+raw_version = "2.2.0"
+url = "https://cran.r-project.org/src/contrib/readr_2.2.0.tar.gz"
+checksum = "md5:3e87b7c88d9853bb2cec2f11eec2bf72"
+requires = [
+ "cli",
+ "clipr",
+ "crayon",
+ "glue",
+ "hms",
+ "lifecycle",
+ "R6",
+ "rlang",
+ "tibble",
+ "vroom",
+ "withr",
+ "cpp11",
+ "tzdb",
+]
+
+[[package]]
+name = "remotes"
+version = "2.5.0"
+source = "cran"
+raw_version = "2.5.0"
+url = "https://cran.r-project.org/src/contrib/remotes_2.5.0.tar.gz"
+checksum = "md5:4cb0cd9d66630548fedd4e56d3564b90"
+
+[[package]]
+name = "rlang"
+version = "1.3.0"
+source = "cran"
+raw_version = "1.3.0"
+url = "https://cran.r-project.org/src/contrib/rlang_1.3.0.tar.gz"
+checksum = "md5:b52c165e43f4d7fe5cfa15c5c9467ff4"
+
+[[package]]
+name = "rmarkdown"
+version = "2.31.0"
+source = "cran"
+raw_version = "2.31"
+url = "https://cran.r-project.org/src/contrib/rmarkdown_2.31.tar.gz"
+checksum = "md5:8f7a4eef6b62e7f2284550c3134f28c8"
+requires = [
+ "bslib",
+ "evaluate",
+ "fontawesome",
+ "htmltools",
+ "jquerylib",
+ "jsonlite",
+ "knitr",
+ "tinytex",
+ "xfun",
+ "yaml",
+]
+
+[[package]]
+name = "rprojroot"
+version = "2.1.1"
+source = "cran"
+raw_version = "2.1.1"
+url = "https://cran.r-project.org/src/contrib/rprojroot_2.1.1.tar.gz"
+checksum = "md5:307fef4f932acc1d8660a857e44d5fb7"
+
+[[package]]
+name = "sass"
+version = "0.4.10"
+source = "cran"
+raw_version = "0.4.10"
+url = "https://cran.r-project.org/src/contrib/sass_0.4.10.tar.gz"
+checksum = "md5:16054a7117a81ba75893fec17da62209"
+requires = [
+ "fs",
+ "rlang",
+ "htmltools",
+ "R6",
+ "rappdirs",
+]
+
+[[package]]
+name = "snakecase"
+version = "0.11.1"
+source = "cran"
+raw_version = "0.11.1"
+url = "https://cran.r-project.org/src/contrib/snakecase_0.11.1.tar.gz"
+checksum = "md5:3e5cbad0056783cff60d05eb75881f62"
+requires = [
+ "stringr",
+ "stringi",
+]
+
+[[package]]
+name = "stringi"
+version = "1.8.9"
+source = "cran"
+raw_version = "1.8.9"
+url = "https://cran.r-project.org/src/contrib/stringi_1.8.9.tar.gz"
+checksum = "md5:6888a5ac007ad34590ce6afbd0cb2491"
+
+[[package]]
+name = "stringr"
+version = "1.6.0"
+source = "cran"
+raw_version = "1.6.0"
+url = "https://cran.r-project.org/src/contrib/stringr_1.6.0.tar.gz"
+checksum = "md5:e6d638f79f82b1c39fc88e7295ba1c9d"
+requires = [
+ "cli",
+ "glue",
+ "lifecycle",
+ "magrittr",
+ "rlang",
+ "stringi",
+ "vctrs",
+]
+
+[[package]]
+name = "systemfonts"
+version = "1.3.2"
+source = "cran"
+raw_version = "1.3.2"
+url = "https://cran.r-project.org/src/contrib/systemfonts_1.3.2.tar.gz"
+checksum = "md5:57b95280ca9bba2bb18477eb512ac971"
+requires = [
+ "base64enc",
+ "jsonlite",
+ "lifecycle",
+ "cpp11",
+]
+
+[[package]]
+name = "tibble"
+version = "3.3.1"
+source = "cran"
+raw_version = "3.3.1"
+url = "https://cran.r-project.org/src/contrib/tibble_3.3.1.tar.gz"
+checksum = "md5:97ff25ebdd1460ec152d48e9bb54fa43"
+requires = [
+ "cli",
+ "lifecycle",
+ "magrittr",
+ "pillar",
+ "pkgconfig",
+ "rlang",
+ "vctrs",
+]
+
+[[package]]
+name = "tidyr"
+version = "1.3.2"
+source = "cran"
+raw_version = "1.3.2"
+url = "https://cran.r-project.org/src/contrib/tidyr_1.3.2.tar.gz"
+checksum = "md5:f8e976221d4ed9092c734cf86abcdba9"
+requires = [
+ "cli",
+ "dplyr",
+ "glue",
+ "lifecycle",
+ "magrittr",
+ "purrr",
+ "rlang",
+ "stringr",
+ "tibble",
+ "tidyselect",
+ "vctrs",
+ "cpp11",
+]
+
+[[package]]
+name = "tidyselect"
+version = "1.2.1"
+source = "cran"
+raw_version = "1.2.1"
+url = "https://cran.r-project.org/src/contrib/tidyselect_1.2.1.tar.gz"
+checksum = "md5:49c581292e819a2a39aac321f27ab0a8"
+requires = [
+ "cli",
+ "glue",
+ "lifecycle",
+ "rlang",
+ "vctrs",
+ "withr",
+]
+
+[[package]]
+name = "timechange"
+version = "0.4.0"
+source = "cran"
+raw_version = "0.4.0"
+url = "https://cran.r-project.org/src/contrib/timechange_0.4.0.tar.gz"
+checksum = "md5:4cabacecbed68e3beb00e47d42fc9fca"
+requires = ["cpp11"]
+
+[[package]]
+name = "tinytex"
+version = "0.60.0"
+source = "cran"
+raw_version = "0.60"
+url = "https://cran.r-project.org/src/contrib/tinytex_0.60.tar.gz"
+checksum = "md5:c680dc21cfd948a22a4f72427967e3e0"
+requires = ["xfun"]
+
+[[package]]
+name = "tzdb"
+version = "0.5.0"
+source = "cran"
+raw_version = "0.5.0"
+url = "https://cran.r-project.org/src/contrib/tzdb_0.5.0.tar.gz"
+checksum = "md5:a9f89aa8a851f7a2a13856e815c8bb1c"
+requires = ["cpp11"]
+
+[[package]]
+name = "unigd"
+version = "0.2.0"
+source = "cran"
+raw_version = "0.2.0"
+url = "https://cran.r-project.org/src/contrib/unigd_0.2.0.tar.gz"
+checksum = "md5:b175ff191262e858e7e0d16dbb8ec32b"
+requires = [
+ "systemfonts",
+ "cpp11",
+ "systemfonts",
+]
+
+[[package]]
+name = "utf8"
+version = "1.2.6"
+source = "cran"
+raw_version = "1.2.6"
+url = "https://cran.r-project.org/src/contrib/utf8_1.2.6.tar.gz"
+checksum = "md5:12037c186ddded4d9b289762b69fc435"
+
+[[package]]
+name = "vctrs"
+version = "0.7.3"
+source = "cran"
+raw_version = "0.7.3"
+url = "https://cran.r-project.org/src/contrib/vctrs_0.7.3.tar.gz"
+checksum = "md5:d99218820f353c359ff59fd46b52ddb3"
+requires = [
+ "cli",
+ "glue",
+ "lifecycle",
+ "rlang",
+]
+
+[[package]]
+name = "vroom"
+version = "1.7.1"
+source = "cran"
+raw_version = "1.7.1"
+url = "https://cran.r-project.org/src/contrib/vroom_1.7.1.tar.gz"
+checksum = "md5:68e4cfa008bd830c7f6f47b26a1cff0e"
+requires = [
+ "bit64",
+ "cli",
+ "crayon",
+ "glue",
+ "hms",
+ "lifecycle",
+ "rlang",
+ "tibble",
+ "tidyselect",
+ "tzdb",
+ "vctrs",
+ "withr",
+ "cpp11",
+ "progress",
+ "tzdb",
+]
+
+[[package]]
+name = "withr"
+version = "3.0.3"
+source = "cran"
+raw_version = "3.0.3"
+url = "https://cran.r-project.org/src/contrib/withr_3.0.3.tar.gz"
+checksum = "md5:121bf3699aadb9d1b47d648964b934f8"
+
+[[package]]
+name = "xfun"
+version = "0.60.0"
+source = "cran"
+raw_version = "0.60"
+url = "https://cran.r-project.org/src/contrib/xfun_0.60.tar.gz"
+checksum = "md5:1bea9ab58602d9b6eac3b5823a95e5e6"
+
+[[package]]
+name = "yaml"
+version = "2.3.12"
+source = "cran"
+raw_version = "2.3.12"
+url = "https://cran.r-project.org/src/contrib/yaml_2.3.12.tar.gz"
+checksum = "md5:6beea9b09717960f6c79fcbc1e129c41"
diff --git a/_posts/newsletters/quarto/uvr.toml b/_posts/newsletters/quarto/uvr.toml
new file mode 100644
index 000000000..8d3105c29
--- /dev/null
+++ b/_posts/newsletters/quarto/uvr.toml
@@ -0,0 +1,14 @@
+[project]
+name = "quarto"
+
+[dependencies]
+DT2 = "*"
+dplyr = "*"
+fs = "*"
+here = "*"
+httpgd = "*"
+janitor = "*"
+jgd = "*"
+readr = "*"
+remotes = "*"
+yaml = "*"
diff --git a/_posts/newsletters/render_new_edition.sh b/_posts/newsletters/render_new_edition.sh
deleted file mode 100755
index 6a75bd772..000000000
--- a/_posts/newsletters/render_new_edition.sh
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/bash
-set -euo pipefail
-
-qmd_file="$1" # input quarto template
-file_in="$2" # intermediate template file from quarto render (markdown without yaml frontmatter)
-file_out="$3" # final output file (markdown post with yaml frontmatter)
-yaml_file="$4" # newsletter parameters
-
-# render quarto to template
-quarto render "$qmd_file" --metadata-file "$yaml_file"
-
-# convert Interesting Reads bib to yaml
-pandoc _data/newsletter_bib.bib -s -f biblatex -t markdown > _data/newsletter_bib_yml.yml
-
-# copy yaml frontmatter into rendered quarto output
-tmp=$(mktemp)
-
-{
- echo "---"
- cat "$yaml_file"
- echo "---"
- sed '1,4d' "$file_in"
-} > "$tmp"
-
-mv "$tmp" "$file_out"
\ No newline at end of file
From 7fa6e636fa2947fd8ea84926a278a4b7571a2ff5 Mon Sep 17 00:00:00 2001
From: TinasheMTapera <15770644+TinasheMTapera@users.noreply.github.com>
Date: Fri, 7 Aug 2026 15:28:23 -0400
Subject: [PATCH 04/11] fix citations htmls
---
_data/newsletter/usrse.bib | 9 +
_data/newsletter_bib.bib | 294 +++++++++++++-----
_includes/citation-article.html | 104 +++++++
_includes/citation-blog.html | 52 ++++
_includes/citation-media.html | 54 ++++
_posts/newsletters/2026-08-05-newsletter.md | 8 +-
.../product-school-nOvIa_x_tfo-unsplash.jpg | Bin 0 -> 3252115 bytes
7 files changed, 443 insertions(+), 78 deletions(-)
create mode 100644 _includes/citation-article.html
create mode 100644 _includes/citation-blog.html
create mode 100644 _includes/citation-media.html
create mode 100644 assets/img/newsletter-202608/product-school-nOvIa_x_tfo-unsplash.jpg
diff --git a/_data/newsletter/usrse.bib b/_data/newsletter/usrse.bib
index a14e31db6..bc38b78d4 100644
--- a/_data/newsletter/usrse.bib
+++ b/_data/newsletter/usrse.bib
@@ -660,6 +660,15 @@ @article{posadaOakRidgeComputing2026
Read\_Status\_Date: 2026-06-15T23:59:08.721Z}
}
+@article{powellBridgingDecisionProblems,
+ title = {Bridging {{Decision Problems}}},
+ author = {Powell, Warren B},
+ langid = {english},
+ annotation = {Read\_Status: New\\
+Read\_Status\_Date: 2026-08-07T17:24:11.532Z},
+ file = {/Users/tit420/Zotero/storage/4QKQFL86/Powell - Bridging Decision Problems.pdf}
+}
+
@book{ramanathanIntroductionNeuromorphicComputing2025,
title = {Introduction to {{Neuromorphic Computing}}},
author = {Ramanathan, Shriram and Sengupta, Abhronil},
diff --git a/_data/newsletter_bib.bib b/_data/newsletter_bib.bib
index d7f0254a8..bc38b78d4 100644
--- a/_data/newsletter_bib.bib
+++ b/_data/newsletter_bib.bib
@@ -4,7 +4,7 @@ @article{armstrongCharacterizingSecurityCulture2026
author = {Armstrong, Matthew and Carver, Jeffrey C. and Milewicz, Reed and Meinel, Michael and Felderer, Michael},
date = {2026-10},
journaltitle = {Future Generation Computer Systems},
- shortjournal = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
volume = {183},
pages = {108571},
issn = {0167739X},
@@ -12,8 +12,8 @@ @article{armstrongCharacterizingSecurityCulture2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002050},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{armstrongPreparingResearchSoftware2026,
@@ -22,7 +22,7 @@ @article{armstrongPreparingResearchSoftware2026
author = {Armstrong, Matthew and Carver, Jeffrey C. and Milewicz, Reed},
date = {2026-10},
journaltitle = {Future Generation Computer Systems},
- shortjournal = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
volume = {183},
pages = {108572},
issn = {0167739X},
@@ -30,8 +30,8 @@ @article{armstrongPreparingResearchSoftware2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002062},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@report{barkerResearchSoftwareEngineering2026,
@@ -45,8 +45,8 @@ @report{barkerResearchSoftwareEngineering2026
urldate = {2026-05-28},
abstract = {The Research Software Engineering in the Age of Generative AI: Building a Community Vision workshop, held in March in Edinburgh, UK, brought together participants to explore how Generative AI may reshape the research software ecosystem, and to help inform a broader community vision for the future of the field.~ Before the workshop, attendees contributed to a draft vision statement that workshop organisers used to identify areas of agreement and difference. A version of this, published as Research Software in an Age of AI-Assisted Development: Reflections from Edinburgh, is intended to provide principles that will guide the community during this time of rapid change. In the workshop, the participants also discussed emerging practices, identified opportunities and risks, and proposed a range of high-impact pilot activities to support the safe, reproducible, and effective use of AI in research software and workflows. The areas focused on included: Suggesting policies and narratives for research-performing institutions Developing a framework to discover, document and address costs, benefits, and risks Understanding future incentives around publishing, preserving and crediting software Verifying and validating research software Defining pathways for the evolution of the research software engineers (RSE) role Identifying and developing necessary training Developing a playbook for RSE managers and open-source software project leaders Making GenAI accessible to all Collaborating together across people, community, and disciplines, not just with AI Across these areas, participants identified 46 different activities, ranging from writing sprints and community-of-practice activities that could begin soon, to longer-term research studies to investigate how verification practices, collaboration patterns, and training needs are changing as AI tools become embedded in research workflows. These projects shared a common focus on community-maintained practices, actionable guidance, and sustained coordination.},
keywords = {community,generative AI,research software,research software engineering},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/9GNVA3UV/Barker et al. - 2026 - Research Software Engineering in the Age of Generative AI Building a Community Vision.pdf}
}
@@ -72,19 +72,17 @@ @online{bortVCBignameProgrammers2026
Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
}
-@video{ByteSizedCreateYour2026,
- entrysubtype = {video},
+@audio{ByteSizedCreateYour2026,
title = {[{{EN}}] {{ByteSized}}: Create Your Web-Site with {{GitHub Pages}} - {{J Cohen}}, {{S Gibson}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{ByteSized}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-05-19},
url = {https://www.buzzsprout.com/1326658/episodes/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson},
urldate = {2026-05-21},
abstract = {English Edition:\ In this ByteSized episode \& online class we're talking about GitHub Pages and how it can help you to create a web-site for your research project (reasonably) quickly. With me are Sarah Gibson and Jeremy Cohen.\ I'd li...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.411Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/2EWWF4FT/19133793-en-bytesized-create-your-web-site-with-github-pages-j-cohen-s-gibson.html}
}
@@ -93,14 +91,15 @@ @article{carverSustainingResearchSoftware2021
author = {Carver, Jeffrey C. and Cosden, Ian A. and Hill, Chris and Gesing, Sandra and Katz, Daniel S.},
date = {2021-06},
journaltitle = {2021 IEEE/ACM International Workshop on Body of Knowledge for Software Sustainability (BoKSS)},
+ shortjournal = {2021 IEEEACM Int. Workshop Body Knowl. Softw. Sustain. BoKSS},
pages = {23--24},
doi = {10.1109/BoKSS52540.2021.00016},
url = {https://ieeexplore.ieee.org/document/9470770},
urldate = {2026-05-21},
abstract = {Research software is a class of software developed to support research. Today a wealth of such software is created daily in universities, government, and commercial research enterprises worldwide. The sustainability of this software faces particular challenges due, at least in part, to the type of people who develop it. These Research Software Engineers (RSEs) face challenges in developing and sustaining software that differ from those faced by the developers of traditional software. As a result, professional associations have begun to provide support, advocacy, and resources for RSEs. These benefits are critical to sustaining RSEs, especially in environments where their contributions are often undervalued and not rewarded. This paper focuses on how professional associations, such as the United States Research Software Engineer Association (US-RSE), can provide this support.},
keywords = {career paths,Conferences,Faces,Government,Knowledge engineering,people,research software,Software,software sustainability,Sustainable development},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/MBQI2WMD/Carver et al. - 2021 - Sustaining Research Software via Research Software Engineers and Professional Associations.pdf;/Users/tit420/Zotero/storage/PETA3B2D/9470770.html}
}
@@ -147,7 +146,7 @@ @article{chugunovaWhoUsesAI2026
author = {Chugunova, Marina and Harhoff, Dietmar and Hölzle, Katharina and Kaschub, Verena and Malagimani, Sonal and Morgalla, Ulrike and Rose, Robert},
date = {2026-03-01},
journaltitle = {Research Policy},
- shortjournal = {Research Policy},
+ shortjournal = {Res. Policy},
volume = {55},
number = {2},
pages = {105381},
@@ -185,19 +184,30 @@ @online{claburnGitHubWeGoing
Read\_Status\_Date: 2026-05-21T02:36:15.500Z}
}
-@video{ComputingNotYou2026,
+@video{clusterraBioChemreadySlurmCluster2026,
entrysubtype = {video},
+ title = {{{BioChem-ready}} {{Slurm Cluster}} in Minutes — {{Clusterra Walkthrough}}},
+ namea = {{Clusterra}},
+ nameatype = {collaborator},
+ date = {2026-04-25},
+ url = {https://www.youtube.com/watch?v=a1-GGm3tAbI},
+ urldate = {2026-06-29},
+ abstract = {A 1:49 walkthrough of the Clusterra console: from an empty AWS account to a running Slurm cluster, a submitted job, and a live JupyterLab notebook — all in your own AWS, same day.},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:29:59.361Z}
+}
+
+@audio{ComputingNotYou2026,
title = {[{{EN}}] {{Computing}}, but Not as You Know It: {{Field Programmable Gate Arrays}} ({{FPGA}}) - with {{Michael McLeod}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{Computing}}, but Not as You Know It},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-05-05},
url = {https://www.buzzsprout.com/1326658/episodes/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-mcleod},
urldate = {2026-05-21},
abstract = {English Edition: In a follow up about "unusual" computers I want to focus on field programmable gate arrays - FPGAs. With my guest and former colleague at UCL, Michael McLeod, we talk about what they are, where they are used and what's so special ...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/HFYACMW9/19019174-en-computing-but-not-as-you-know-it-field-programmable-gate-arrays-fpga-with-michael-m.html}
}
@@ -207,7 +217,7 @@ @article{cosdenDesigningImplementingComprehensive2026
author = {Cosden, Ian A. and Holtz, Elizabeth and Bretheim, Joel U.},
date = {2026-10},
journaltitle = {Future Generation Computer Systems},
- shortjournal = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
volume = {183},
pages = {108574},
issn = {0167739X},
@@ -215,8 +225,20 @@ @article{cosdenDesigningImplementingComprehensive2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002086},
urldate = {2026-05-21},
langid = {english},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
+}
+
+@online{CrankGPTLocalHumanpowered,
+ title = {{{CrankGPT}} — {{Local Human-powered AI}}},
+ author = {Squeez Labs},
+ url = {https://crankgpt.com/},
+ urldate = {2026-06-16},
+ abstract = {A human-powered, fully local, fully private AI solution.},
+ langid = {english},
annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.963Z}
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/QGJ3I4WD/crankgpt.com.html}
}
@article{crouchSoftwareSustainabilityInstitute2013,
@@ -225,6 +247,7 @@ @article{crouchSoftwareSustainabilityInstitute2013
author = {Crouch, Stephen and Hong, Neil Chue and Hettrick, Simon and Jackson, Mike and Pawlik, Aleksandra and Sufi, Shoaib and Carr, Les and De Roure, David and Goble, Carole and Parsons, Mark},
date = {2013-11},
journaltitle = {Computing in Science \& Engineering},
+ shortjournal = {Comput. Sci. Eng.},
volume = {15},
number = {6},
pages = {74--80},
@@ -234,8 +257,8 @@ @article{crouchSoftwareSustainabilityInstitute2013
urldate = {2026-05-21},
abstract = {To effect change, the Software Sustainability Institute works with researchers, developers, funders, and infrastructure providers to identify and address key issues with research software.},
keywords = {domain engineering,Domain engineering,maintainability,Programming,reliability,scientific computing,Scientific computing,Software development,software engineering,Software engineering,Software reliability,Training},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/ALBPHA5I/6731384.html}
}
@@ -264,6 +287,34 @@ @article{dicosmoStopTreatingCode2025
file = {/Users/tit420/Zotero/storage/ZDISSPC7/d41586-025-03196-0.html}
}
+@audio{DoesSpecDrivenDevelopment2026,
+ title = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile? {{With Graham Lee}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{Does Spec-Driven Development}} Replace Agile?},
+ author = {Schmidt, Peter},
+ date = {2026-06-02},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee},
+ urldate = {2026-06-16},
+ abstract = {English Edition: Will spec-driven development replace agile processes? My guest Graham Lee\ (https://chironcodex.com/ ) and I discuss if there is still a place for agile software engineering in a world of AI assisted coding.Links:https://mart...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/QWCZ298A/19163979-en-does-spec-driven-development-replace-agile-with-graham-lee.html}
+}
+
+@online{DozensAmericasLargest2026,
+ title = {Dozens of {{America}}'s Largest Companies Have No Simple Way to Report Security Flaws},
+ author = {Whittaker, Zach},
+ date = {2026-06-19T12:00:34},
+ url = {https://this.weekinsecurity.com/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws/},
+ urldate = {2026-06-29},
+ abstract = {New analysis shows that around one-third of America's Fortune 100 companies do not have a vulnerability disclosure policy, bug bounty, or a dedicated email address for reporting security flaws.},
+ langid = {english},
+ organization = {\textasciitilde this week in security\textasciitilde},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-29T15:31:33.542Z},
+ file = {/Users/tit420/Zotero/storage/X3RV4UQU/dozens-of-americas-largest-companies-have-no-simple-way-to-report-security-flaws.html}
+}
+
@report{druskatResearchSoftwareEngineers2026,
title = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}: {{Same Value}}, {{Changing Practice}}},
shorttitle = {Research {{Software Engineers}} in the {{Age}} of {{GenAI}}},
@@ -276,8 +327,8 @@ @report{druskatResearchSoftwareEngineers2026
abstract = {Research software and its creators have long played a critical role in the advancement of research worldwide. This role is changing in the age of “generative AI” (GenAI), but both the software and the people remain of key importance. Understanding these changes is essential in enabling Research Software Engineers (RSEs) to continue contributing the same high value to the research process and its outputs.~ Before GenAI, the RSE movement had learned to clearly articulate the value proposition of embedding expert software engineering in research to its stakeholders. This blog post highlights how RSEs use GenAI to increase their capacity in both software engineering and research, and visualize this evolution. While GenAI is changing - perhaps considerably - how RSEs work in practice, their value and the value of their work for research remains steady and likely to increase.},
langid = {english},
keywords = {GenAI,Research,Research software,Research software engineers},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/UY727H52/Druskat et al. - 2026 - Research Software Engineers in the Age of GenAI Same Value, Changing Practice.pdf}
}
@@ -333,6 +384,7 @@ @article{hasselbringTechnologyResearchSoftware2026
author = {Hasselbring, Wilhelm and Katz, Daniel S. and family=Nieuwpoort, given=Rob, prefix=van, useprefix=true},
date = {2026-01},
journaltitle = {Computing in Science \& Engineering},
+ shortjournal = {Comput. Sci. Eng.},
volume = {28},
number = {1},
pages = {94--99},
@@ -342,8 +394,8 @@ @article{hasselbringTechnologyResearchSoftware2026
urldate = {2026-05-28},
abstract = {Research software has been categorized for various goals. One fundamental dimension of such categorizations is the role that the software plays in the research process. Recently, a new role category has emerged: technology research software, which covers research software developed in technology research. Until now, this category of technology research software has often been overlooked and neglected within the research software engineering community. In this article, we explain technology research software and its primary subroles. Technology readiness levels are an established method of estimating the maturity of technologies, including software systems. For technology research software, these readiness levels define secondary subroles. To illustrate the concept of technology research software and to make it more tangible, we present examples of research software that, depending on its specific use within or outside of research, take on the role of technology research software as well as that of another research software category.},
keywords = {Research and development,Software development management,Technology planning},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/6BSWQ8MR/Hasselbring et al. - 2026 - Technology Research Software An Often Overlooked Category of Research Software.pdf;/Users/tit420/Zotero/storage/2UK2DMNQ/11482008.html}
}
@@ -352,6 +404,7 @@ @article{kaiserProbabilisticComputingPbits2021
author = {Kaiser, Jan and Datta, Supriyo},
date = {2021-10-11},
journaltitle = {Applied Physics Letters},
+ shortjournal = {Appl. Phys. Lett.},
volume = {119},
number = {15},
eprint = {2108.09836},
@@ -376,8 +429,8 @@ @article{kamaliCommunitySoftwareFacility
url = {https://opensky.ucar.edu/islandora/object/technotes%3A45415},
urldate = {2026-05-28},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/UDUNTTC9/Kamali et al. - Community Software Facility Discovery Workshop Report Scientific software best practices, tools, an.pdf}
}
@@ -392,8 +445,8 @@ @report{katzResearchSoftwareAge2026
urldate = {2026-05-28},
abstract = {Important: This document began as a draft vision statement prepared in advance of the “Research Software Engineering in the Age of Generative AI” workshop, March 2026. It was intended to lead to discussion in the document before and discussion in-person at the workshop, including disagreement, and refinement. The current version of the document is a snapshot of that draft vision statement and some of the discussion. It captures a sense of the identified principles, benefits, challenges, and open questions, rather than having a single point of view that represents all of the workshop attendees and contributors. Not all authors necessarily agree with all the points in the document. A note on terminology: We use AI-assisted software development throughout this document to refer to tools and practices often described as Generative AI, GenAI, LLM-enabled development, or AI-assisted coding. We chose this term because it focuses on the activity we care about here, namely the production, verification, documentation, and maintenance of research software, rather than on a particular technology label or marketing category. Research software, the source code, scripts, computational workflows, and infrastructure that power modern research, have never been more central to human discovery. And the scholarly community (funders, publishers, societies, etc.) increasingly recognizes this, though there is still a long way to go before such recognition is widespread or leads to systemic change. At the same time, in the last few years, the rise of AI-assisted tools, i.e., those that can generate code and documentation by using large language and multimodal trained models, and act in semi-autonomous “agentic modes,” has caused significant disruption in software creation and society at large. These tools raise legitimate questions about training data provenance, licensing, quality, security, attribution, environmental cost, and accountability that are hard to ignore. Yet the conversation around AI-assisted tools too often seems to oscillate between hype and dystopian predictions. Neither of these extremes serve research well. This document also starts from the assumption that these tools are and will continue to be used, regardless of the concerns raised above, and aims to guide further usage within this context. This document outlines some ideas about how research software can and should be produced in the era of AI-assisted research tools by Research Software Engineers, computational researchers, and domain experts writing their own code. It focuses on the software production function: building and maintaining software that meaningfully advances research, but also includes the people involved. Workshop participants discussed both, including the role of RSEs and how it will change, such as leveraging the ADSA/USE-RSE-led Position Statement on Generative AI in the RSE Workplace and related work in this space. We believe that developing a shared vision of the future of research software is urgent: AI tools act as an amplifier of existing practices at every level: individual coding habits, institutional incentives, and the commercial priorities of the companies building these tools – accelerating whatever patterns they encounter, both good and bad. Applied without thought, AI-assisted tools can proliferate bugs, embed and reinforce biases, and generate plausible-looking results faster than our existing systems of peer review and verification can check and absorb them. Applied with care and discipline, it has the potential to expand access to computational methods from those with software development skills to those without them, at least for those who can afford it, and allow all researchers to focus on the work that most requires human skill and judgment.},
keywords = {generative AI,research software,research software engineering},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.904Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/MABEB35L/Katz et al. - 2026 - Research Software in an Age of AI-Assisted Development Reflections from Edinburgh.pdf}
}
@@ -406,23 +459,50 @@ @online{KindofBriefShared00:00:00+0000
abstract = {United States Research Software Engineer Association},
langid = {english},
organization = {US-RSE},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/DS3WJMXT/2022-02-06-a-brief-history-of-usrse.html}
}
-@video{ManagingPackagesPixi2026,
- entrysubtype = {video},
+@online{LeidenDeclarationArtificial2026,
+ title = {Leiden {{Declaration}} on {{Artificial Intelligence}} and {{Mathematics}}},
+ author = {{International Mathematical Union}},
+ date = {2026-08-05},
+ url = {https://leidendeclaration.ai/},
+ urldate = {2026-08-06},
+ abstract = {This declaration calls for action to address the challenges posed by the use of artificial intelligence within mathematics research.},
+ langid = {english},
+ organization = {Leiden Declaration on Artificial Intelligence and Mathematics},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-08-06T02:57:47.352Z},
+ file = {/Users/tit420/Zotero/storage/8SY8H9LJ/leidendeclaration.ai.html}
+}
+
+@online{macdonaldSTAMPEDPrinciplesReproducible2026,
+ title = {{{STAMPED}} Principles for Reproducible Research Objects},
+ author = {Macdonald, Austin and Baker, Cody and To, Isaac and Halchenko, Yaroslav O},
+ date = {2026-05-26},
+ number = {f3h82\_v1},
+ url = {https://osf.io/preprints/metaarxiv/f3h82_v1/},
+ urldate = {2026-06-15},
+ abstract = {Scientific claims increasingly rely upon the interplay of code, data, and computational environments. Yet the record of how they are used together is often incomplete, scattered, or lost. This undermines rigor, reproducibility, reusability, and efficiency. Previous approaches have improved the governance of digital objects but do not specify how research objects ought to be structured and managed so they can be re-executed and extended. The community is missing a shared vocabulary for this operational layer. Building on recurrent practices and convergent patterns across disciplines, we formalize seven principles: Self-containment, Tracking, Actionability, Modularity, Portability, Ephemerality, and Distributability (STAMPED). Together they give researchers guidelines for building and assessing research objects that others can trust, rerun, and build upon. We frame each principle as a spectrum so that adoption is incremental and starts from existing practice. We support each principle with normative requirements, an interactive checklist, and a map of enabling tools. As conventions mature, tooling improves, and AI agents become increasingly involved in research workflows, the goals of rigor, reproducibility, reusability, and efficiency are becoming more attainable. STAMPED gives researchers, collaborators, reviewers, and agents a common language, concrete goals, and an aligned direction for making computational research more durable. https://github.com/stamped-principles/stamped-paper/},
+ pubstate = {prepublished},
+ keywords = {open science,provenance,reproducibility,research objects},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.126Z},
+ file = {/Users/tit420/Zotero/storage/TJ2BGX9N/Macdonald et al. - 2026 - STAMPED principles for reproducible research objects.pdf}
+}
+
+@audio{ManagingPackagesPixi2026,
title = {[{{EN}}] {{Managing Packages}} with {{Pixi}} - {{Raniere}} de {{Silva}} and {{Wolf Vollprecht}} - {{Code}} for {{Thought}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-05-12},
url = {https://www.buzzsprout.com/1326658/episodes/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht},
urldate = {2026-05-21},
abstract = {English Edition:\ there is a (relatively) new kid on the block - of open source package managers. It's called Pixi: and in this episode I talk to Raniere de Silva (GESIS) and Wolf Vollprecht (Prefix - the company behind Pixi), what the tool br...},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/8C38H95J/19064274-en-managing-packages-with-pixi-raniere-de-silva-and-wolf-vollprecht.html}
}
@@ -431,8 +511,8 @@ @online{ManagingResearchSoftware
author = {Wilson, Greg},
url = {https://third-bit.com/mrsp/},
urldate = {2026-05-28},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-28T20:09:36.905Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z},
file = {/Users/tit420/Zotero/storage/GKTHZ5R8/mrsp.html}
}
@@ -441,7 +521,7 @@ @article{martinaEmpiricalEvaluationLLMs2026
author = {Martina, Tobia and Saad, Motaz and Rucco, Chiara and Longo, Antonella},
date = {2026-10},
journaltitle = {Future Generation Computer Systems},
- shortjournal = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
volume = {183},
pages = {108587},
issn = {0167739X},
@@ -449,8 +529,8 @@ @article{martinaEmpiricalEvaluationLLMs2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26002219},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.962Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{mcmahonPhysicsOpticalComputing2023,
@@ -458,7 +538,7 @@ @article{mcmahonPhysicsOpticalComputing2023
author = {McMahon, Peter L.},
date = {2023-10-09},
journaltitle = {Nature Reviews Physics},
- shortjournal = {Nat Rev Phys},
+ shortjournal = {Nat. Rev. Phys.},
volume = {5},
number = {12},
eprint = {2308.00088},
@@ -484,16 +564,16 @@ @book{millerIntroductionSoftwareSecurity
isbn = {9798195700508},
langid = {english},
pagetotal = {390},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z}
}
@article{mineaultGoodResearchCode,
title = {Good {{Research Code}} Handbook},
author = {Mineault, Patrick},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.412Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/VN9MWNVD/Mineault - Good Research Code handbook.pdf}
}
@@ -524,8 +604,8 @@ @online{NotsobriefHistoryResearch
author = {Hettrick, Simon},
url = {https://www.software.ac.uk/blog/not-so-brief-history-research-software-engineers-0},
urldate = {2026-05-21},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T03:25:52.413Z},
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.722Z},
file = {/Users/tit420/Zotero/storage/QJB9WWQZ/not-so-brief-history-research-software-engineers-0.html}
}
@@ -545,7 +625,7 @@ @article{PhysicsNeedsResearch2025
title = {Physics Needs Research Software Engineers},
date = {2025-07},
journaltitle = {Nature Reviews Physics},
- shortjournal = {Nat Rev Phys},
+ shortjournal = {Nat. Rev. Phys.},
volume = {7},
number = {7},
pages = {349--349},
@@ -568,7 +648,7 @@ @article{posadaOakRidgeComputing2026
author = {Posada, Edwin F. and Holmen, John K. and Rentschler, Asa},
date = {2026-09},
journaltitle = {Future Generation Computer Systems},
- shortjournal = {Future Generation Computer Systems},
+ shortjournal = {Future Gener. Comput. Syst.},
volume = {182},
pages = {108513},
issn = {0167739X},
@@ -576,8 +656,17 @@ @article{posadaOakRidgeComputing2026
url = {https://linkinghub.elsevier.com/retrieve/pii/S0167739X26001470},
urldate = {2026-05-21},
langid = {english},
- annotation = {Read\_Status: To Read\\
-Read\_Status\_Date: 2026-05-21T23:31:57.962Z}
+ annotation = {Read\_Status: Read\\
+Read\_Status\_Date: 2026-06-15T23:59:08.721Z}
+}
+
+@article{powellBridgingDecisionProblems,
+ title = {Bridging {{Decision Problems}}},
+ author = {Powell, Warren B},
+ langid = {english},
+ annotation = {Read\_Status: New\\
+Read\_Status\_Date: 2026-08-07T17:24:11.532Z},
+ file = {/Users/tit420/Zotero/storage/4QKQFL86/Powell - Bridging Decision Problems.pdf}
}
@book{ramanathanIntroductionNeuromorphicComputing2025,
@@ -595,6 +684,16 @@ @book{ramanathanIntroductionNeuromorphicComputing2025
file = {/Users/tit420/Zotero/storage/JCZQ8GXY/853942021D89F82AED182F9021E7E0F5.html}
}
+@online{RealScorelineReveals,
+ title = {The {{Real Scoreline}} Reveals Nations Facing Climate Penalties - {{University}} of {{Reading}}},
+ author = {The University of Reading},
+ url = {https://www.reading.ac.uk/news/2026/University-News/The-Real-Scoreline-reveals-nations-facing-climate-penalties},
+ urldate = {2026-06-16},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T01:04:20.125Z},
+ file = {/Users/tit420/Zotero/storage/926BIU3J/The-Real-Scoreline-reveals-nations-facing-climate-penalties.html}
+}
+
@unpublished{ruchtiUSRSE25Rapid2025,
title = {{{USRSE}} 25 Rapid Access Micro Talks},
author = {Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula and Ruchti, Carol and Ogundipe, Michael and Ward, Brian and Hillegas, Curt and Mizrachi, Eli and Brownell, Dave and Tapera, Tinashe Michael and Soules, Jeff and Lackie, Paula},
@@ -627,12 +726,10 @@ @online{saulGreatExpectationsUnifying2025
file = {/Users/tit420/Zotero/storage/NE7I7ZIL/Saul - 2025 - Great expectations Unifying Statistical Theory and Programming.pdf;/Users/tit420/Zotero/storage/G87HXPJD/2510.html}
}
-@video{schmidtByteSizedFunFloating2026,
- entrysubtype = {video},
+@audio{schmidtByteSizedFunFloating2026,
title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{ByteSized}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-03-31},
url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
urldate = {2026-04-13},
@@ -643,12 +740,10 @@ @video{schmidtByteSizedFunFloating2026
file = {/Users/tit420/Zotero/storage/PTLJK4KV/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli.html}
}
-@video{schmidtByteSizedFunFloating2026a,
- entrysubtype = {video},
+@audio{schmidtByteSizedFunFloating2026a,
title = {[{{EN}}] {{ByteSized}}: Fun with Floating Points - {{U Ruede}}, {{A Herten}} and {{E}} Di {{Napoli}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{ByteSized}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-03-31},
url = {https://www.buzzsprout.com/1326658/episodes/18841644-en-bytesized-fun-with-floating-points-u-ruede-a-herten-and-e-di-napoli},
urldate = {2026-04-13},
@@ -673,12 +768,10 @@ @audio{schmidtByteSizedHowGet2026
file = {/Users/tit420/Zotero/storage/44JQ455Z/18674534-en-bytesized-how-to-get-your-digital-ducks-in-a-row-with-richard-acton.html}
}
-@video{schmidtNextBrainExploringHuman2026,
- entrysubtype = {video},
+@audio{schmidtNextBrainExploringHuman2026,
title = {[{{EN}}] {{NextBrain}}: Exploring the Human Brain - {{Eugenio Iglesias}}, {{James Hughes}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{NextBrain}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-03-17},
url = {https://www.buzzsprout.com/1326658/episodes/18717155-en-nextbrain-exploring-the-human-brain-eugenio-iglesias-james-hughes},
urldate = {2026-04-13},
@@ -702,12 +795,10 @@ @audio{schmidtRevealingStructureCrystals2026
file = {/Users/tit420/Zotero/storage/DSPJ2H3G/18674558-en-revealing-the-structure-of-crystals-and-proteins-with-crystfel-thomas-white.html}
}
-@video{schmidtTeamPortraitResearch2026,
- entrysubtype = {video},
+@audio{schmidtTeamPortraitResearch2026,
title = {[{{EN}}] {{Team Portrait}}: {{Research Software Engineering}} in {{Newcastle}} - {{Code}} for {{Thought}}},
shorttitle = {[{{EN}}] {{Team Portrait}}},
- namea = {Schmidt, Peter},
- nameatype = {collaborator},
+ author = {Schmidt, Peter},
date = {2026-03-24},
url = {https://codeforthought.buzzsprout.com/1326658/episodes/18761138-en-team-portrait-research-software-engineering-in-newcastle},
urldate = {2026-04-13},
@@ -718,6 +809,20 @@ @video{schmidtTeamPortraitResearch2026
file = {/Users/tit420/Zotero/storage/ZST9FS63/18761138-en-team-portrait-research-software-engineering-in-newcastle.html}
}
+@online{schreinerClaudeCodeReviews2026,
+ title = {Claude {{Code Reviews}} with {{Fable}}},
+ author = {Schreiner, Henry},
+ date = {2026-06-16T20:00:00-04:00},
+ url = {https://iscinumpy.dev/post/claude-code-reviews/},
+ urldate = {2026-06-17},
+ abstract = {Fable came out and then disappeared a couple of days later. In that short time, I managed to run a lot of repository reviews with it, and was really happy with the results. I’ve found and fixed around 400 bugs and 400+ other issues (performance, simplifications, modernizations) across dozens of my projects, making several hundred PRs with a nearly 100\% merge rate on decided PRs.},
+ langid = {english},
+ organization = {ISciNumPy.dev},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-17T16:59:48.292Z},
+ file = {/Users/tit420/Zotero/storage/RI3ZH3FE/claude-code-reviews.html}
+}
+
@online{SilentScientistWhen2025,
title = {The {{Silent Scientist}}: {{When Software Research Fails}} to {{Reach Its Audience}} – {{Communications}} of the {{ACM}}},
shorttitle = {The {{Silent Scientist}}},
@@ -799,6 +904,20 @@ @report{teranishiS4PSTStewardshipAdvancement2026
file = {/Users/tit420/Zotero/storage/UYMG4WYZ/Teranishi et al. - 2026 - S4PST Stewardship and Advancement for Programming Systems and Tools 2024-2025 Project Report.pdf}
}
+@online{udellHowMakeBest2026,
+ title = {How to Make Best Use of Git and {{GitHub}} for {{AI-assisted}} Software Development},
+ author = {Udell, Jon},
+ date = {2026-06-02T19:41:11+00:00},
+ url = {https://blog.jonudell.net/2026/06/02/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development/},
+ urldate = {2026-06-16},
+ abstract = {I’m working on a new tool whose tagline is the title of this post: Make best use of git and GitHub for AI-assisted software development. Called Bram (“Bram runs agents mindfully”)…},
+ langid = {american},
+ organization = {How to make best use of git and GitHub for AI-assisted software development},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:18:22.799Z},
+ file = {/Users/tit420/Zotero/storage/74BXFIZD/how-to-make-best-use-of-git-and-github-for-ai-assisted-software-development.html}
+}
+
@online{UnderstandingAdvancingResearch2025,
title = {Understanding and Advancing Research Software Grant Funding Models},
date = {2025-07-25},
@@ -812,3 +931,30 @@ @online{UnderstandingAdvancingResearch2025
Read\_Status\_Date: 2026-03-16T02:12:49.786Z},
file = {/Users/tit420/Zotero/storage/UVZXHIQE/v1.html}
}
+
+@audio{WhatHappenedAgile2026,
+ title = {[{{EN}}] {{What}} Happened to Agile Development? - {{A}} Review with {{Dave Thomas}} - {{Code}} for {{Thought}}},
+ shorttitle = {[{{EN}}] {{What}} Happened to Agile Development?},
+ author = {Schmidt, Peter},
+ date = {2026-06-16},
+ url = {https://www.buzzsprout.com/1326658/episodes/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas},
+ urldate = {2026-06-16},
+ abstract = {English Edition:\ I want to come back to agile development practices with my guest Dave Thomas, or Pragmatic Dave as he is also known in the trade. Dave is one of the authors of the manifesto for agile development - and we talk about what has ...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/NBJV5ZD6/19292687-en-what-happened-to-agile-development-a-review-with-dave-thomas.html}
+}
+
+@audio{WhenBitsRot2026,
+ title = {[{{EN}}] {{When Bits Rot}} - with {{C McKean}}, {{L Talboom}}, {{A Page-Mitchell}} - {{Code}} for {{Thought}}},
+ author = {Schmidt, Peter},
+ date = {2026-06-09},
+ url = {https://codeforthought.buzzsprout.com/1326658/episodes/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell},
+ urldate = {2026-06-16},
+ abstract = {English Edition: floppy disks, hard drives, CDs, DVDs, SSD drives - no matter what you choose to store your data on - ultimately they all decay. With my guests Callum McKean, Leontien Talboom and Adrian Page-Mitchell, we're going to talk about wha...},
+ langid = {english},
+ annotation = {Read\_Status: To Read\\
+Read\_Status\_Date: 2026-06-16T16:05:28.241Z},
+ file = {/Users/tit420/Zotero/storage/YGL4ZLC9/19221837-en-when-bits-rot-with-c-mckean-l-talboom-a-page-mitchell.html}
+}
diff --git a/_includes/citation-article.html b/_includes/citation-article.html
new file mode 100644
index 000000000..1347d2127
--- /dev/null
+++ b/_includes/citation-article.html
@@ -0,0 +1,104 @@
+{% assign ref = include.ref %}
+
+{% assign people = ref.author %}
+{% if people == nil or people.size == 0 %}
+ {% assign people = ref.editor %}
+{% endif %}
+
+{% capture creators -%}
+{%- if people and people.size > 0 -%}
+ {%- for a in people -%}
+ {%- if forloop.index <= 3 -%}
+ {%- if a.literal -%}
+ {{ a.literal }}
+ {%- elsif a.family and a.given -%}
+ {{ a.family }}, {{ a.given | slice: 0 }}.
+ {%- elsif a.family -%}
+ {{ a.family }}
+ {%- elsif a.name -%}
+ {{ a.name }}
+ {%- endif -%}
+ {%- if forloop.index < people.size and forloop.index < 3 -%}, {% endif -%}
+ {%- elsif forloop.index == 4 -%}
+ et al.
+ {%- break -%}
+ {%- endif -%}
+ {%- endfor -%}
+{%- elsif ref.publisher -%}
+ {{ ref.publisher }}
+{%- elsif ref.institution -%}
+ {{ ref.institution }}
+{%- elsif ref.organization -%}
+ {{ ref.organization }}
+{%- endif -%}
+{%- endcapture %}
+
+{% assign creators = creators | strip %}
+
+{% assign year = nil %}
+{% assign date_parts = ref.issued["date-parts"] %}
+{% if date_parts and date_parts[0] %}
+ {% assign year = date_parts[0][0] %}
+{% endif %}
+
+{% assign title = ref.title %}
+
+{% assign container = ref["container-title"] %}
+{% if container and container.first %}
+ {% assign container = container.first %}
+{% endif %}
+
+{% assign collection = ref["collection-title"] %}
+{% if collection and collection.first %}
+ {% assign collection = collection.first %}
+{% endif %}
+
+{% assign publisher = ref.publisher | default: ref.institution | default: ref.organization %}
+{% assign place = ref["publisher-place"] %}
+{% assign genre = ref.genre %}
+{% assign number = ref.number %}
+{% assign volume = ref.volume %}
+{% assign issue = ref.issue %}
+{% assign page = ref.page %}
+{% assign edition = ref.edition %}
+
+{% assign link = ref.url | default: ref.URL %}
+{% if ref.doi %}
+ {% assign doi_clean = ref.doi
+ | remove: "https://doi.org/"
+ | remove: "http://doi.org/"
+ | remove: "doi:" %}
+ {% assign link = "https://doi.org/" | append: doi_clean %}
+{% endif %}
+
+{% capture venue -%}
+{%- if container -%}
+ *{{ container }}*{% if volume %} {{ volume }}{% endif %}{% if issue %}({{ issue }}){% endif %}{% if page %}, {{ page }}{% endif %}
+{%- elsif collection -%}
+ *{{ collection }}*{% if volume %} {{ volume }}{% endif %}{% if issue %}({{ issue }}){% endif %}{% if page %}, {{ page }}{% endif %}
+{%- endif -%}
+{%- endcapture %}
+
+{% assign venue = venue | strip %}
+
+{% capture details -%}
+{%- if genre -%}
+ {{ genre }}
+{%- endif -%}
+{%- if number -%}
+ {%- if genre -%}, {% endif -%}{{ number }}
+{%- endif -%}
+{%- if edition -%}
+ {%- if genre or number -%}. {% endif -%}{{ edition }} ed.
+{%- endif -%}
+{%- if publisher -%}
+ {%- if genre or number or edition -%}. {% endif -%}{{ publisher }}
+{%- endif -%}
+{%- if place -%}
+ {%- if publisher -%}, {% elsif genre or number or edition -%}. {% endif -%}{{ place }}
+{%- endif -%}
+{%- endcapture %}
+
+{% assign details = details | strip %}
+
+- {% if creators != "" %}**{{ creators }}**{% endif %}{% if year %}{% if creators != "" %} {% endif %}({{ year }}){% endif %}. *{{ title }}*{% if venue != "" %}. {{ venue }}{% endif %}{% if details != "" %}. {{ details }}{% endif %}{% if link %}. [Read it.]({{ link }}){% endif %}
\ No newline at end of file
diff --git a/_includes/citation-blog.html b/_includes/citation-blog.html
new file mode 100644
index 000000000..ca82ae4dd
--- /dev/null
+++ b/_includes/citation-blog.html
@@ -0,0 +1,52 @@
+{% assign ref = include.ref %}
+
+{% assign people = ref.author %}
+{% if people == nil or people.size == 0 %}
+ {% assign people = ref.editor %}
+{% endif %}
+
+{% capture creators -%}
+{%- if people and people.size > 0 -%}
+ {%- for a in people -%}
+ {%- if forloop.index <= 3 -%}
+ {%- if a.literal -%}
+ {{ a.literal }}
+ {%- elsif a.family and a.given -%}
+ {{ a.family }}, {{ a.given | slice: 0 }}.
+ {%- elsif a.family -%}
+ {{ a.family }}
+ {%- elsif a.name -%}
+ {{ a.name }}
+ {%- endif -%}
+ {%- if forloop.index < people.size and forloop.index < 3 -%}, {% endif -%}
+ {%- elsif forloop.index == 4 -%}
+ et al.
+ {%- break -%}
+ {%- endif -%}
+ {%- endfor -%}
+{%- elsif ref.publisher -%}
+ {{ ref.publisher }}
+{%- elsif ref.organization -%}
+ {{ ref.organization }}
+{%- endif -%}
+{%- endcapture %}
+
+{% assign creators = creators | strip %}
+
+{% assign year = nil %}
+{% if ref.issued and ref.issued.date-parts and ref.issued.date-parts[0] %}
+ {% assign year = ref.issued.date-parts[0][0] %}
+{% endif %}
+
+{% assign title = ref.title %}
+{% assign container = ref.container-title %}
+{% if container and container.first %}
+ {% assign container = container.first %}
+{% endif %}
+
+{% assign link = ref.url | default: ref.URL %}
+{% if ref.doi and link == nil %}
+ {% assign link = "https://doi.org/" | append: ref.doi %}
+{% endif %}
+
+- {% if creators != "" %}**{{ creators }}**{% endif %}{% if year %}{% if creators != "" %} {% endif %}({{ year }}){% endif %}. *{{ title }}*{% if container %}. *{{ container }}*{% endif %}{% if link %}. [Check it out.]({{ link }}){% endif %}
\ No newline at end of file
diff --git a/_includes/citation-media.html b/_includes/citation-media.html
new file mode 100644
index 000000000..6459b919a
--- /dev/null
+++ b/_includes/citation-media.html
@@ -0,0 +1,54 @@
+{% assign ref = include.ref %}
+
+{% assign people = ref.author %}
+{% if people == nil or people.size == 0 %}
+ {% assign people = ref.editor %}
+{% endif %}
+
+{% capture creators -%}
+{%- if people and people.size > 0 -%}
+ {%- for a in people -%}
+ {%- if forloop.index <= 3 -%}
+ {%- if a.literal -%}
+ {{ a.literal }}
+ {%- elsif a.family and a.given -%}
+ {{ a.family }}, {{ a.given | slice: 0 }}.
+ {%- elsif a.family -%}
+ {{ a.family }}
+ {%- elsif a.name -%}
+ {{ a.name }}
+ {%- endif -%}
+ {%- if forloop.index < people.size and forloop.index < 3 -%}, {% endif -%}
+ {%- elsif forloop.index == 4 -%}
+ et al.
+ {%- break -%}
+ {%- endif -%}
+ {%- endfor -%}
+{%- elsif ref.publisher -%}
+ {{ ref.publisher }}
+{%- elsif ref.organization -%}
+ {{ ref.organization }}
+{%- endif -%}
+{%- endcapture %}
+
+{% assign creators = creators | strip %}
+
+{% assign year = nil %}
+{% if ref.issued and ref.issued.date-parts and ref.issued.date-parts[0] %}
+ {% assign year = ref.issued.date-parts[0][0] %}
+{% endif %}
+
+{% assign action_label = "Open resource" %}
+{% if ref.URL %}
+ {% assign url_lc = ref.URL | downcase %}
+{% elsif ref.url %}
+ {% assign url_lc = ref.url | downcase %}
+{% endif %}
+
+{% if url_lc contains "youtube.com" or url_lc contains "youtu.be" or url_lc contains "vimeo.com" %}
+ {% assign action_label = "Watch here" %}
+{% elsif url_lc contains "buzzsprout.com" or url_lc contains "podcast" or url_lc contains "spotify.com" %}
+ {% assign action_label = "Listen here" %}
+{% endif %}
+
+- {% if creators != "" %}**{{ creators }}**{% endif %}{% if year %}{% if creators != "" %} {% endif %}({{ year }}){% endif %}. *{{ ref.title }}*{% if ref.container-title %}. *{{ ref.container-title }}*{% endif %}{% if ref.url or ref.URL %}. [{{ action_label }}.]({{ ref.url | default: ref.URL }}){% endif %}
\ No newline at end of file
diff --git a/_posts/newsletters/2026-08-05-newsletter.md b/_posts/newsletters/2026-08-05-newsletter.md
index 43c6b7bc9..d71b9a962 100644
--- a/_posts/newsletters/2026-08-05-newsletter.md
+++ b/_posts/newsletters/2026-08-05-newsletter.md
@@ -1,13 +1,13 @@
---
layout: post
title: "US-RSE Summer 2026 Newsletter"
-subtitle: "Summer is in full swing, which means US-RSE is right around the corner..."
+subtitle: "☀️Summer is in full swing, which means US-RSE is right around the corner...☀️"
category: newsletter
tags: [newsletter, August]
date: 2026-08-05 00:00:00 -0400
author: "Tinashe M. Tapera (Author & Editor), Sandra Gesing (Editor), Ian Cosden (Editor)"
-image: "/assets/img/newsletter-202606/tasha-kostyuk-TtMKq3lJm-U-unsplash.jpg" #Done
-img_alttext: "A railway traffic controller with his back to the camera, looking at several screens with train camera feed and data." #Done
+image: "/assets/img/newsletter-202608/product-school-nOvIa_x_tfo-unsplash.jpg" #Done
+img_alttext: "A conference hall full of people" #Done
next_meeting_date: Thursday, July 9, 2026, 12:00PM EST #Done
sections:
preamble: true #Done
@@ -37,7 +37,7 @@ So grab a beverage and settle in as we recap all kinds of updates from the summe
In this issue...