docs(report): proofreading on remi's self-assessment

report/self-assessment/remi.typ

@@ -41,16 +41,21 @@ Un rapport d'auto-évaluation doit dans le grandes lignes :
 
 = Introduction
 
-This report is a self-assessment provided aside of the team report of the project. It is meant to be a personal reflection on the project, and should be read after reading the team report.
+This report is a self-assessment provided alongside the team report. It is meant to be a personal reflection on the project, and should be read after the team report.
 
-I want to warn the reader that like it's a bit said in the team report, this project was made in parallel of a similar hobby project made with some friends, at least similar to my part. I have to admit I made way more efforts on this hobby project as this current project. Not because I didn't care about this project, but because my hobby project is way more complex and will last after this semester. 
+I want to be upfront, as hinted at in the team report, that this project ran in parallel with a similar hobby project I was doing with some friends. At least, similar regarding my specific tasks. I have to admit, I put more effort into the hobby project than this current one. Not because I didn't care about this PI, but because my hobby project is significantly more complex and will continue long after this semester ends. However, the skills I was developing there directly benefited my work here, and vice versa.
 
 = Role in the Team
-My role was to up the server, develop all the API around the database and the data management in the cloud.
 
-It also appear during the project that I have an important technical role. We decide in the beginning of the project to establish clear git rules to work efficiently together. I was in charge to write this Guidelines & Unified Laws for Advanced Gitflow (GULAG) and to make sure everyone respect it. It also appears quickly that I have to do most of the review. This was quite time conssuming but very formative. We all have different path before arriving in this project and diffent coding approach. 
+My primary role was to set up the server, and develop the APIs for the database and cloud data management.
+
+It also became apparent early on that I'd naturally take on a broader technical role. We decided at the beginning to establish clear Git rules to work efficiently. I was responsible for writing these "Guidelines & Unified Laws for Advanced Gitflow" (GULAG) and making sure everyone respected them. It quickly turned out that I also had to do most of the code reviews. This was quite time-consuming but very formative, especially since we all came into this project with different backgrounds and coding approaches.
+
+Beyond doing most of the reviews, I also ended up helping my teammates with debugging and code design. I became the team's troubleshooter.
+
+I was basically the person picking up all the tasks we forgot to plan for at the beginning. I didn't mind this role at all; I like helping out and sharing my knowledge.
+
 
-During the project more than do most of the review, I also help some other of my teammates for debugging and code design. I became the handyman of the team, the one who can help everyone for everything. I don't mind this role, I like to help and to share my knowledge.
 
 = Objective & skills review
 
@@ -59,7 +64,9 @@ My initial objective was to #quote(strike[Solve Maxwell's equations])
   A data infrastructure is automated, deployed both in productive and development environment. The database is automatically configured and populated by external MeteoSwiss data. 
   The student didn't experiment automatic deploy /configuration and multi-environment. 
 ]
-This objective was partially achieved and changed during the project. 
-I indeed deployed an server infrastructure with a database and a broker with the corresponding API to push and retrieve data. However, the meteoSwiss data was abandonned after one student left the groupe because it was useless. The database is indeed automatically configured. Automatic deployement was made by another student. 
 
-I devlop this skills for automatic deployement on my hobby project aside this one. But I still develop some skills on this project. Not really what I expected, but more on technical management project, and how to work with people with very different background and horizon. I became more polivalent during this project, something very important for me as engineer I think we should be all more able to do a bit of everything and speak with everyone. 
+This objective was partially completed and shifted during the project. I did successfully deploy a server infrastructure with a database and a broker, including the corresponding APIs to push and retrieve data. However, the MeteoSwiss data integration was abandoned because it fell out of scope after one student left the group.
+
+The database is indeed automatically configured. I didn't focus on setting up automatic deployment for my part, mostly because this code is basically a prototype that won't be maintained after the semester ends anyway. Another student ended up doing automatic deployment for his own part. I did, however, develop those automatic deployment skills on my hobby project instead.
+
+I still learned a lot on this project overall. It wasn't really what I expected technically, but I gained much more experience in technical project management and figuring out how to work with people from very different backgrounds and horizons. I became much more versatile during this project, which, I think, is essential for an engineer. We should all be able to do a bit of everything and communicate with anyone.