asboyer · asboyer · Apr 30, 2026 · Apr 30, 2026
diff --git a/lmc_portfolio/analysis.html b/lmc_portfolio/analysis.html
@@ -0,0 +1,143 @@
+<!doctype html>
+<html lang="en">
+    <head>
+        <meta charset="UTF-8" />
+        <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+        <title>Self-Assessment Analysis | Andrew Boyer</title>
+        <link rel="preconnect" href="https://fonts.googleapis.com" />
+        <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
+        <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet" />
+        <link rel="stylesheet" href="assets/styles.css" />
+    </head>
+    <body>
+        <nav class="nav">
+            <div class="nav-inner">
+                <a href="index.html" class="nav-brand">Andrew Boyer · <span class="accent">LMC 3403</span></a>
+                <ul class="nav-links">
+                    <li><a href="index.html">Home</a></li>
+                    <li><a href="analysis.html" class="active">Analysis</a></li>
+                    <li><a href="mp1.html">MP1</a></li>
+                    <li><a href="mp2.html">MP2</a></li>
+                    <li><a href="mp3.html">MP3</a></li>
+                    <li><a href="goatgrade.html">Goat Grade</a></li>
+                    <li><a href="spotify.html">Spotify App</a></li>
+                </ul>
+            </div>
+        </nav>
+
+        <main>
+            <span class="eyebrow">Self-Assessment</span>
+            <h1>Analysis</h1>
+            <p class="lead">
+                Looking back at my Video Pitch goals and how the four learning outcomes (Rhetoric, Process, Modes &amp; Media, and Design) played out
+                across the semester.
+            </p>
+
+            <h2>Video Pitch</h2>
+            <p>
+                In my Video Pitch, my goals were to translate technical concepts into clear language, adapt my messaging and emphasis for different
+                audiences, and create a technical crisis infographic. I met those goals across the three major projects. I also met each of the four
+                learning outcomes for the course.
+            </p>
+
+            <h2>Rhetoric</h2>
+            <p>
+                MP1 leaned hardest on considering the language for my audience and adapting my messaging and emphasis for different audience types. I
+                went through multiple revisions of my cover letter and thought carefully about the language I was using to describe my skills and
+                experience.
+            </p>
+            <p>I targeted a Software Engineer I role at Amazon. The cover letter opens by naming the role first, then pivots to my background:</p>
+            <blockquote>
+                "This position at Twitch as a Software Engineer I requires someone who will craft immersive experiences and scalable applications for
+                users. I believe my previous professional, project, and educational experiences make me a viable candidate for this job."
+            </blockquote>
+            <p>
+                I wanted the opening to prove I had read the job description. The body paragraph uses Amazon-specific vocabulary to signal cultural
+                fit:
+            </p>
+            <blockquote>
+                "This process acquainted me with Amazon's unique ecosystem of internal tools, like Brazil, Pipelines, and Cradle, as well as standard
+                software libraries like the AWS CDK."
+            </blockquote>
+            <p>
+                Brazil, Pipelines, and Cradle are internal Amazon tools. This would only resonate with someone who has worked at Amazon. I followed
+                this with a concrete impact metric:
+                <em
+                    >"Adoption of the tool would reduce operational overhead by 99.8%, saving the company hundreds of thousands of dollars per
+                    year."</em
+                >
+            </p>
+            <p>
+                The resume follows this same structure, with an action paired with an actual outcome.
+                <em>"Tool reduces operational overhead by 99.8%, saving $300,000 annually, built to scale with company-wide adoption."</em>
+            </p>
+            <p>I've done this professionally as well, from writing documentation at Ashvin AI, to writing a presentation I gave at Amazon.</p>
+
+            <h2>Process</h2>
+            <p>
+                For MP3, my team created training materials. The process involved discussion with teammates, getting everyone on the same page,
+                because we all had varying amounts of experience with Claude Code.
+            </p>
+            <p>
+                We split the six parts up, drafted in Google Docs, and went through multiple revisions. The feedback that mattered most was
+                considering audience, because readers would have varying degrees of experience with the tool, as well as general technology concepts.
+                starting points with the tool. We added notes for readers who had never used an LLM, like the question that opens the memory section
+                of Part 1:
+            </p>
+            <blockquote>
+                "Have you ever tried asking Claude too many questions, and suddenly it forgets about the first question you asked? This has to do with
+                a concept called context."
+            </blockquote>
+            <p>We also carried this through the remaining parts.</p>
+            <p>
+                I've also had to go through iterations of feedback, implementation, and improvement during my internships. Code review at Amazon and
+                Ashvin AI followed a similar process.
+            </p>
+
+            <h2>Modes and Media</h2>
+            <p>MP2 combined a report and a graphic. Both sources had to reinforce the same argument without repeating each other.</p>
+            <p>
+                The report is aimed at specialists, talking about company leadership, engineers, and regulators. It draws on Winsor's analysis of the
+                Challenger disaster and Grabill and Simmons' work on technocratic communication. It uses quotes straight from pilots. One captain
+                called the 737 Max manual <em>"inadequate and almost criminally insufficient"</em> and asked,
+                <em>"I am left to wonder: what else don't I know?"</em> Those quotes back up a specialist-facing argument: that excluding pilots from
+                MCAS documentation was a "technocratic" communication failure, where as Grabill and Simmons put it,
+                <em>"risk communicators strive to educate/influence the public to think about risk the way experts do."</em>
+            </p>
+            <p>
+                The infographic packages the same research for a public reader. It opens with the death toll and uses a timeline, breaking the
+                failures into three causes. We added the pilot quotes too, packaged with colors so the casual reader gets them before any of the
+                statistics. Our
+                <em>"Suppressed Internal Communication"</em> label says:
+                <em>"Communication requires shared interpretation, not just data,"</em> summarizing what we are trying to communicate.
+            </p>
+            <p>I've used different media in my internships, from documentation to presentations with graphics.</p>
+
+            <h2>Design</h2>
+            <p>
+                For MP3, we went with a website design style appealing to the eye. This is so it's easy to follow along and read technical commands,
+                while also quickly understanding if something is part of the core guide or a tip.
+            </p>
+            <p>
+                Code samples sit inside a card that gives a visual distinction to commands. The body font is Inter, while code is JetBrains Mono.
+                While this is subtle, it shows that font selection can be key to making an easy to follow technical guide.
+            </p>
+            <p>
+                In the infographic from MP2, we had to fit a whole crisis onto one page adding too much clutter. We added a timeline at the top,
+                setting up how the crisis progressed before getting into any text. The "Lessons" section at the bottom uses four colored circles
+                around a central question, <em>"How Future Disasters Can Be Prevented,"</em> to leave the reader with something actionable.
+            </p>
+
+            <h2>Closing</h2>
+            <p>
+                The Video Pitch goals I set in January (clear translation, audience adaptation, a public infographic) all show up across MP1, MP2, and
+                MP3. I learned a lot throughout the revision processes and getting feedback from classmates. My content would change after a review
+                would flag something and my final submissions improved because of this.
+            </p>
+        </main>
+
+        <footer class="footer">
+            <p>© 2026 Andrew Boyer · Built for LMC 3403 · Hosted on <a href="https://asboyer.com" target="_blank" rel="noopener">asboyer.com</a></p>
+        </footer>
+    </body>
+</html>
diff --git a/lmc_portfolio/assets/img/at_desk.png b/lmc_portfolio/assets/img/at_desk.png
diff --git a/lmc_portfolio/assets/img/headshot.jpeg b/lmc_portfolio/assets/img/headshot.jpeg
diff --git a/lmc_portfolio/assets/img/mp3-screenshot.png b/lmc_portfolio/assets/img/mp3-screenshot.png
diff --git a/lmc_portfolio/assets/img/nba.png b/lmc_portfolio/assets/img/nba.png
diff --git a/lmc_portfolio/assets/img/spotify.png b/lmc_portfolio/assets/img/spotify.png
diff --git a/lmc_portfolio/assets/pdf/mp1.pdf b/lmc_portfolio/assets/pdf/mp1.pdf
diff --git a/lmc_portfolio/assets/pdf/mp2-infographic.pdf b/lmc_portfolio/assets/pdf/mp2-infographic.pdf
diff --git a/lmc_portfolio/assets/pdf/mp2-report.pdf b/lmc_portfolio/assets/pdf/mp2-report.pdf
diff --git a/lmc_portfolio/assets/pdf/mp2-rough-draft.pdf b/lmc_portfolio/assets/pdf/mp2-rough-draft.pdf