\input prelude

\pageheight=11in
\pagewidth=8.5in
%\voffset=-0.4in
%\vsize=9.5in
\voffset=-0.5in
\vsize=10.5in

\nopagenumbers

\def\header{%
\centerline{{\hf Michael Stone}}%
\vskip -5pt%
\centerline{\leaders\hrule\hskip 12cm}%
\centerline{\vbox{{\halign{##\hfil&\qquad\qquad\hfil##\hfil&\qquad\qquad\hfil##\cr%
Cambridge, MA       & \href{http://mstone.info}{mstone.info} | \hhref{https://github.com/mstone}{{\gh}\hskip0.5ex mstone} | \hhref{https://mastodon.online/mstone}{{\color{dkpurple}\lower 0.05em\hbox{\mstdn}}\hskip0.4ex mstone} | {\it he, him}       & December 2022              \cr}}}}%
}

\header

% \def\job#1#2#3{\smallskip \goodbreak {\parindent=0pt \halign to \hsize{\jtf##\hfil&, \jpf##\hfil\tabskip=0pt plus 1 fil&\tabskip=0pt\hfil\jdf##\cr#2&#3&#1\cr}}\par}
\def\model#1#2{\smallskip {\mh \parindent=0pt {\jtf #1}\rm: #2\par}}

\def\jobb#1#2#3{\bf#2\hskip0.5em\hfil&\hskip0.5em\it#3\hskip0.5em\hfil&\hfil#1\cr}

\sect{\ul{Trajectory}}{
  \medskip \centerline{\vbox{\baselineskip=12.5pt \halign{#&#&#\cr
  %\jobb{\jdf year}{\jdf title}{}{}
  \jobb{2022}{Author{\rm, \href{https://github.com/mstone/depict/}{depict}}}{``Operadic Systems''}
  \jobb{2009-2021}{Chief Architect {\rm (from Senior Researcher)}}{Akamai Technologies, Inc.}
  \jobb{2007-2009}{Release Manager {\rm (from Software Developer)}}{One Laptop per Child}
  \jobb{\hfil2007}{BA with High Honors{\rm, Math \& Statistics + English}}{Swarthmore College}
  }}}

}

\def\back{\hskip -1.1em}

\sect{\ul{Accomplishments}}{
  \medskip \job{}{As the Chief Security Architect at Akamai}{I led, sponsored, and supervised:}

    \mh ...Akamai's technical security approach, team, and policy, including its decision to bet on \href{http://mit.edu/psas}{STAMP} for \ul{\bf overall system safety} {\it including} security. This non-obvious choice helped preserve the company and the well-functioning of the Web through 4x growth of the company, exponential growth of traffic served, and the challenges of the early years of the COVID-19 pandemic.

  \medskip \job{}{As a People Manager and Director at Akamai}{I supported and developed:}

    \mh ...six staff who I hired, two more who came to me via assignment, and
      many others elsewhere in the company through example and influence. Since
      working with me, these immediate colleagues have been promoted to titles
      including Senior Researcher, Architect, and Senior/Principal/Chief
      Architect.

  \medskip \job{}{As a Process Owner at Akamai}{I overhauled:}

    \mh ...Akamai's approach to technical incident \& crisis management. Here, I introduced new training and `blame-aware' retrospectives, built new tooling, lead dozens of engagements and incident reviews some of which changed the direction of the company, and evolved new approaches to incident process governance.

  \medskip \job{}{As a Systems Architect at Akamai}{I built:}

    \mh ...a {\jdf codesearch} system trusted by
    incident responders, a {\jdf log search} prototype that proved to the
    responsible engineering team that Akamai's logs could reasonably be
    searched and indexed, and the {\jdf incidents} information fusion system
    used daily by Akamai's incident responders to manage their response efforts.

  \medskip \job{}{As a Security Researcher and Incident Responder at Akamai}{I personally:}
    \mh ...provided expert security advice for dozens of Akamai systems including during internet-wide security crises like Heartbleed and Shellshock. Later, I also built the {\jdf vscan} malware scanning system to scan Akamai's production storage array and I joined and led Akamai's 24x7x365 team of ``incident managers of last resort''.

  \medskip \job{}{As a Release Manager at OLPC}{I launched:}
    \mh ...a new release process that shipped changes that
    closed approximately 1,000 tickets, including a complete UI redesign, over
    the following 34 weeks.  The release shipped within 6 weeks of the target
    month to positive reviews on Amazon and in the OLPC software community.

  \medskip \job{}{As a Software Developer at OLPC}{I designed and shipped:}
    \mh ...portions of OLPC's ``Bitfrost'' security system including
    its activity isolation framework, parts of its software theft deterrence
    system, and its secure update system. This work addressed the technical
    problem of safeguarding the education of hundreds of thousands of children
    and the commercial problem of convincing governments to purchase
    Linux-based educational laptops.

  \medskip \goodbreak {\parindent=0pt \halign to \hsize{\kern2em#\hfil& #\hfil\tabskip=0pt plus 1 fil&\it#&\tabskip=0pt\hfil#\cr
  \omit{\bf As a Speaker}{\rm,} {\it I presented:} \hfil & {\jdf venue} & & {\jdf year} \cr
  \noalign{\vskip0.25em}
  \back \href{http://psas.scripts.mit.edu/home/wp-content/uploads/2020/07/STAMP-at-Akamai-2020-Edition-2.pdf}{STAMP at Akamai}  & MIT STAMP Workshop \& internally & invited & '20 \cr
  \back \href{http://mstone.info/posts/system-safety-psychology-20181204/}{System Safety $\cap$ Psychology}  & Tufts PSY 53, {\it Engineering Psychology} & invited & '18 \cr
  ``Keeping Watch'' & Akamai Program Management Summit \hskip 5em & invited & '17 \cr
  \back \href{http://mstone.info/posts/talk-atlas-20130327/}{An Atlas of Systems}  & MIT STAMP Workshop & & '13 \cr
  \back \href{http://mstone.info/posts/systems-thinking-in-web-security/}{Systems Thinking + Web Security}\hskip2em & MIT STAMP Workshop & & '10 \cr
  }}

}

\medskip

% unpracticed %rusty
\sect{\ul{Selected Skills \& Conversation Topics} \hfill \jdf \color{black} legend \hskip 0.5em \BBB current, \BB recent, \B nascent/lapsed}{
\medskip \centerline{\vbox{\baselineskip=12.5pt \halign{\hfil\jdf#&\hskip 0.5em\jdf#\hfil\cr
%people mgmt & & & \cr
programming & \BBB Rust, \BBB Nix, \BB Go, \BB C, \BB C++, \BB R, \BB Python, \BB Swift, \B Haskell, \B PHP, \B Lua, \B VHDL, \BB \TeX, \BB PyTorch \hfil \cr
%AI/ML       & \hskip0.5em \BB PyTorch, \BB NLProc, \BB LLMs, \BB HuggingFace, \BB rust-tokenizers, \BB BERT, \B AlphaZero \hfil \cr
%systems     & \rm \B code search, \B log search, \BB incident awareness, \BB dashboarding, \BBB software packaging, \BB debugging \cr
%processes   & \rm \BB incident response, \BBB incident debriefing, \BBB change management, \BB governance, \BB org design, \BB optimization \cr
web tech    & \BB XML, \BB HTML, \BB CSS, \BB SQL, \BB JS, \B RDF, \BB DNS, \BB HTTP, \BB TLS, \B SMTP, \B IMAP, \B XMPP, \B Atom, \B ActivityPub \cr
tools       & \BBB git, \BB sapling, \BB pijul, \BB p4, \BBB Make, \BB autotools, \BB klee, \BB LLVM IR, \B CPSA, \B Coq, \B Alloy, \B DIVINE, \BB Minion, \B Z3, \B Agda  \cr % \B s2e
networking     & \B IEEE 802, {\B}802.11b/g, \BB IPv4, \BB IPv6, \BB TCP, \BB UDP, \B AWS, \B Azure, \BB GCP   \cr
systems      & \BBB STPA, \BBB CAST, \BB intent specifications, \BB asking good questions, \BB finding answers, \BB history, \BB Wardley maps  \cr
math        & \BB algebra, \BB real analysis, \BB topology, \BB probability, \BB statistics, \BB queueing theory, \B control theory, \BB category theory         \cr
%topics      & \BBB reading, \BB games, \B plumbing, \BB travel, \BB law, \BB causality, \BBB planning, \BB empiricism, \BB cognition, \B conflict \cr
inspirations& \BBB Leveson, \BB Rickover, \B Boyd, \B Cook, \B Victor, {\it <<\ul{your inspiration here}?>>} \cr
}}}}

\end
