Updates to «Coda»

006/006 time.csv

@@ -24,3 +24,6 @@ Date,Topic,Minutes
 ,,15
 ,,60
 ,,60
+,,55
+,ch. 2 edits, 20
+2025.02.09,barcodes,60

006/codex-006.tex

@@ -28,7 +28,6 @@
 \usepackage{microtype} % Make things neater. Thanks /u/-LeopardShark-
 \usepackage{tabularray} % Easy tables
 \usepackage[defaultsans]{Cantarell} % sans-serif font; https://tug.org/FontCatalogue/firasansregular
-\usepackage[]{footmisc}
 
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

006/include/coda.tex

@@ -16,6 +16,11 @@ Protip: draw it on paper first.
 \fbox{\includegraphics[scale=0.30]{tikz-on-paper}}
 \end{center}
 
+\subsection{\texttt{include} is Your Friend}
+
+Last time around, I mentioned using \verb|\input{<filename>}| to keep your \LaTeX{} GUI happy. But I've also found that using \verb|\include{<filename>}| keeps \textit{me} happy. Creating this zine means I end up with a very long file (the file for issue \#5 was 1005 lines long!) making it time consuming to constanty scroll through the file to get to the last part I was editing. (It's not terrible in and of itself, but repeatedly having to do it impacts my overall efficiency.) 
+
+For this issue, I decided to write up each chapter as a separate file, and then just \texttt{include} that file into my main document. This makes it much easier to manage, and I do feel more efficient. But because I'm using a GUI (Texmaker) I do have to remember to switch back to my main file when I compile the document. Overall, that's a trade-off I can live with. 
 
 %\newpage % Use only to keep the afterword together if we end up with orphans
 \section{Afterword}