Update nl-workshop1.md

Updated with event write up and photograph

nl-workshop1.md

@@ -4,6 +4,24 @@ title: CODECHECK NL Workshop for Engineering Sciences
 permalink: /nl-workshop1/
 ---
 
+## UPDATE: We have successfully completed our first workshop! Read on...
+
+![Image of participants from CODECHECK Delft event](https://github.com/codecheckers/codecheckers.github.io/assets/150461262/f91ed93a-2624-457d-bc2a-a01353891f51)
+
+
+On the 30th of May 2024, the CODECHECK-NL team organised its first roadshow event in Delft. The event marks the beginning of a series of four workshops to be conducted across the Netherlands, where we carry out live codechecks with authors and reviewers, while also training a new batch of codecheckers across universities in the Netherlands. 
+
+The Delft event kicked off in the morning with 20 participants and members of the CODECHECK-NL team. We began with a short introduction to the  project and its scope by Frank Ostermann (PI for the project, based at the University of Twente), followed by an introduction to codechecking by Stephen Eglen, one of the founders of CODECHECK, and a computational neuroscientist based at the University of Cambridge. Stephen’s presentation (which can be found [here](https://sje30.github.io/talks/2024/codecheck2024-02.html#/title-slide)) introduced the philosophy behind codecheck, and the importance of the concept of “good enough” in facilitating code reproducibility. The introduction was followed by a live demo codecheck, conducted on a project submitted by Filip Surma of Delft University of Technology. Curious to see what a CODECHECK certificate looks like? See Filip's certificate [here](https://zenodo.org/records/11403956). 
+
+Following lunch and the successful codecheck of Filip’s project, in collaboration with the participants, in the afternoon we moved into breakout sessions, codechecking three more projects in smaller groups, with authors also present during the process. Three more successful codechecks later, participants had a much clearer picture of what codechecks are, how the process works, and how easy or difficult it can be to run or reuse someone else’s code! 
+
+All these points were touched upon in our final reflection session, where we considered questions of how codechecks could be incorporated into the research and publishing workflow, and ideas for the sustainability of codechecking. Some important issues were raised, such as the importance of institutional support, how to recognise codecheck efforts for both authors and reviewers. Some interesting solutions were also proposed, like the concept of ‘codecheck buddies’, or making codechecks a service researchers could avail of, having a dedicated ‘codechecker’ based at a journal. The discussion was finally only concluded because it was time to leave the room!  
+
+Do you find the topics of code reuse, reproducibility and learning a hands-on skill interesting? Then join us at one of our next workshops! We are hosting our next event at the **University of Twente on 26th of September 2024**, and another at the **Erasmus University Rotterdam on the 28th of November 2024**. Save the (tentative) dates, and stay tuned for updates!  
+
+---------------------------------------------------------------------------------------
+
+## Our call for papers for the Delft worksop
 
 ### Are you a researcher in engineering interested in reproducible code and Open Science? We have the perfect opportunity for you! 
 
@@ -29,7 +47,7 @@ later in the year as we plan three more workshops around the
 Netherlands.
 
 
-## What do I get if I submit my code?  
+### What do I get if I submit my code?  
 
 A codechecker will work with you during the session to check whether
 your code and data can be run by others to generate the same or
@@ -47,7 +65,7 @@ By participating, you contribute towards making science more open and
 transparent AND increase the visibility of your own research! 
 
 
-## Sounds good! What should I do?  
+### Sounds good! What should I do?  
 
 Are you interested in submitting code or data for this event, and helping to
 promote code reproducibility? Send an email