@@ -51,12 +51,16 @@ Encountering all these problems taught us many things during the timespan of thi
<br>
First, we learned that a project dependent on other tools is always risky. While this time we put a lot of effort into a tool that ultimately didn't work, next time we would look for alternatives much earlier and consider other options. Our somewhat too great optimism at the beginning, that everything will work again, was reduced from error message to error message.
<br>
We also learned how important communication is when working with foreign code and tools. While we hesitated at the beginning, we now immediately contacted the editors with every problem where we did not know what to do. Even if this meant that we had to write them emails several times a week until we got an answer.
<br>
We also learned that error messages are not mistakes but part of the process. In this software project we encountered more errors than in our entire studies, and yet we found a solution every time.
<br>
This leads us to the next point. The more error messages there were in the beginning, the lower our motivation became. Especially in such moments where it seemed to run partly not at all, we learned how important it is to stay on. Also the importance of cooperation in a group became clearer from week to week. Despite the fact that we already functioned well as a group from the beginning and had no problem with work sharing, each error message welded us together a bit more. There were many days when we spent hours together trying to solve problems and implement new ideas. Despite not being able to meet in person due to Corona times, we found a way to communicate and act as a group on a daily basis.
<br>
If we were to start the same project again from scratch, we would probably approach things differently. However, we would not have made these experiences, which we will take with us for our future projects.
