docs(report): compress remi's self-assessment to 1 page
Signed-off-by: Klagarge <remi@heredero.ch>
This commit was merged in pull request #3.
This commit is contained in:
@@ -21,6 +21,7 @@
|
||||
logos: logos,
|
||||
custom-title-page: mse-title-page(
|
||||
title: [Self-assessment],
|
||||
subtitle: [Team: Pleeeeein deeeee eeeeeeeeeeeeeeeeee],
|
||||
authors: (
|
||||
(name: "Rémi Heredero"),
|
||||
),
|
||||
@@ -28,6 +29,8 @@
|
||||
),
|
||||
)
|
||||
|
||||
// #show "e": "ee"
|
||||
|
||||
//-------------------------------------
|
||||
// Content
|
||||
//
|
||||
@@ -39,11 +42,33 @@ Un rapport d'auto-évaluation doit dans le grandes lignes :
|
||||
- Lister les gains en compétences que vous ressentez après ce projet.
|
||||
*/
|
||||
|
||||
#show heading.where(level: 1): (it) => {
|
||||
set text(size: huge)
|
||||
set block(above: 1.2em, below: 1.0em)
|
||||
if it.numbering != none {
|
||||
let num = numbering(it.numbering, ..counter(heading).at(it.location()))
|
||||
let prefix = num + h(0.5em) + text(code-border)[|] + h(0.5em)
|
||||
unshift-prefix(prefix, it.body)
|
||||
} else {
|
||||
it
|
||||
}
|
||||
}
|
||||
|
||||
#show heading.where(level: 2): (it) => {
|
||||
if it.numbering != none {
|
||||
let num = numbering(it.numbering, ..counter(heading).at(it.location()))
|
||||
unshift-prefix(num + h(0.8em), it.body)
|
||||
} else {
|
||||
it
|
||||
}
|
||||
}
|
||||
|
||||
= Introduction
|
||||
|
||||
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 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.
|
||||
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.
|
||||
// However, the skills I was developing there directly benefited my work here, and vice versa.
|
||||
|
||||
= Role in the Team
|
||||
|
||||
@@ -55,18 +80,15 @@ Beyond doing most of the reviews, I also ended up helping my teammates with debu
|
||||
|
||||
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.
|
||||
|
||||
|
||||
|
||||
= Objective & skills review
|
||||
|
||||
My initial objective was to #quote(strike[Solve Maxwell's equations])
|
||||
#quote(block: true)[
|
||||
#par(text(size: 0.8em, emph[
|
||||
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 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.
|
||||
The database is indeed automatically configured. I didn't focus on setting up automatic deployment for my part. Another student ended up doing automatic deployment on the project.
|
||||
|
||||
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.
|
||||
Reference in New Issue
Block a user