mirror of
https://github.com/smyalygames/checklist-tester.git
synced 2025-05-18 06:24:12 +02:00
feat(dissertation): add planning and implementation to reflection
This commit is contained in:
parent
5bac026e70
commit
186c087572
@ -92,7 +92,74 @@
|
||||
|
||||
|
||||
\section{Reflection}
|
||||
\subsection{Planning}
|
||||
\subsubsection{Gantt Chart}
|
||||
Used Gantt chart to create a plan for what would be needed from this project
|
||||
|
||||
\textbf{Pros:}
|
||||
\begin{itemize}
|
||||
\item Was useful for the first part because it set expectations
|
||||
of what was needed and how much time there was to complete them
|
||||
\item Helped visualize the different components of the project
|
||||
\item Helped in the beginning being accompanied by a Kanban in Leantime\footnote{\url{https://leantime.io/}}
|
||||
\end{itemize}
|
||||
|
||||
\textbf{Cons:}
|
||||
\begin{itemize}
|
||||
\item Was not detailed enough, and a design document would have been useful
|
||||
to accompany the Gantt chart for each section
|
||||
\item The lack of detail was not helpful when falling behind as having
|
||||
attention deficit hyperactivity disorder (ADHD)
|
||||
added to the burden of feeling like each section was a massive project
|
||||
\item Leantime's claim for being \enquote{built with ADHD [\ldots] in mind}
|
||||
felt misleading as navigating through it felt worse than using the front page
|
||||
of Stack Overflow\footnote{\url{https://stackoverflow.com/}}
|
||||
\item Todoist\footnote{\url{https://todoist.com/}} was a good alternative though
|
||||
\end{itemize}
|
||||
|
||||
\subsubsection{GUI Design}
|
||||
Figma was very useful in implementations as
|
||||
|
||||
\textbf{Pros:}
|
||||
\begin{itemize}
|
||||
\item It helped with timing and knowing what to do
|
||||
\item Made things feel manageable as it was split up to different sections
|
||||
\item Meant features will not be forgotten
|
||||
\end{itemize}
|
||||
|
||||
\textbf{Cons:}
|
||||
\begin{itemize}
|
||||
\item Certain features being too simple and annoying to use
|
||||
\item A bit of a learning curve for using other components, compared
|
||||
to using plugins
|
||||
\end{itemize}
|
||||
|
||||
\subsection{Implementation}
|
||||
|
||||
\subsubsection{Checklist Tester}
|
||||
\begin{itemize}
|
||||
\item Implementing the GUI was useful to split up the sections required
|
||||
for the project and having a goal for what to be done
|
||||
\item However, a bit too much time was spent on creating a GUI when it
|
||||
could have been used for development
|
||||
\item It was useful for motivational reasons to feel like something
|
||||
materialistic has been produced rather than something theoretical
|
||||
\item Was originally intended to be used to interact with custom
|
||||
plugin for X-Plane as it would have been difficult otherwise
|
||||
\end{itemize}
|
||||
|
||||
\subsubsection{Connecting to the Flight Simulator}
|
||||
\begin{itemize}
|
||||
\item Would have been more useful to search a bit further if there was
|
||||
another plugin available, as found Dataref Editor on the X-Plane docs,
|
||||
so could have looked for a similar plugin for connecting to X-Plane
|
||||
\item At first spent about a week developing a C++ X-Plane plugin from scratch,
|
||||
requiring to figure out sockets
|
||||
\item At the same time finding out XPC exists and having wasted that time
|
||||
\item However, it did teach me more about understanding how sockets work and
|
||||
more about C++ and setting up a project with CMake and adding packages with
|
||||
vcpkg
|
||||
\end{itemize}
|
||||
|
||||
\section{Time Spent}
|
||||
\begin{figure}[h!]
|
||||
|
Binary file not shown.
@ -1 +1 @@
|
||||
3581
|
||||
3971
|
||||
|
Loading…
x
Reference in New Issue
Block a user