From 6fbb02d544e75a0e6b510c0e74967c6fa3aca9b8 Mon Sep 17 00:00:00 2001
From: Benedikt Galbavy <benedikt@galbavy.at>
Date: Tue, 14 Jan 2025 17:32:18 +0100
Subject: [PATCH] minor fixes

---
 slides.tex | 31 ++++++++++++++++---------------
 1 file changed, 16 insertions(+), 15 deletions(-)

diff --git a/slides.tex b/slides.tex
index 600bd07..4648aff 100644
--- a/slides.tex
+++ b/slides.tex
@@ -35,8 +35,8 @@
 \begin{frame}{Who are we?}
 \begin{itemize}
     \item Group of 5 people
-    \item 1 Semester of C++ Programming under our belt at the start
-    \item Common interest: C++ Programming + game development
+    \item 1 Semester of C++ programming under our belt at the start
+    \item Common interest: C++ programming + game development
 \end{itemize}
 \end{frame}
 \subsection{The project}
@@ -50,10 +50,10 @@
 \begin{frame}{Our interpretation and goals}
 \begin{itemize}
     \item Started out with a Minigame
-    \item Realized we can split it into \enquote{Engine} and \enquote{Game Specific} Content
-    \item Goal: make easy to use engine without GUI \Rightarrow essentially a game dev lib
+    \item Realized we can split it into \enquote{Engine} and \enquote{Game Specific content}
+    \item Goal: make easy to use engine without GUI
 \end{itemize}
-    \Rightarrow We could then build on what we have while simultaneously having an implementation using the engine as proof of concept
+    \Rightarrow We could then build an engine from existing code while using our game as a proof of concept for the engine
     
     Smart right :D ?\dots
 \end{frame}
@@ -64,26 +64,27 @@
     In other words, quite a messy endeavor\dots
 \end{frame}
 \begin{frame}{Roadmap}
-\nth{3} Semester - learning SDL and the principles of game development
+\nth{3} semester - learning SDL and the principles of game development
 
-\nth{4} and \nth{5} Semester - making the engine
+\nth{4} and \nth{5} semester - making the engine
 
-At this point we were certain this would be a walk in the park as it would essentially *just* be some refactoring, right?.
+At this point we were certain this would be a walk in the park as it would essentially *just* be some refactoring, right?
 \end{frame}
 \note[itemize]{
-    \item Somewhere around this time we realized there was more to compiling a C++ program than pressing
-          the run button in Visual Studio.
+    \item Somewhere around this time we realized there was more to compiling a C++ program than pressing the run button in Visual Studio.
     \item (subtle foreshadowing about how using VS set us back many many hours :,))
     \item There was quite the naive optimism at the end of this semester (i.e wheeee we made a whole game on our own we are unstoppable :D)
     \item (about 4th/5th semester): separating the project into the game and the parts of the program that could be reused for other games.
 }
-\begin{frame}
-Realization: doing it right the first time is better than fixing it later.
 
-And no, don't "just start programming because the architecture will solve itself later"
+\begin{frame}{Overcoming naivety}
+Realization: Doing it right the first time is better than fixing it later.
+
+And no, don't \enquote{just start programming because the architecture will solve itself later}
 \end{frame}
 
 \section{Learnings}
+
 \begin{frame}[allowframebreaks, fragile]{Spaghetti, an example}
 \begin{itemize}
     \item Original Ticket: \enquote{Attack speed stat needs reimplementation}
@@ -161,8 +162,8 @@ void chickengame::pickupables::movementSpeedEffect(Entity* player)
 
 \begin{frame}{Baby's first \texttt{CMakeLists.txt}}
 \begin{itemize}
-    \item On UAS: Only \texttt{make} is taught, most subjects didn't have further requirements for project setup
-    \item CMake is good documented, works out of the box with most IDEs, is directly supported by all used libraries
+    \item At UAS: Only \texttt{make} is taught, most subjects didn't have further requirements for project setup
+    \item CMake is well documented, works out of the box with most IDEs, is directly supported by all used libraries
 \end{itemize}
 \end{frame}
 \note[itemize]{