diff options
Diffstat (limited to 'cv.tex')
-rw-r--r-- | cv.tex | 87 |
1 files changed, 50 insertions, 37 deletions
@@ -1,6 +1,8 @@ -%! TEX program = xelatex -\documentclass[a4paper,11pt]{article} -\usepackage{array, fancyhdr, color, fontspec, parskip, tikz, ulem, xcolor} +\documentclass[a4paper,10pt,margin=0.5in]{article} +\usepackage{array, fancyhdr, color, fontspec, titlesec, parskip, tikz, ulem, + xcolor, longtable, titling, supertabular} +\usepackage{blindtext} +\usepackage{enumitem} \usepackage[linkcolor=magenta, colorlinks=true]{hyperref} \usepackage[margin=1.5cm, bottom=0.15cm, top=0.15cm]{geometry} \hypersetup{ @@ -22,45 +24,55 @@ \pagestyle{fancy} \fancyhf{} -\title{\bfseries\Huge Olivia Mackintosh} +\title{\bfseries\Huge Olivia\linebreak Mackintosh} \author{\href{mailto:livvy@base.nu}{livvy@base.nu}} -\date{} +\date{2} \makeatletter \def\@maketitle{% - \begin{center} \hrule height \z@ % to avoid lineskip - {\LARGE \center\protect{\@title}\par}% - {\large\lineskip .5em\@author\par} + \parbox{.50\textwidth}{\LARGE \protect{\@title}\par} + \parbox{.50\textwidth}{ + \begin{flushright} + \large\lineskip.5em\@author\par + \large\lineskip.5em\href{https://base.nu/}{https://base.nu}\par + \end{flushright} + } \vskip 1.0em } \begin{document} \maketitle -A software engineer of 8 years with a passion for delivering business results -though software. +\begin{minipage}[t]{0.55\textwidth} +A software engineer of 8 years with a passion for delivering business result +though software. Often utilizing test-first, iterative development. There's a lot of waste in our industry and we need to become better at building the right thing, and delivering it faster. Iterative development alongside techniques such as TDD, pair-programming can often unlock a lot of value, yet -teams have struggled to implement this properly due to a lack of support -regarding deployment pipelines and infrastructure as well as a lack of -experience with the test-first approach. Perhaps this sounds familiar for your -company? - -\section{Technical Skills} -C/Python/JS/Haskell/Kotlin/SQL/{\LaTeX} | TDD | Refactoring | Build Systems | -Infrastructure-as-Code | Deployment Pipelines | AWS | API Design | Frontend Dev -| UNIX/Linux Systems | Protocol Knowledge (HTTP, SMTP, USB in particular) +teams have struggled to implement this properly due to alack of support +regarding deployment pipelines and infrastructure; a lack of experience with the +test first approach and communication gaps. Perhaps this sounds like a familar +experience in your company? +\end{minipage} +\hfill +\begin{minipage}[t]{0.4\textwidth} + \begin{description} + \item [Languages:]\hfill\\ C, Python, JS, Haskell, Kotlin, SQL, {\LaTeX} + \item [Skills]\hfill\\ TDD, Refactoring + \item [Dev]\hfill\\ API Design, Frontend Dev + \item [Ops]\hfill\\ AWS, Azure, Infrastructure-as-Code, Deployment Pipelines + \item [Specialist]\hfill\\ UNIX/Linux Systems | Protocol Knowledge (HTTP, SMTP, USB in particular) + \end{description} +\end{minipage} \section{Professional Experience} -\begin{tabular}{L!{\VRule}R} - - 2022- &{\bf Klima.Metrix GmbH - Senior Software Engineer}\\ +\begin{supertabular}{ccc} + 2022- &{\bf Klima.Metrix GmbH — Senior Software Engineer}\\ &{\begin{itemize} \item Joined Klima.Metrix: a carbon accounting startup. \item Introduced and champtined a trunk-based, test-driven approoch to reduce deployment frequency to <1 week. \item Refactored legacy calculation code with BDD style tests that stakeholders can understand and give feedback on - \item Deprecated MongoDB backend service to reduce technical debt and to take advantage of the existing relational DB. Created custom tooling to make this easier + \item Deprecated MongoDB backend service to reduce technical debt and to take advantage of the existing relational DB.\@ Created custom tooling to make this easier \item OWASP top 10-based security audit + fixes \end{itemize}}\\ @@ -68,9 +80,10 @@ Infrastructure-as-Code | Deployment Pipelines | AWS | API Design | Frontend Dev &{\begin{itemize} \item Contract work with YLD and Uphold \item 50/50 consuting dev role + \item Microservice architecture \end{itemize}}\\ - 2017--2020 &{\bf Co-op Digital - Senior Software Engineer}\\ + 2017--2020 &{\bf Co-op Digital — Senior Software Engineer}\\ &{\begin{itemize} \item Joined the Digital Engineering department within the HQ of The Co-operative Group in 2017. @@ -88,8 +101,8 @@ React often providing development frameworks. These are software craftmanship and public speaking workshops respectively. \end{itemize}}\\ - - 2016--2017 &{\bf Beautiful Destinations - Software + \pagebreak + 2016--2017 &{\bf Beautiful Destinations — Software Engineer (Contract)}\\ &{\begin{itemize} \item Towards the end of 2016 I were hired by a @@ -99,26 +112,26 @@ industry. I were responsible for making machine learning code production ready (testing, QA, refactoring); setting up build/test/deploy pipelines; containerizing releases with Docker etc. - \item Introduced into Haskell as this was -used heavily for creating type-safe front/backends. Haskell and FP -remain influential and encouraged me to learn Haskell proper as well as -study Category Theory in my spare time. + \item Learnt Haskell/GHCJS as this was used heavily for enforcing +type-safety across the front-add-back end. Haskell and FP remain influential +and encouraged me to learn Haskell proper as well as study Category Theory in my +spare time. \end{itemize}}\\ - 2016 &{\bf Liberal Democrats - Software Engineer (Contact)}\\ + 2016 &{\bf Liberal Democrats — Software Engineer (Contact)}\\ -\end{tabular} +\end{supertabular} \section{Open Source Contributions} \begin{tabular}{L!{\VRule}R} - Linux Kernel & Supporting Pioneer audio mixers within ALSA: the - Linux audio subsystem. Reverse engineered the DJM-750 vendor + Linux Kernel & Supporting Pioneer audio mixers within ALSA:\@ the + Linux audio subsystem. Reverse engineered the DJM-750 vendor specific audio interface with OpenVizsla/ViewSB and collaborated with other users to expand support for other models.\\\\ - K9-Mail & Implementing IETF RFC6186: "Use of SRV Records for - Locating Email Submission/Access Services" as part of an - improved on-boarding experience. + K9-Mail & Implementing IETF RFC6186: `Use of SRV Records for + Locating Email Submission/Access Services' as part of an + improved setup experience. \end{tabular} %\section{Education} |