Add reflection
This commit is contained in:
parent
bb9a8419cb
commit
aa6ef080a8
|
@ -56,4 +56,50 @@ That even with hardware it is possible to work with hardware over the internet t
|
||||||
\subsection*{If you could do it all over, what would you do differently?}
|
\subsection*{If you could do it all over, what would you do differently?}
|
||||||
Hardware wise it would have been easier had we used an ARM CPU based microcontroller instead of AVR, as this would have provided us with much more memory and disk space for our application.
|
Hardware wise it would have been easier had we used an ARM CPU based microcontroller instead of AVR, as this would have provided us with much more memory and disk space for our application.
|
||||||
|
|
||||||
|
\pagebreak
|
||||||
|
\section*{Danila Fedorin}
|
||||||
|
|
||||||
|
\subsection*{What technical information did you learn?}
|
||||||
|
I did not learn any technical information this year. I did the sections of the project
|
||||||
|
that I knew how to do - the Android application and the API server. Our team did a great
|
||||||
|
job in separating concerns, so that I only needed to be aware of the boundaries between
|
||||||
|
our parts, and not of the implementation of the hardware.
|
||||||
|
|
||||||
|
\subsection*{What non-technical information did you learn?}
|
||||||
|
I learned that cows are actually surprisingly hard to train - though our project did not
|
||||||
|
reach the animal testing stage, I did some research, which suggested that fenceless collar
|
||||||
|
systems will be ineffective with most livestock.
|
||||||
|
|
||||||
|
\subsection*{What have you learned about project work?}
|
||||||
|
I did not learn much about project work, since this is not
|
||||||
|
at all my first project, and nor is it my biggest one. I find
|
||||||
|
that our inability to pick our own capstone projects tends to
|
||||||
|
lead to rather uninspired final products.
|
||||||
|
|
||||||
|
\subsection*{What have you learned about project management?}
|
||||||
|
I learned that having a centralized archive of all files related to the project
|
||||||
|
is very helpful. This is the first project I was part of
|
||||||
|
that was not entirely contained within a Git repository, and
|
||||||
|
had other metadata (images, documents, receipts). With the year
|
||||||
|
coming to an end, we now find ourselves with a complete
|
||||||
|
archive of all our data, without any hastle.
|
||||||
|
|
||||||
|
\subsection*{What have you learned about working in teams?}
|
||||||
|
This was the first project I was part of that did not
|
||||||
|
have a well-defined position of power. Though the client
|
||||||
|
did effectively tell us what to do, they did not micromanage
|
||||||
|
the majority of our group work, and the team had to find
|
||||||
|
its own dynamic to meet deadlines. I learned about the
|
||||||
|
value of explicitly delegating action items to group members,
|
||||||
|
who, though willing to help, would not do so without
|
||||||
|
request. This is likely because, without well-defined
|
||||||
|
goals, it's hard to know where to start.
|
||||||
|
|
||||||
|
\subsection*{If you could do it all over, what would you do differently?}
|
||||||
|
I would take some time to look into what my teammates are doing.
|
||||||
|
I did what I knew how to do, and time pressures led me to not stray
|
||||||
|
far from my own part of the work. However, my team members were
|
||||||
|
working on some interesting stuff, and I would've learned a lot
|
||||||
|
from looking over their shoulders.
|
||||||
|
|
||||||
\end{document}
|
\end{document}
|
||||||
|
|
Loading…
Reference in New Issue
Block a user