Beamer Pittsburgh

\documentclass[10pt]{beamer}
\usetheme{Pittsburgh}
\usecolortheme{beaver}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{amsmath,amssymb}
\usepackage{graphicx}
\usepackage{booktabs}
\usepackage{hyperref}

\title{The Case for Research Software Engineers}
\subtitle{Pittsburgh Theme Demo}
\author{First Last}
\institute[Example U]{Department of Computer Science \\ University of Example}
\date{\today}

\begin{document}

\frame{\titlepage}

\begin{frame}{Outline}
\tableofcontents
\end{frame}

\section{Motivation}
\begin{frame}{Why This Matters}
\begin{itemize}
  \item Scientific software is often fragile and undocumented.
  \item Research Software Engineers (RSEs) bridge the gap.
  \item The community is growing quickly across Europe, the US, and Asia.
\end{itemize}
\end{frame}

\begin{frame}{A Familiar Situation}
\begin{itemize}
  \item PhD students write ``prototype'' code that ends up in production.
  \item Maintenance falls through the cracks after graduation.
  \item Reproducibility suffers.
\end{itemize}
\end{frame}

\section{What RSEs Do}
\begin{frame}{Core Responsibilities}
\begin{enumerate}
  \item Build and maintain research software.
  \item Apply software engineering practices (CI, tests, docs).
  \item Train researchers in modern development tooling.
  \item Co-author papers on methods and tools.
\end{enumerate}
\end{frame}

\begin{frame}{A Day in the Life}
\begin{columns}
  \column{0.5\linewidth}
  \textbf{Morning:}
  \begin{itemize}
    \item Pair-program with a PhD student.
    \item Review a pull request.
    \item Triage GitHub issues.
  \end{itemize}
  \column{0.5\linewidth}
  \textbf{Afternoon:}
  \begin{itemize}
    \item Benchmark a numerical kernel.
    \item Write user-facing documentation.
    \item Lead a Python workshop.
  \end{itemize}
\end{columns}
\end{frame}

\section{Results}
\begin{frame}{Impact Across Groups}
\begin{table}
\centering
\begin{tabular}{lcc}
\toprule
Group & Papers/yr (before) & Papers/yr (after) \\
\midrule
Group A & 4  & 7 \\
Group B & 6  & 10 \\
Group C & 3  & 6 \\
\bottomrule
\end{tabular}
\end{table}
Embedded RSEs correlate with a $\sim 70\%$ increase in publication output.
\end{frame}

\section{Getting Started}
\begin{frame}{Build an RSE Culture}
\begin{itemize}
  \item Hire RSEs on long-term contracts, not per-project.
  \item Credit them as co-authors.
  \item Create career pathways distinct from tenure track.
\end{itemize}
\end{frame}

\begin{frame}{Further Reading}
\begin{itemize}
  \item \texttt{society-rse.org}
  \item \texttt{us-rse.org}
  \item The Turing Way handbook.
\end{itemize}
\end{frame}

\begin{frame}{Thank You}
\centering
\Huge Questions?\\[1em]
\normalsize [email protected]
\end{frame}

\end{document}