<p>Supported by the Nordic e-Infrastructure Collaboration (NeiC), CodeRefinery is dedicated to promoting
+FAIR (Findable, Accessible, Interoperable, and Reusable) research software development.
+Our workshops provide essential training in research software development, and we are constantly evolving our teaching methods to create an effective and inclusive learning environment.</p>
+<p>Our Train the Trainer workshops are designed to share our best practices and provide insights into our approach.
+The sessions are highly interactive, encouraging participants to share their own experiences.
+While there’s no obligation to become a CodeRefinery instructor after attending, we warmly welcome anyone interested in joining our community of instructors.</p>
+<p>This blog post serves as a report on the workshop and a compilation of the invaluable contributions made by participants throughout the sessions.</p>
<h2 id="workshop-setup">Workshop setup</h2>
-<p>The workshop in August / September 2024 was not the first time we shared how we run things, however a lot has changed throughout the years and materials needed to be updated.
-We also added more exercises and discussions for participants to get to know and learn from each other.
-We also updated the format, splitting the four half day workshop days across four Tuesdays.</p>
+<p>The August/September 2024 workshop was not our first time sharing our methods, but with the many changes over the years,
+we updated the materials accordingly. We also introduced more exercises and discussions to help participants connect and learn from each other.</p>
+<p>We spread the four half-day workshop sessions across four consecutive Tuesdays in an effort to make it more manageable and engaging.</p>
<h2 id="workshop-materials">Workshop materials</h2>
-<p>The workshop materials are available at XX. We decided to not record this workshop to make it a safe space for interaction.
-You can also find previous iterations materials XX and XX.
-The materials are under CC-BY licensed and we encourage anyone to reuse them. Let us know and we can help advertize your materials/course on our website!
-The materials themselves also explain how you can create your own lesson materials in the same style using the CodeRefinery lesson template (XX). </p>
+<p>All materials from the workshop are available with a DOI on <a href="https://coderefinery.org/previews/PR906/blog/train-the-trainer/XX">Zenodo</a>. We chose not to record the sessions
+to ensure a comfortable and open environment for interaction. However, you can find materials from
+previous iterations of our <a href="https://coderefinery.github.io/train-the-trainer/branch/instructor-training/">CodeRefinery instructor training</a>
+and <a href="https://coderefinery.github.io/train-the-trainer/branch/community-teaching/">Community teaching</a>. </p>
+<p>The materials are licensed under Creative Commons Attribution 4.0 International, and we encourage anyone to reuse them.
+If you do, let us know so we can help advertise your materials or course on our website!</p>
+<p>You can also learn how to create your own lesson materials using the CodeRefinery lesson template in the episode
+<a href="https://coderefinery.github.io/train-the-trainer/lessons-with-git/#coderefinery-lesson-template">Lessons with version control episode</a>. </p>
<h2 id="participants">Participants</h2>
-<p>For this workshop, we had a record interest in the workshop with 82 registrations including instructors from 22 countries with most participants joining from Finland, United Kingdom, Norway, Sweden, Netherlands and Germany, with 10-40 participants attending the sessions. The sessions were standalone and it was free for participants to choose which session to attend.</p>
+<p>This workshop attracted record interest, with 82 registrations from 22 countries. The majority of participants were from
+Finland, the United Kingdom, Norway, Sweden, the Netherlands, and Germany, with 10-40 attendees joining each session.
+Since the sessions were standalone, participants could choose which ones to attend.</p>
+<p>We gathered on Zoom, utilizing breakout rooms and collaborative notes for discussions and questions.
+The notes are archived on the <a href="https://coderefinery.github.io/train-the-trainer/notes-archive/">materials web page</a>.</p>
<h2 id="workshop-themes-and-topics">Workshop themes and topics</h2>
<p>The main topics discussed in the workshop were:</p>
<ul>
@@ -45,39 +58,48 @@ The materials themselves also explain how you can create your own lesson materia
<li>Session 4: Workshop streaming practices and post-workshop tasks (Sep 3)</li>
</ul>
<h3 id="session-1-about-lesson-design-deployment-and-iterative-improvement">Session 1: About lesson design, deployment and iterative improvement</h3>
-<p>In our first session, we dove into the CodeRefinery lesson materials, explored the journey to their current versions, and discovered how anyone can contribute to this dynamic resource.</p>
-<p>One essential aspect of our lesson material is that we have it under version control from the very beginning. We discussed how version control makes lessonds shareable and easy to contribute. We explored different formats and highlighted why we like Sphinx with the sphinx-lesson extension.</p>
-<p>We shared our design processes for teaching material and presentations and discussed and practiced the "backwards lesson design", starting from learning objectives and learner personas.</p>
-<p>We also discussed how we learned to collect feedback, how we turn that into actionable items and how we measure the impact of our teaching. We also discussed the reasons and sources of inspiration behind major lesson and workshop updates.</p>
-<p>During the group work sessions we also encouraged everyone to share their way of creating lessons and lesson material as well as feedback.</p>
+<p>In this session, we explored the evolution of CodeRefinery lesson materials and how anyone can contribute to their ongoing development.
+A key aspect is version control, which ensures lessons are shareable and easy to contribute to. We discussed our preference for Sphinx with the sphinx-lesson extension.</p>
+<p>We introduced "backward lesson design," where we start from learning objectives and learner personas, and work backwards to create effective lessons.
+Feedback collection, its conversion into actionable improvements, and the impact of these refinements were also key topics.</p>
+<p>During group work, participants shared their methods for creating lesson materials and gathering feedback.</p>
<h3 id="session-2-tools-and-techniques-adopted-in-coderefinery-workshops">Session 2: Tools and techniques adopted in CodeRefinery workshops</h3>
-<p>In the second session, we took a peek behind the scenes of a large CodeRefinery workshop. We discovered the process of setting up a big event, the various roles involved, and how we keep it interactive with collaborative documents and the possibility to bring your own classroom.</p>
-<p>We also looked into the onboarding process for new instructors and helpers, how to prepare for teaching with regard to sound and screenshare.</p>
-<p>CodeRefinery teaches intermediate-level software development tool lessons. Since it is difficult to define "best practices", we try to teach <strong>"good enough" practices</strong>. We are also a training network for other lessons from Python to High Performance Computing. CodeRefinery Publicly-funded discrete projects (3 projects actually) transitioning towards an open community project. We have online material, teaching, and exercise sessions. Our main target audience are competent practitioners, but also novices and experts can get something out of the workshops. We want more people to work with us, and to work with more people. </p>
-<p>CodeRefinery workshops are a collaborative effort with many different roles. For these roles to play well together, onboarding the different roles is one key aspect of our workshops. All of our instructors came into the project on a different path, and we want to keep it open for many more. We try to teach our ways through this train the trainer workshop, however, we are open for everyone brining in their own experiences.</p>
-<p>Our workshops themselves are streamed (see session 4 for more information about why we do that). Having a collaborative document improves communication and interaction between participants, instructors and rest of the team. Answering questions requires a dedicated person - A Collaborative Document Manager.
-We aim to post the collaborative document on the website as soon as possible after each workshop day.</p>
-<p>In the following episode we looked at screensharing. Since we stream our workshops, have the collaborative document and want participants to work in the terminal once in a while to we share in <strong>portrait layout</strong> instead of sharing entire screen. We discussed the importance of adjusting your prompt to make commands easy to read. Readability and beauty is important: adjust your setup for your audience. We also discussed the sharing of the history of your commands. Feedback and time to improve is very important to make things clear and accessible. 10 minutes before the session starts is typically too late.</p>
-<p>We then also discussed that audio quality is important and one of the most notable parts of the workshop. Improving audio isn't hard or expensive, but does require preparation. During the workshop we also provided participants with some time to set up a nice screenshare and test their audio.</p>
+<p>This session gave participants a behind-the-scenes look at how we run large CodeRefinery workshops.
+We covered event setup, roles, and how we maintain interactivity through collaborative documents and "bring your own classroom" setups.</p>
+<p>We discussed onboarding new instructors and helpers, teaching preparation (sound, screen sharing),
+and the importance of teaching "good enough" practices in intermediate software development tools, given the difficulty of defining "best practices."
+Our workshops aim to cater to all skill levels, with a focus on competent practitioners.</p>
+<p>Collaboration plays a key role in our workshops, and we highlighted the importance of assigning a Collaborative Document Manager
+to handle questions and interactions. Participants practiced setting up effective screen shares, ensuring readability,
+tested their sound levels and learned different ways to adjust it as well as ways of adjusting terminal prompts for teaching.</p>
<h3 id="session-3-about-teaching-cool-things-we-all-would-like-to-share">Session 3: About teaching & cool things we all would like to share</h3>
-<p>The third session was all about mastering the art of teaching — from preparation strategies and embracing the co-teaching model to the tools we use and the teaching philosophies that guide us.</p>
-<p>In the first episode we learned that Computational Thinking consists of 4 main parts: decomposition, pattern recognition, abstraction and algorithmic design. We discussed how can this be a useful framework for solving problems and how it can be used practically.</p>
-<p>In the next session we discussed different viewpoints on teaching and asked participants to share their own.<br />
-Afterwards, we discussed the co-teaching approach. Co-teaching focuses on complementing individual skills and strengths in teaching process. We discussed that Co-teaching may save time, reduce teachers' workload and make lessons more interactive/ engaging. Team teaching requires some adjustments in lesson preparation and delivery.</p>
+<p>This session focused on teaching techniques, co-teaching models, and useful tools. We discussed Computational Thinking,
+a framework that breaks problem-solving into four parts: decomposition, pattern recognition, abstraction, and algorithmic design.</p>
+<p>We also examined the benefits of co-teaching, where complementary skills enhance the learning experience and reduce the workload
+for individual instructors. Participants shared their perspectives on teaching and discussed how team teaching can improve lesson delivery.</p>
<p>In the "cool gems" session we had a few tool presentations:</p>
<ul>
<li><a href="https://www.thregr.org/wavexx/software/screenkey">Screenkey for showing keyboard shortcuts</a></li>
-<li><a href="https://coderefinery.org/previews/PR906/blog/train-the-trainer/XX">Containerized teaching setup</a></li>
+<li><a href="https://github.com/bast/teaching-setup">Containerized teaching setup</a></li>
<li>A DIY teaching clock, showing chunks of 5/10 minutes in black and white sections instead of numbers</li>
</ul>
<h3 id="session-4-workshop-streaming-practices-and-post-workshop-tasks">Session 4: Workshop streaming practices and post-workshop tasks</h3>
-<p>In the fourth session, we dove into managing streaming and recording setups, unveiling our go-to tools for a seamless experience for both instructors and learners: Open Broadcaster Software (OBS) and ffmpeg.</p>
-<p>While the broadcaster role seems overwhelming at first, this episode tried to show that while it is a lot to manage, each individual part isn't that hard. We discussed that video editing can be very useful for learning and improving your teaching and that it is important to set your time budget and make it good enough in that time.</p>
-<p>Participants got hands-on experience with OBS, a powerful tool that’s great not just for workshops, but also for your personal projects. While OBS may seem complicated, it's a graphical application and most pieces make sense once you know how it works.</p>
-<h3 id="interested-join-the-next-iteration">Interested? - Join the next iteration</h3>
-<p>We are still collecting full workshop feedback and link it here later. You can however already find all notes, questions and single day feedbacks from the <a href="https://coderefinery.github.io/train-the-trainer/notes-archive">materials - notes archive</a>. By focusing on the instructors, the program creates a powerful network of individuals who are equipped to teach, inspire, and build communities. Whether you're looking to enhance your teaching skills or simply want to be a part of this growing community, the TTT program offers an opportunity to make a lasting impact on the computational research education world.</p>
-<p>Interested in becoming part of this exciting initiative?
-Learn more about the project and available lesson materials by checking out <a href="https://coderefinery.org">CodeRefinery webpage</a> and sign up for the <a href="https://coderefinery.org/about/newsletter">Coderefinery newsletter</a> to get to know about the next iteration.</p>
+<p>In this session, we covered streaming and recording workflows, with a focus on using Open Broadcaster Software (OBS) and ffmpeg.
+While managing a streaming setup can seem daunting, we broke down the process to show that each step is manageable.
+We also discussed video editing as a valuable tool for improving teaching.</p>
+<p>Participants had hands-on experience with OBS, a powerful but accessible tool, not just for workshops but for personal projects too.
+While OBS may appear complex, once the pieces fall into place, it's an intuitive tool for enhancing online workshops.</p>
+<h3 id="interested-in-joining-next-time">Interested in joining next time?</h3>
+<p>We are still collecting full workshop feedback and link it here later. You can however already find all notes,
+questions and single day feedbacks from the <a href="https://coderefinery.github.io/train-the-trainer/notes-archive">materials - notes archive</a>.
+Through this Train the Trainer workshop, we hope to empower more instructors to contribute to CodeRefinery
+and foster an inclusive community of practice around research software development.
+We look forward to seeing how participants will apply these skills and insights in their own teaching endeavors.</p>
+<p>No matter if you are an instructor or want to observe or support the project in some other way, you are very welcome.
+Learn more about the project and available lesson materials by checking out <a href="https://coderefinery.org">CodeRefinery webpage</a>
+and sign up for the <a href="https://coderefinery.org/about/newsletter">Coderefinery newsletter</a> to get to know about the next iteration.
+If you do not have any resources to join, but would like to support the project,
+please consider becoming a <a href="https://coderefinery.org/join/individuals/#coderefinery-ambassador">CodeRefinery ambassador</a>.</p>
<h2 id="collection-of-teaching-related-tips-and-tricks-gathered-throughout-the-workshop-through-questions-to-the-audience">Collection of teaching related tips and tricks gathered throughout the workshop through questions to the audience</h2>
<h3 id="what-is-the-hardest-thing-about-teaching-for-you">What is the hardest thing about teaching for you?</h3>
<ul>
diff --git a/previews/PR906/blog/train-the-trainer/index.html b/previews/PR906/blog/train-the-trainer/index.html
index 669da67c..f10a2bbe 100644
--- a/previews/PR906/blog/train-the-trainer/index.html
+++ b/previews/PR906/blog/train-the-trainer/index.html
@@ -829,19 +829,32 @@
-
CodeRefinery, supported by the Nordic e-infrastructure collaboration (NeiC), is dedicated to enhancing FAIR (Findable, Accessible, Interoperable, and Reusable) research software development practices. Our workshops aim to provide essential training in research software development, and we’re continually exploring new methods to make this learning process effective and inclusive. Through our train the trainer workshop we aim to share these practices and give some insights into why we do things as we do. The workshop was highly interactive, and apart from us sharing our experiences we also encouraged everyone in the workshop to share their own experiences. While it is not a requirement to become a CodeRefinery instructor after going through the workshop, we are welcoming everyone interested to join our pool of instructors.
-This blogpost serves as report from the workshop as well as a collection of the wonderful contributions from all participants throughout the workshop.
+ Supported by the Nordic e-Infrastructure Collaboration (NeiC), CodeRefinery is dedicated to promoting
+FAIR (Findable, Accessible, Interoperable, and Reusable) research software development.
+Our workshops provide essential training in research software development, and we are constantly evolving our teaching methods to create an effective and inclusive learning environment.
+Our Train the Trainer workshops are designed to share our best practices and provide insights into our approach.
+The sessions are highly interactive, encouraging participants to share their own experiences.
+While there’s no obligation to become a CodeRefinery instructor after attending, we warmly welcome anyone interested in joining our community of instructors.
+This blog post serves as a report on the workshop and a compilation of the invaluable contributions made by participants throughout the sessions.
Workshop setup
-The workshop in August / September 2024 was not the first time we shared how we run things, however a lot has changed throughout the years and materials needed to be updated.
-We also added more exercises and discussions for participants to get to know and learn from each other.
-We also updated the format, splitting the four half day workshop days across four Tuesdays.
+The August/September 2024 workshop was not our first time sharing our methods, but with the many changes over the years,
+we updated the materials accordingly. We also introduced more exercises and discussions to help participants connect and learn from each other.
+We spread the four half-day workshop sessions across four consecutive Tuesdays in an effort to make it more manageable and engaging.
Workshop materials
-The workshop materials are available at XX. We decided to not record this workshop to make it a safe space for interaction.
-You can also find previous iterations materials XX and XX.
-The materials are under CC-BY licensed and we encourage anyone to reuse them. Let us know and we can help advertize your materials/course on our website!
-The materials themselves also explain how you can create your own lesson materials in the same style using the CodeRefinery lesson template (XX).
+All materials from the workshop are available with a DOI on Zenodo. We chose not to record the sessions
+to ensure a comfortable and open environment for interaction. However, you can find materials from
+previous iterations of our CodeRefinery instructor training
+and Community teaching.
+The materials are licensed under Creative Commons Attribution 4.0 International, and we encourage anyone to reuse them.
+If you do, let us know so we can help advertise your materials or course on our website!
+You can also learn how to create your own lesson materials using the CodeRefinery lesson template in the episode
+Lessons with version control episode.
Participants
-For this workshop, we had a record interest in the workshop with 82 registrations including instructors from 22 countries with most participants joining from Finland, United Kingdom, Norway, Sweden, Netherlands and Germany, with 10-40 participants attending the sessions. The sessions were standalone and it was free for participants to choose which session to attend.
+This workshop attracted record interest, with 82 registrations from 22 countries. The majority of participants were from
+Finland, the United Kingdom, Norway, Sweden, the Netherlands, and Germany, with 10-40 attendees joining each session.
+Since the sessions were standalone, participants could choose which ones to attend.
+We gathered on Zoom, utilizing breakout rooms and collaborative notes for discussions and questions.
+The notes are archived on the materials web page.
Workshop themes and topics
The main topics discussed in the workshop were:
@@ -851,39 +864,48 @@ Workshop themes and topics
- Session 4: Workshop streaming practices and post-workshop tasks (Sep 3)
Session 1: About lesson design, deployment and iterative improvement
-In our first session, we dove into the CodeRefinery lesson materials, explored the journey to their current versions, and discovered how anyone can contribute to this dynamic resource.
-One essential aspect of our lesson material is that we have it under version control from the very beginning. We discussed how version control makes lessonds shareable and easy to contribute. We explored different formats and highlighted why we like Sphinx with the sphinx-lesson extension.
-We shared our design processes for teaching material and presentations and discussed and practiced the "backwards lesson design", starting from learning objectives and learner personas.
-We also discussed how we learned to collect feedback, how we turn that into actionable items and how we measure the impact of our teaching. We also discussed the reasons and sources of inspiration behind major lesson and workshop updates.
-During the group work sessions we also encouraged everyone to share their way of creating lessons and lesson material as well as feedback.
+In this session, we explored the evolution of CodeRefinery lesson materials and how anyone can contribute to their ongoing development.
+A key aspect is version control, which ensures lessons are shareable and easy to contribute to. We discussed our preference for Sphinx with the sphinx-lesson extension.
+We introduced "backward lesson design," where we start from learning objectives and learner personas, and work backwards to create effective lessons.
+Feedback collection, its conversion into actionable improvements, and the impact of these refinements were also key topics.
+During group work, participants shared their methods for creating lesson materials and gathering feedback.
-In the second session, we took a peek behind the scenes of a large CodeRefinery workshop. We discovered the process of setting up a big event, the various roles involved, and how we keep it interactive with collaborative documents and the possibility to bring your own classroom.
-We also looked into the onboarding process for new instructors and helpers, how to prepare for teaching with regard to sound and screenshare.
-CodeRefinery teaches intermediate-level software development tool lessons. Since it is difficult to define "best practices", we try to teach "good enough" practices. We are also a training network for other lessons from Python to High Performance Computing. CodeRefinery Publicly-funded discrete projects (3 projects actually) transitioning towards an open community project. We have online material, teaching, and exercise sessions. Our main target audience are competent practitioners, but also novices and experts can get something out of the workshops. We want more people to work with us, and to work with more people.
-CodeRefinery workshops are a collaborative effort with many different roles. For these roles to play well together, onboarding the different roles is one key aspect of our workshops. All of our instructors came into the project on a different path, and we want to keep it open for many more. We try to teach our ways through this train the trainer workshop, however, we are open for everyone brining in their own experiences.
-Our workshops themselves are streamed (see session 4 for more information about why we do that). Having a collaborative document improves communication and interaction between participants, instructors and rest of the team. Answering questions requires a dedicated person - A Collaborative Document Manager.
-We aim to post the collaborative document on the website as soon as possible after each workshop day.
-In the following episode we looked at screensharing. Since we stream our workshops, have the collaborative document and want participants to work in the terminal once in a while to we share in portrait layout instead of sharing entire screen. We discussed the importance of adjusting your prompt to make commands easy to read. Readability and beauty is important: adjust your setup for your audience. We also discussed the sharing of the history of your commands. Feedback and time to improve is very important to make things clear and accessible. 10 minutes before the session starts is typically too late.
-We then also discussed that audio quality is important and one of the most notable parts of the workshop. Improving audio isn't hard or expensive, but does require preparation. During the workshop we also provided participants with some time to set up a nice screenshare and test their audio.
+This session gave participants a behind-the-scenes look at how we run large CodeRefinery workshops.
+We covered event setup, roles, and how we maintain interactivity through collaborative documents and "bring your own classroom" setups.
+We discussed onboarding new instructors and helpers, teaching preparation (sound, screen sharing),
+and the importance of teaching "good enough" practices in intermediate software development tools, given the difficulty of defining "best practices."
+Our workshops aim to cater to all skill levels, with a focus on competent practitioners.
+Collaboration plays a key role in our workshops, and we highlighted the importance of assigning a Collaborative Document Manager
+to handle questions and interactions. Participants practiced setting up effective screen shares, ensuring readability,
+tested their sound levels and learned different ways to adjust it as well as ways of adjusting terminal prompts for teaching.
Session 3: About teaching & cool things we all would like to share
-The third session was all about mastering the art of teaching — from preparation strategies and embracing the co-teaching model to the tools we use and the teaching philosophies that guide us.
-In the first episode we learned that Computational Thinking consists of 4 main parts: decomposition, pattern recognition, abstraction and algorithmic design. We discussed how can this be a useful framework for solving problems and how it can be used practically.
-In the next session we discussed different viewpoints on teaching and asked participants to share their own.
-Afterwards, we discussed the co-teaching approach. Co-teaching focuses on complementing individual skills and strengths in teaching process. We discussed that Co-teaching may save time, reduce teachers' workload and make lessons more interactive/ engaging. Team teaching requires some adjustments in lesson preparation and delivery.
+This session focused on teaching techniques, co-teaching models, and useful tools. We discussed Computational Thinking,
+a framework that breaks problem-solving into four parts: decomposition, pattern recognition, abstraction, and algorithmic design.
+We also examined the benefits of co-teaching, where complementary skills enhance the learning experience and reduce the workload
+for individual instructors. Participants shared their perspectives on teaching and discussed how team teaching can improve lesson delivery.
In the "cool gems" session we had a few tool presentations:
Session 4: Workshop streaming practices and post-workshop tasks
-In the fourth session, we dove into managing streaming and recording setups, unveiling our go-to tools for a seamless experience for both instructors and learners: Open Broadcaster Software (OBS) and ffmpeg.
-While the broadcaster role seems overwhelming at first, this episode tried to show that while it is a lot to manage, each individual part isn't that hard. We discussed that video editing can be very useful for learning and improving your teaching and that it is important to set your time budget and make it good enough in that time.
-Participants got hands-on experience with OBS, a powerful tool that’s great not just for workshops, but also for your personal projects. While OBS may seem complicated, it's a graphical application and most pieces make sense once you know how it works.
-Interested? - Join the next iteration
-We are still collecting full workshop feedback and link it here later. You can however already find all notes, questions and single day feedbacks from the materials - notes archive. By focusing on the instructors, the program creates a powerful network of individuals who are equipped to teach, inspire, and build communities. Whether you're looking to enhance your teaching skills or simply want to be a part of this growing community, the TTT program offers an opportunity to make a lasting impact on the computational research education world.
-Interested in becoming part of this exciting initiative?
-Learn more about the project and available lesson materials by checking out CodeRefinery webpage and sign up for the Coderefinery newsletter to get to know about the next iteration.
+In this session, we covered streaming and recording workflows, with a focus on using Open Broadcaster Software (OBS) and ffmpeg.
+While managing a streaming setup can seem daunting, we broke down the process to show that each step is manageable.
+We also discussed video editing as a valuable tool for improving teaching.
+Participants had hands-on experience with OBS, a powerful but accessible tool, not just for workshops but for personal projects too.
+While OBS may appear complex, once the pieces fall into place, it's an intuitive tool for enhancing online workshops.
+Interested in joining next time?
+We are still collecting full workshop feedback and link it here later. You can however already find all notes,
+questions and single day feedbacks from the materials - notes archive.
+Through this Train the Trainer workshop, we hope to empower more instructors to contribute to CodeRefinery
+and foster an inclusive community of practice around research software development.
+We look forward to seeing how participants will apply these skills and insights in their own teaching endeavors.
+No matter if you are an instructor or want to observe or support the project in some other way, you are very welcome.
+Learn more about the project and available lesson materials by checking out CodeRefinery webpage
+and sign up for the Coderefinery newsletter to get to know about the next iteration.
+If you do not have any resources to join, but would like to support the project,
+please consider becoming a CodeRefinery ambassador.
What is the hardest thing about teaching for you?