You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
203 lines
7.8 KiB
TeX
203 lines
7.8 KiB
TeX
% Options for packages loaded elsewhere
|
|
\PassOptionsToPackage{unicode}{hyperref}
|
|
\PassOptionsToPackage{hyphens}{url}
|
|
|
|
\documentclass[
|
|
]{article}
|
|
\usepackage{amsmath,amssymb}
|
|
\usepackage{titlesec}
|
|
\usepackage{titling}
|
|
\usepackage{lmodern}
|
|
\usepackage{xcolor}
|
|
\usepackage{iftex}
|
|
\usepackage[margin=1in]{geometry}
|
|
\ifPDFTeX
|
|
\usepackage[T1]{fontenc}
|
|
\usepackage[utf8]{inputenc}
|
|
\usepackage{textcomp} % provide euro and other symbols
|
|
\else % if luatex or xetex
|
|
\usepackage{unicode-math}
|
|
\defaultfontfeatures{Scale=MatchLowercase}
|
|
\defaultfontfeatures[\rmfamily]{Ligatures=TeX,Scale=1}
|
|
\fi
|
|
% Use upquote if available, for straight quotes in verbatim environments
|
|
\IfFileExists{upquote.sty}{\usepackage{upquote}}{}
|
|
\IfFileExists{microtype.sty}{% use microtype if available
|
|
\usepackage[]{microtype}
|
|
\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts
|
|
}{}
|
|
\makeatletter
|
|
\@ifundefined{KOMAClassName}{% if non-KOMA class
|
|
\IfFileExists{parskip.sty}{%
|
|
\usepackage{parskip}
|
|
}{% else
|
|
\setlength{\parindent}{0pt}
|
|
\setlength{\parskip}{1pt plus 2pt minus 1pt}}
|
|
}{% if KOMA class
|
|
\KOMAoptions{parskip=half}}
|
|
\makeatother
|
|
\definecolor{myblue}{RGB}{24, 102, 201}
|
|
\titleformat{\section}
|
|
{\huge\bfseries\color{myblue}}
|
|
{}
|
|
{0em}
|
|
{}[\titlerule]
|
|
|
|
\titleformat{\subsection}
|
|
{\Large\bfseries}
|
|
{}
|
|
{0em}
|
|
{}
|
|
|
|
\titleformat{\subsubsection}[runin]
|
|
{\bfseries}
|
|
{}
|
|
{0em}
|
|
{}[:]
|
|
|
|
\titlespacing{\subsubsection}
|
|
{0em}{0.75em}{0.5em}
|
|
|
|
\titlespacing{\subsection}
|
|
{0em}{1em}{0.65em}
|
|
|
|
\titlespacing{\maketitle}
|
|
{0em}{0em}{0em}
|
|
\renewcommand{\maketitle}{
|
|
\begin{center}
|
|
{\huge\bfseries \theauthor}\\
|
|
\vspace{.35em}
|
|
sufyaan.me/ovsk
|
|
\end{center}
|
|
}
|
|
\usepackage{color}
|
|
\usepackage{fancyvrb}
|
|
\newcommand{\VerbBar}{|}
|
|
\newcommand{\VERB}{\Verb[commandchars=\\\{\}]}
|
|
\DefineVerbatimEnvironment{Highlighting}{Verbatim}{commandchars=\\\{\}}
|
|
% Add ',fontsize=\small' for more characters per line
|
|
\newenvironment{Shaded}{}{}
|
|
\newcommand{\AlertTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{#1}}}
|
|
\newcommand{\AnnotationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{#1}}}}
|
|
\newcommand{\AttributeTok}[1]{\textcolor[rgb]{0.49,0.56,0.16}{#1}}
|
|
\newcommand{\BaseNTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{#1}}
|
|
\newcommand{\BuiltInTok}[1]{\textcolor[rgb]{0.00,0.50,0.00}{#1}}
|
|
\newcommand{\CharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{#1}}
|
|
\newcommand{\CommentTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textit{#1}}}
|
|
\newcommand{\CommentVarTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{#1}}}}
|
|
\newcommand{\ConstantTok}[1]{\textcolor[rgb]{0.53,0.00,0.00}{#1}}
|
|
\newcommand{\ControlFlowTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{#1}}}
|
|
\newcommand{\DataTypeTok}[1]{\textcolor[rgb]{0.56,0.13,0.00}{#1}}
|
|
\newcommand{\DecValTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{#1}}
|
|
\newcommand{\DocumentationTok}[1]{\textcolor[rgb]{0.73,0.13,0.13}{\textit{#1}}}
|
|
\newcommand{\ErrorTok}[1]{\textcolor[rgb]{1.00,0.00,0.00}{\textbf{#1}}}
|
|
\newcommand{\ExtensionTok}[1]{#1}
|
|
\newcommand{\FloatTok}[1]{\textcolor[rgb]{0.25,0.63,0.44}{#1}}
|
|
\newcommand{\FunctionTok}[1]{\textcolor[rgb]{0.02,0.16,0.49}{#1}}
|
|
\newcommand{\ImportTok}[1]{\textcolor[rgb]{0.00,0.50,0.00}{\textbf{#1}}}
|
|
\newcommand{\InformationTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{#1}}}}
|
|
\newcommand{\KeywordTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{\textbf{#1}}}
|
|
\newcommand{\NormalTok}[1]{#1}
|
|
\newcommand{\OperatorTok}[1]{\textcolor[rgb]{0.40,0.40,0.40}{#1}}
|
|
\newcommand{\OtherTok}[1]{\textcolor[rgb]{0.00,0.44,0.13}{#1}}
|
|
\newcommand{\PreprocessorTok}[1]{\textcolor[rgb]{0.74,0.48,0.00}{#1}}
|
|
\newcommand{\RegionMarkerTok}[1]{#1}
|
|
\newcommand{\SpecialCharTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{#1}}
|
|
\newcommand{\SpecialStringTok}[1]{\textcolor[rgb]{0.73,0.40,0.53}{#1}}
|
|
\newcommand{\StringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{#1}}
|
|
\newcommand{\VariableTok}[1]{\textcolor[rgb]{0.10,0.09,0.49}{#1}}
|
|
\newcommand{\VerbatimStringTok}[1]{\textcolor[rgb]{0.25,0.44,0.63}{#1}}
|
|
\newcommand{\WarningTok}[1]{\textcolor[rgb]{0.38,0.63,0.69}{\textbf{\textit{#1}}}}
|
|
\setlength{\emergencystretch}{3em} % prevent overfull lines
|
|
\providecommand{\tightlist}{%
|
|
\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}
|
|
\setcounter{secnumdepth}{-\maxdimen} % remove section numbering
|
|
\ifLuaTeX
|
|
\usepackage[bidi=basic]{babel}
|
|
\else
|
|
\usepackage[bidi=default]{babel}
|
|
\fi
|
|
\babelprovide[main,import]{english}
|
|
% get rid of language-specific shorthands (see #6817):
|
|
\let\LanguageShortHands\languageshorthands
|
|
\def\languageshorthands#1{}
|
|
\ifLuaTeX
|
|
\usepackage{selnolig} % disable illegal ligatures
|
|
\fi
|
|
\IfFileExists{bookmark.sty}{\usepackage{bookmark}}{\usepackage{hyperref}}
|
|
\IfFileExists{xurl.sty}{\usepackage{xurl}}{} % add URL line breaks if available
|
|
\urlstyle{same} % disable monospaced font for URLs
|
|
\hypersetup{
|
|
pdftitle={(POST) Oversimplification Kills},
|
|
pdflang={en},
|
|
colorlinks=true,
|
|
linkcolor=blue,
|
|
filecolor=blue,
|
|
urlcolor=blue,
|
|
pdfcreator={LaTeX via pandoc}}
|
|
|
|
\title{Sufyaan's Website}
|
|
\author{Sufyaan's Website}
|
|
\date{}
|
|
|
|
\begin{document}
|
|
\maketitle
|
|
|
|
\section[Oversimplification Kills]{Oversimplification Kills}\label{why-i-use-terminal-apps}
|
|
|
|
\textbf{10 July 2023}
|
|
|
|
|
|
\textbf{Category: }Software
|
|
|
|
Oversimplification kills. It is as simple as that. Most of the time,
|
|
there are simple solutions to a problem that work well which are not
|
|
used because individuals feel like they need to be more simple.
|
|
|
|
If you want to get more technical, think about the over-engineering of
|
|
website builders. Instead of having a simple piece of software that
|
|
generates static sites and blog posts based on
|
|
\href{sufyaan.me/definitions/markdown}{markdown} files, we have ultra-bloated
|
|
website builders that provide a simple way to make a website at the cost
|
|
of extremely slow websites and unneeded JavaScript. We also have
|
|
oversimplified user interfaces in Windows and MacOS. These
|
|
\href{sufyaan.me/definitions/operating-system}{operating systems} have made bad
|
|
and oversimplified interfaces a norm, which makes good interfaces such
|
|
as ones you can customize on Linux seem too complicated or confusing
|
|
even though it would be easier for someone with no experience in
|
|
computing to get started with most desktop environments available.
|
|
|
|
As
|
|
\href{https://lukesmith.xyz/articles/obvious-technical-solutions/}{Luke
|
|
Smith mentions in his post,} we never thought about using wheels on
|
|
suitcases until the 1990s even though children in the Incan empire did
|
|
have toys with wheels. This is one of the examples where trying to
|
|
oversimplify something by making an all-in-one or a good solution delays
|
|
progress.
|
|
|
|
Oversimplification shifts focus away from the main problem. For example,
|
|
with website builders, the problem shifted away from being able to make
|
|
websites fast and easily to give the user information in a swift manner
|
|
to just making your website pretty. With Windows and MacOS, the focus
|
|
shifted away from making user interfaces that actually make sense for
|
|
everyone to use to making user interfaces that are familiar.
|
|
|
|
On the other end of the same spectrum, overcomplication also has a
|
|
similar result. A technical example of this is software management.
|
|
Windows and MacOS (at least how most people use MacOS) have complicated
|
|
software management which results in difficult updates, confusing
|
|
software usage and an overall increase in storage usage throughout the
|
|
years. However, Linux has package managers. One command is all that is
|
|
required to install a package and remove it. You can clear cache,
|
|
download an older version, update both your system and applications at
|
|
the same time and even view all installed packages.
|
|
|
|
In the end, most things are complicated. We can try simplifying them and
|
|
that is perfectly fine. However, trying to oversimplify a problem and
|
|
making it a binary outcome does not work in all cases. There are many
|
|
factors to take into consideration. Oversimplification leads to no
|
|
problems being solved. If anything, it creates and solves arbitrary
|
|
problems that are not important.
|
|
|
|
\end{document}
|