\@writefile{toc}{\contentsline{subsection}{\numberline{2.3.1}Where does the Unix Principle actually apply in real life?}{15}{subsection.2.3.1}\protected@file@percent }
\@writefile{toc}{\contentsline{subsection}{\numberline{2.3.2}Where else does the Unix Principle \textit{not} apply that it probably should in real life?}{17}{subsection.2.3.2}\protected@file@percent }
\@writefile{toc}{\contentsline{subsection}{\numberline{2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{19}{subsection.2.3.3}\protected@file@percent }
\@writefile{toc}{\contentsline{chapter}{\numberline{3}What Are All Those Files in the Linux Root?}{20}{chapter.3}\protected@file@percent }
\@writefile{toc}{\contentsline{subsection}{\numberline{2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{20}{subsection.2.3.3}\protected@file@percent }
\@writefile{toc}{\contentsline{chapter}{\numberline{3}What Are All Those Files in the Linux Root?}{21}{chapter.3}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.1}A Scanner Darkly, but with a workflow}{25}{section.4.1}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.2}Is This Really a Hack? Or Is It Just a Tip?}{25}{section.4.2}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.3}What I Learned About \LaTeX\tmspace +\thinmuskip{.1667em} While Creating This Issue}{28}{section.4.3}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.1}A Scanner Darkly, but with a workflow}{26}{section.4.1}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.2}Is This Really a Hack? Or Is It Just a Tip?}{26}{section.4.2}\protected@file@percent }
\@writefile{toc}{\contentsline{section}{\numberline{4.3}What I Learned About \LaTeX\tmspace +\thinmuskip{.1667em} While Creating This Issue}{29}{section.4.3}\protected@file@percent }
\contentsline{subsection}{\numberline{2.3.1}Where does the Unix Principle actually apply in real life?}{15}{subsection.2.3.1}%
\contentsline{subsection}{\numberline{2.3.2}Where else does the Unix Principle \textit{not} apply that it probably should in real life?}{17}{subsection.2.3.2}%
\contentsline{subsection}{\numberline{2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{19}{subsection.2.3.3}%
\contentsline{chapter}{\numberline{3}What Are All Those Files in the Linux Root?}{20}{chapter.3}%
\contentsline{subsection}{\numberline{2.3.3}Where does the Unix Principle not apply in real life and this is actually a good thing?}{20}{subsection.2.3.3}%
\contentsline{chapter}{\numberline{3}What Are All Those Files in the Linux Root?}{21}{chapter.3}%
@ -326,10 +326,14 @@ When I was a kid, we were given a microwave oven as a gift. It included a cookbo
Alas, I have no idea how a beef roast cooked in the microwave oven tastes. Nor do I want to know.
You'll notice that I left ``thawing out frozen food'' off that list. Have you ever tried to defrost anything in the microwave oven? It's an utter failure, with half of it still being frozen, and the other half being mostly thawed with overcooked inedible bits at the edges, with an odd liquid slowly coagulating on the plate below. No, thank you. The best way to thaw out frozen foods is to plan ahead and throw them in the refrigerator the night before. But in a society which does not encourage us to think—indeed, we are often discouraged from thinking—we are taught to think that defrosting in a microwave is a good alternative.
You'll notice that I left ``thawing out frozen food'' off that list. Have you ever tried to defrost anything in the microwave oven? It's an utter failure, with half of it still being frozen, and the other half being mostly thawed with overcooked inedible bits at the edges, with an odd liquid slowly coagulating on the plate below. No, thank you. The best way to thaw out frozen foods is to plan ahead and throw them in the refrigerator the night before. But in a society which does not encourage us to think—indeed, we are often discouraged from thinking—we are taught to think that defrosting food in a microwave is a good alternative.
It is not.
But we are enthralled with the \textit{illusion} of choice. Most people will not buy a microwave oven with only one or two buttons, even though in reality, that is all you need: one control for how long and another control for how high. My current microwave has only three buttons that I use on a regular basis: 1 minute cook, 2 minute cook, and add 30 seconds. It also has a 3 minute cook, a 5 minute cook, `Popcorn,' `Beverage,' `Reheat,' `Potato,' `Reheat,' `Delay Start' (why, praytell, are you delaying the start in a device whose entire point is 'right here, right now'?), `Defrost,' `Timer,' `Reminder,' and a host of other buttons for setting the clock, adjusting whether it's AM or PM, etc, in addition to `Start' (highly useful if you're not using the 1 minute cook button) and `Cancel' which I don't use because I just run out the clock. If you pull out food before the timer runs out, the oven keeps giving you a message on the screen that you still have time on the clock. Any well-designed microwave oven should just time out that message after five minutes.
Again, we are enthralled with the illusion of choice, and actually devote time and resources to it, even though they could probably be better spent elsewhere. Case in point: Every microwave oven has a `Popcorn' button, but every packet of microwave popcorn has an instruction telling you explicitly \textit{not} to use the `Popcorn' button. Something does not align here.
\subsection{Where does the Unix Principle not apply in real life and this is actually a good thing?}
\textbf{Instant Pots (and to a lesser degree, multicookers)}
@ -454,6 +458,14 @@ I suppose I should have been an archivist.
tips about pdftk. (What were these? from the man pages.)
\begin{verbatim}
$ pdftk A=001a.pdf B=001b.pdf shuffle A B output 001.pdf
\end{verbatim}
\begin{verbatim}
$ pdftk A=001a.pdf B=001b.pdf shuffle A Bend-1 output 001.pdf
\end{verbatim}
\section{Is This Really a Hack? Or Is It Just a Tip?}
The word ``hacker'' has a lot of definitions, and if you just google it, you'll find a lot of scary ones on the websites of companies that want you to be scared of ``hackers'' and then spend hundreds of dollars on their security products, some of which may actually protect you against actual threats, and some of which may provide protection against a threat which isn't actually real.
@ -498,6 +510,7 @@ I'm still a relative newbie to LaTeX, so there's always something to learn. Here
\item Use the \textbf{fancyhdr} package to get more granular control over your headers and footers.
\item You can use the \textbf{geometry} package to make a document have a paper size of half letter (i.e., 5.5 inches by 8.5 inches).
\item You can make your top margin larger by using \verb|\addtolength| \\\verb|{\topmargin}{0.5in}| but there is not a similar parameter for the bottom margin. Instead, you need to make the text box shorter by using \verb|\addtolength{\textheight}{-1in}|.
\item Want to show code blocks? Use the \\\verb|\begin{verbatim} code block| \verb|\end{verbatim}| \\ construction. (Line breaks are up to you.)
\item Want to show inline code without executing it? Use \verb|verb| followed by two pipes. Place your code between the pipes. (I had to use two of those in \#7, because that code just went right off the edge of the page when I only used one.)
\item Need a little space between elements? Just insert \verb|\,| (that is, a backslash followed by a comma). (This is actually a non-breaking space, so use it judiciously.)
\item Footnotes reset back to the number one with each chapter. To prevent that, add \verb|\counterwithout{foootnote}{chapter}| to the preamble.