34 lines
3.3 KiB
TeX
34 lines
3.3 KiB
TeX
|
\documentclass[10pt, draftclsnofoot,onecolumn, compsoc]{IEEEtran}
|
||
|
|
|
||
|
|
\def\changemargin#1#2{\list{}{\rightmargin#2\leftmargin#1}\item[]}
|
||
|
|
\let\endchangemargin=\endlist
|
||
|
|
|
||
|
|
\usepackage{setspace}
|
||
|
|
\linespread{1}
|
||
|
|
|
||
|
|
\title{Conclusions and Reflections}
|
||
|
|
|
||
|
|
\begin{document}
|
||
|
|
\maketitle
|
||
|
|
|
||
|
|
\section*{Ryan Alder}
|
||
|
|
\subsection*{What technical information did you learn?}
|
||
|
|
I learned how to write C++ code for AVR, how to compile and flash code onto Arduino chips, and how to use a bootloader (vs no bootloader) for Arduino. Outside of the hardware, I learned a lot regarding LoRa and LoRaWAN, including the specific implementation and design constraints of this communication protocol. I went into this project knowing nothing regarding LoRa, and have come a very long way since then. Diving into LoRa specification was extremely fun and rewarding, as it helped us to understand how to implement the protocol into our network. This information also provided me with knowledge regarding the constraints of the LoRa protocol, informing me of the scalability and efficiency of a full LoRaWAN network.
|
||
|
|
|
||
|
|
\subsection*{What non-technical information did you learn?}
|
||
|
|
How to communicate with team members, project management, and document design. This class required a lot of writing which I would not classify as a strong suit for myself, and having the opportunity to write helped me to build that skill.
|
||
|
|
|
||
|
|
\subsection*{What have you learned about project work?}
|
||
|
|
Specifically, I have learned how to effectively spread out work and work as a team. While I have had internship experience before, much of my work was completely solo and I do not have much experience working on software as a team. This is the largest project I have participated in where there were other people working on the same code base, which taught me how to develop software with others.
|
||
|
|
|
||
|
|
\subsection*{What have you learned about project management?}
|
||
|
|
Mostly, each team needs an actual leader. A team is more efficient with a person in charge helping to make decisions and assign work. Our team learned this after the Fall term, and had one of our team members assign out work during the Winter term.
|
||
|
|
|
||
|
|
\subsection*{What have you learned about working in teams?}
|
||
|
|
I have learned how to communicate with others and spread out the work. As a team member you must be flexible to other ideas, especially if you are not in charge of the team. Learning new things that others want to do is required, otherwise you wont be able to contribute or will end up forcing other people to do things that only you are confident with. Flexibility and maleability leads to a good, effective team. The more variety in terms of ideas that are brought to the table results in a better product.
|
||
|
|
|
||
|
|
\subsection*{If you could do it all over, what would you do differently?}
|
||
|
|
Honestly I wouldn't change much. After the first term, our team discovered a better way of splitting up work to make us more efficient and ensure work was being done evenly. The only significant thing I would change would be to implement this design from the beginning, to reduce anger amongst teammates and increase our efficiency. We used an online resource to assign out action items to the team members, and then team members could complete these action items on their own time and report results back to the team via this online tool.
|
||
|
|
|
||
|
|
\end{document}
|