<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Quincy-Cudjoe on Medium]]></title>
        <description><![CDATA[Stories by Quincy-Cudjoe on Medium]]></description>
        <link>https://medium.com/@quincycudjoe1?source=rss-c9db860075c0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ZyDcBprBerrvtK5c</url>
            <title>Stories by Quincy-Cudjoe on Medium</title>
            <link>https://medium.com/@quincycudjoe1?source=rss-c9db860075c0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:57:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@quincycudjoe1/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Blood on the Doorpost: Catching CVEs Before They Ship]]></title>
            <link>https://medium.com/@quincycudjoe1/blood-on-the-doorpost-catching-cves-before-they-ship-7e12c5ba31c9?source=rss-c9db860075c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e12c5ba31c9</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[ci-cd-pipeline]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Quincy-Cudjoe]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 20:55:53 GMT</pubDate>
            <atom:updated>2026-07-13T20:55:53.575Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Building a real CI/CD pipeline meant asking myself “why” at almost every step, and getting backward answers a few times before I got it right.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4XxBqrlLPXXFLu6Dd6IfCw.png" /></figure><h3>Where v1 started</h3><p>My first pipeline was simple: a static site on S3, a buildspec with a handful of lines, push-to-deploy in about 37 seconds. It worked, and seeing it work the first time felt great. That’s still one of the best feelings in this field, watching a push actually land.</p><p>But a static site doesn’t have tests to run. It doesn’t have dependencies that can carry a CVE. It doesn’t need a human to look at anything before going live. V1 taught me that a pipeline exists. It didn’t teach me why a real one has more than one stage.</p><h3>Why v2 was needed</h3><p>I wanted to actually understand each piece of a production-style pipeline, not just wire four AWS services together and call it done. So Pipeline v2 became this: take a small Flask habit tracker, containerize it, and ask myself “why” before adding each stage. Tests. A container vulnerability scan. A human approval. A real deploy behind a load balancer.</p><p>The architecture, in the end:</p><pre>GitHub push → CodeBuild (pytest → Docker build → Trivy scan) → Manual Approval → ECS Fargate deploy</pre><p>Four stages. I only actually understood why each one earns its place by breaking something at every layer, one at a time.</p><h3>The habit tracker itself</h3><p>Nothing exotic. A Flask app with a CLI mode and a web UI, tracking things like AWS study, dumbbells, reading. JSON file storage. The app was never really the point. It just needed to be real enough to write actual tests against, containerize, and scan.</p><h3>pytest: why does the test file even matter?</h3><p>I asked myself this before writing a single test. If tracker.py already works, why do I need a whole second file just to test it?</p><p>The answer, once I sat with it: tracker.py does the work. test_tracker.py proves the work is correct, by importing the real functions and checking their output against what it should be, automatically, on every push, without me having to remember to check it myself.</p><pre>def test_log_habit_twice_same_day_does_not_duplicate(temp_data_file):<br>    tracker.log_habit(&quot;Reading&quot;, verbose=False)<br>    tracker.log_habit(&quot;Reading&quot;, verbose=False)<br>    data = tracker.load_data()<br>    assert len(data[&quot;Reading&quot;]) == 1</pre><p>Eleven tests in the end, covering the dedup logic, streak calculation (including the “what if I missed yesterday” edge case), and both Flask routes. Wired into CodeBuild’s pre_build phase, so a broken app never even gets the chance to become a Docker image.</p><p>The first real lesson here wasn’t a concept. It was a mistake. I wrote that test file, staged it, committed it, pushed it, and it turned out to be zero bytes. A heredoc had silently failed mid-write in my terminal, and nothing downstream noticed, because an empty file is still a valid file as far as git is concerned. CodeBuild’s response was blunt: pytest -v exited with status 5, pytest&#39;s code for &quot;no tests were collected.&quot; Not a failing test. No tests at all. I ended up cloning my own repo fresh into /tmp just to prove to myself the file really was empty on GitHub, not just in my head.</p><h3>Trivy: why does the gate need to be this strict?</h3><p>Once tests passed and Docker built the image, Trivy scanned it, hard-failing the build on any HIGH or CRITICAL CVE. The first time it actually caught something, it caught 20 vulnerabilities, every one of them in the Debian OS layer underneath my Python packages, not in Flask or pytest themselves.</p><p>I thought about why this mattered by imagining someone else on the team. Say Michael pushes code to prod on a Friday, and it has a vulnerability nobody caught. Without a gate like this, that code ships anyway. The build doesn’t fail just because a CVE exists, so it goes out, sits there, and nobody looks at it again until something goes wrong. With the gate in place, it doesn’t matter if it’s Michael or me pushing. The pipeline runs the same check every time, whether or not anyone remembers to ask for it.</p><p>Then I actually hit the real version of this myself. python:3.12-slim was silently defaulting to Debian Trixie, the newest Debian release, so new that a chunk of its own CVEs were still marked affected or fix_deferred, meaning no patch existed yet upstream. apt-get upgrade can&#39;t install a patch that doesn&#39;t exist. The fix was pinning to Bookworm, the previous stable release, which has had far longer for Debian&#39;s security team to catch up, and adding --ignore-unfixed to the Trivy command so the gate only blocks on CVEs that could genuinely be fixed. Otherwise the pipeline would be permanently unable to pass through no fault of my own.</p><p>Even installing Trivy broke first. The original wget | tar command failed silently on Amazon Linux&#39;s CodeBuild image, which doesn&#39;t reliably ship wget. Switched to Trivy&#39;s official curl-based install script, and that fire was out.</p><h3>What broke, in the order it broke</h3><p>CodeConnections pointed at the wrong GitHub App installation. I had two GitHub connections in my AWS account from different points in time, and CodeBuild kept defaulting to the older one, which didn’t have habit-tracker in its authorized repository list. The error looked like an IAM problem. It wasn&#39;t. It was GitHub&#39;s own App authorization scope, sitting underneath AWS&#39;s IAM entirely, and no AWS-side policy could fix it because the block was happening on GitHub&#39;s side of the handshake.</p><p>IAM permission layering went three deep. Even with an AdministratorAccess-attached user, the exact same connection error persisted, which is how I knew it wasn&#39;t a normal permissions problem. Using a GitHub connection to authorize another AWS service requires a specific UseConnection and PassConnection grant, separate from just being an admin. Passing that connection down to CodePipeline later needed the same grant added to a completely different role. Same idea, three separate places, before I actually saw the pattern.</p><p>Privileged mode got missed entirely on the first CodeBuild project. docker build needs elevated container permissions to build images inside a container. CodeBuild calls this &quot;privileged mode,&quot; and it&#39;s not on by default. My first build sailed past source download, past install, and died right at the Docker step, for a reason that had nothing to do with Docker itself. Just a checkbox I&#39;d never checked.</p><p>Security group rules got attached backward. I built two groups on purpose: one guarding the load balancer (public, port 80), one guarding the actual container (only reachable from the load balancer, port 5000). The port 5000 rule somehow ended up attached to the load balancer’s group instead of the container’s. Nothing failed loudly. It just would have quietly defeated the entire point of separating them. I caught it by reading the output line by line instead of assuming the commands did what I typed.</p><p>The CodeBuild role couldn’t read its own source. Once CodeBuild started running inside CodePipeline instead of pulling straight from GitHub, its source stopped coming from GitHub directly. CodePipeline zips it and drops it in S3, then hands CodeBuild that object. Nobody had told the CodeBuild role it was allowed to read from that bucket. Same role, genuinely different job, needed genuinely different permission.</p><p>My browser lied to me. Everything had deployed. Target health showed healthy. curl returned a clean 200 OK with the full page. Chrome still refused to load it, timing out completely. A cached HSTS policy was silently force-upgrading the request to HTTPS, against a load balancer that only had an HTTP listener. I opened it in a different browser and it worked instantly. The infrastructure was never broken. My browser&#39;s memory was.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5z8qN74uia2CwZN2gRL2Cw.png" /><figcaption>Source → Build → Approval → Deploy, all succeeded.</figcaption></figure><h3>Bookworm, Trixie, and a doorpost</h3><p>Bookworm and Trixie aren’t AWS terms. They’re just Debian’s naming convention, released in sequence. python:3.12-slim rides whatever Debian calls &quot;current stable&quot; right now, which had quietly become Trixie, new enough that its own CVE backports hadn&#39;t caught up. Pinning explicitly to Bookworm traded &quot;newest&quot; for &quot;more security-mature,&quot; which is the right trade for anything actually shipping.</p><p>The other thing that stuck with me was tagging. latest is a label that gets silently repainted onto whatever&#39;s newest every push. Useful for &quot;what&#39;s live right now,&quot; useless for &quot;what was live on Tuesday.&quot; The fix was tagging every image with the short git commit SHA too, something like 1a4a3e2. Permanent, tied to one exact commit, never reassigned.</p><p>The best way I found to explain it to myself: it’s the blood on the doorpost from Passover. Not a label that moves with whoever’s currently living there, but a mark tied to one specific night, permanent, so it can always be pointed back to no matter what happens after. latest tells you who&#39;s home today. The SHA tag tells you who was home on any given night, forever.</p><h3>Why the approval stage exists at all</h3><p>Trivy and pytest can tell me code is safe. Neither can tell me it’s the right moment to ship. The manual approval stage is a pause where a human, not a script, makes that second, different call, and it leaves a real record behind: who approved this deploy, and when. In this pipeline, that record read my own IAM user, timestamped, with a one-line review note. That’s the one part of the pipeline where accountability has a name attached to it.</p><h3>The final flow</h3><pre>GitHub push (main)<br>      │<br>      ▼<br>CodePipeline: Source (CodeConnections)<br>      ▼<br>CodePipeline: Build<br>      │  pytest -v        → 11 tests<br>      │  docker build     → image<br>      │  trivy image scan → HIGH/CRITICAL, fixable only<br>      │  docker push      → ECR (tagged latest + commit SHA)<br>      ▼<br>CodePipeline: Approval  ◄── human review, blocks until approved<br>      ▼<br>CodePipeline: Deploy<br>      ▼<br>ECS Fargate Service ── Application Load Balancer ── Public URL</pre><p>Everything came down after the screenshots were taken. No lingering cost, no orphaned resources. What’s left is the part that actually matters: the code, the tests, the pipeline definition, and a README that documents the decisions I actually made, not just the parts that worked on the first try.</p><p><a href="https://github.com/Quincy-000/habit-tracker">github.com/Quincy-000/habit-tracker</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e12c5ba31c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I Killed My App on Purpose: Here’s What Kubernetes Did About It]]></title>
            <link>https://medium.com/@quincycudjoe1/i-killed-my-app-on-purpose-heres-what-kubernetes-did-about-it-489c42d40bfe?source=rss-c9db860075c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/489c42d40bfe</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Quincy-Cudjoe]]></dc:creator>
            <pubDate>Sun, 28 Jun 2026 23:28:00 GMT</pubDate>
            <atom:updated>2026-06-28T23:28:00.756Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yGSVacfe6tPphHQg" /><figcaption>Photo by <a href="https://unsplash.com/@scottrodgerson?utm_source=medium&amp;utm_medium=referral">Scott Rodgerson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I am not a Kubernetes expert. I want to be clear about that upfront.</p><p>I am a student learning cloud engineering, trying to understand the tools that actually matter in the industry. Today, Kubernetes was that tool. And the way I learned it was simple. I broke things until they made sense.</p><p>This is that story.</p><h3>The Problem I Didn’t Know I Had</h3><p>Before I ran a single Kubernetes command, I ran a Docker one.</p><pre>docker run -d --name my-app -p 8080:80 nginx</pre><p>My app was running. I opened the browser, saw the nginx welcome page, felt good about myself. Then I killed it.</p><pre>docker kill my-app</pre><p>And nothing happened. Not “nothing happened and Kubernetes fixed it.” Just nothing. The app was dead. The browser showed an error. If this had been a real production app, users would have been staring at a broken page until I manually noticed and restarted it myself.</p><p>That quiet, unremarkable death is the entire reason Kubernetes exists.</p><p>Docker is brilliant at running containers. But it doesn’t ask the question: <em>what should be running?</em> It just runs what you tell it to, once, and moves on. Kubernetes asks that question constantly. And it enforces the answer.</p><h3>Enter the Cluster</h3><p>I set up a local Kubernetes cluster using a tool called <strong>kind</strong> (Kubernetes IN Docker). It runs a real K8s cluster on your machine using Docker containers as the nodes. No virtual machines, no cloud account needed. Just Docker, which I already had.</p><pre>kind create cluster --name my-cluster</pre><p>Sixty seconds later, I had a working Kubernetes cluster on my laptop. Then I ran:</p><pre>kubectl get nodes</pre><p>One node. Status: Ready. That’s the machine that was going to run my apps from now on.</p><p>kubectl is the command-line tool for talking to Kubernetes. Think of it like the docker command, but for an entire cluster instead of a single machine.</p><h3>What is a Pod?</h3><p>The first thing Kubernetes teaches you is the Pod.</p><p>A Pod is the smallest thing Kubernetes knows how to run. It wraps your container, or containers, and gives them a shared IP address and a place to live inside the cluster. You don’t talk to the container directly anymore. You talk to the Pod.</p><p>I created one like this:</p><pre>kubectl run my-pod --image=nginx --restart=Never</pre><p>Then I watched it come to life:</p><pre>kubectl get pods</pre><pre>NAME     READY   STATUS    RESTARTS   AGE<br>my-pod   1/1     Running   0          15s</pre><p>Same instincts as Docker, different vocabulary, just a new layer of abstraction over what I already knew.</p><p>Then I deleted it and watched it stay dead. A bare Pod has no self-healing either. Which brings me to the part that actually changed how I think about infrastructure.</p><h3>The Deployment: A Contract With Kubernetes</h3><p>A Deployment is not just a way to run your app. It is a promise you make to Kubernetes, and Kubernetes enforces that promise forever.</p><p>You say: <em>“I want three copies of this app running at all times.”</em></p><p>Kubernetes signs that contract. One Pod dies? Kubernetes creates a new one. A node crashes? Kubernetes moves the Pods elsewhere. You never manually restart anything again.</p><p>Here is the YAML I wrote to create that contract:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: nginx-deployment<br>spec:<br>  replicas: 3<br>  selector:<br>    matchLabels:<br>      app: nginx<br>  template:<br>    metadata:<br>      labels:<br>        app: nginx<br>    spec:<br>      containers:<br>      - name: nginx<br>        image: nginx:latest<br>        ports:<br>        - containerPort: 80</pre><p>I applied it and three Pods appeared. Then I asked myself a question that I think every beginner should ask early:</p><p><em>What happens if I kill one?</em></p><p>I deleted one Pod by name. Within seconds, a new one appeared, different name, same purpose. Kubernetes had seen the contract drop to two and immediately corrected it back to three.</p><p>That is self-healing. And it works whether you are watching or not.</p><p>I then scaled up to five replicas with a single command. Two more Pods appeared with no downtime. Scaled back down to two. Three Pods gracefully terminated. One command. No outage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qDNuHzpbgpQRoWrxdrs2Tw.png" /></figure><h3>Jason, the Hydra, and the Problem With Pod IPs</h3><p>This is where my favourite analogy of the session came in.</p><p>I described the Deployment to myself as a many-headed Hydra. You cut one head and Kubernetes grows two back. The Deployment is what makes that happen. But then I asked a follow-up question that took the analogy further than I expected:</p><p><em>“So services ensure that the same head with its features returns if Jason cuts one down? The same IP address being maintained?”</em></p><p>The answer was almost right, but not quite. And the correction is what made everything click.</p><p>The heads do not keep the same IP when they regrow. Every new Pod that Kubernetes creates gets a fresh, random IP address. So if your app was sending traffic to 10.0.0.5 and that Pod died and came back as 10.0.0.8, anything pointing at the old address is now broken. The Hydra grew a new head, but it grew back standing in a different spot..</p><p>This is the problem a <strong>Service</strong> solves.</p><h3>The Service: A Reception Desk That Never Moves</h3><p>A Service is the permanent address in front of your Pods.</p><p>You never talk to the Pods <strong>directly</strong>. You talk to the Service. The Service knows which Pods are currently alive and forwards your request to one of them. Pods die, Pods regrow with new IPs, their positions shift, but the Service address never changes.</p><pre>You → Service (one fixed IP, port 80) → Pod 1 (random IP, port 80)<br>                                       → Pod 2 (random IP, port 80)<br>                                       → Pod 3 (random IP, port 80)</pre><p>Here is the YAML:</p><pre>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: nginx-service<br>spec:<br>  type: NodePort<br>  selector:<br>    app: nginx<br>  ports:<br>  - port: 80<br>    targetPort: 80<br>    nodePort: 30080</pre><p>Notice selector: app: nginx. The Service does not route by IP address. It routes by <strong>label</strong>. Any Pod wearing the label app: nginx receives traffic from this Service. When a Pod dies and a new one is created with the same label, the Service automatically includes it. No configuration change needed. Nothing is hardcoded. Everything finds everything else by identity, not location.</p><p>I forwarded the port and visited http://localhost:8080. The nginx welcome page loaded, served by a Kubernetes-managed Deployment, behind a Service, running on a local cluster on my machine.</p><p>Then I killed every Pod at once. Refreshed the browser. Still worked. New Pods had already replaced the old ones, and the Service had never missed a beat.</p><h3>What I Pushed to GitHub</h3><p>By the end of the session I had three YAML files:</p><ul><li>pod/my-pod.yaml (the bare Pod, a learning exercise)</li><li>deployment/my-deployment.yaml (three replicas, self-healing)</li><li>service/my-service.yaml (stable address over the Deployment)</li></ul><p>All pushed to <a href="https://github.com/Quincy-000/Kubernetes-Lab">github.com/Quincy-000/Kubernetes-Lab</a>.</p><p>The whole point of writing infrastructure as YAML is that the files <em>are</em> the infrastructure. Anyone who clones that repo and has kind and kubectl installed can recreate exactly what I built today with one command:</p><pre>kubectl apply -f deployment/my-deployment.yaml<br>kubectl apply -f service/my-service.yaml</pre><p>That is infrastructure as code. And it starts with three small files and one afternoon of breaking things on purpose.</p><h3>What Comes Next</h3><p>This was day one. The concepts I am moving into next:</p><p><strong>ConfigMaps and Secrets:</strong> how to inject configuration and API keys into Pods without hardcoding them into your images.</p><p><strong>Ingress:</strong> how to route external traffic to different Services based on URL paths, the real-world version of what the Service does internally.</p><p><strong>Helm:</strong> packaging K8s YAML as reusable, shareable charts.</p><p>I am not an expert. But I understand Pods, Deployments, and Services now, not because I read a definition, but because I killed things and watched Kubernetes bring them back.</p><p>That is the only way I know how to learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=489c42d40bfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Man I Hate Is the Man I Am]]></title>
            <link>https://medium.com/@quincycudjoe1/the-man-i-hate-is-the-man-i-am-ba0a209ee99c?source=rss-c9db860075c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ba0a209ee99c</guid>
            <category><![CDATA[jungian-psychology]]></category>
            <category><![CDATA[human-behavior]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Quincy-Cudjoe]]></dc:creator>
            <pubDate>Sat, 30 May 2026 16:41:14 GMT</pubDate>
            <atom:updated>2026-05-30T16:41:14.046Z</atom:updated>
            <content:encoded><![CDATA[<p>You know that moment.</p><p>You’re scrolling, and someone says something that gets under your skin. Maybe it’s the coworker who’s always complaining but never does anything about it. Or the friend who’s chronically late, again. Or that person who talks way too much about how hard they work.</p><p>And you think, I would never.</p><p>That little surge of superiority. That quiet satisfaction that you’re not like them.</p><p>But here’s the thing nobody tells you about that feeling: it’s a trail of breadcrumbs. And if you follow it, it leads back to you.</p><p>I used to dislike people who complained but never changed. Couldn’t stand them. The lack of self-awareness, the victim mentality. It made my blood boil. I’d lecture friends about it. I’d feel so above it.</p><p>Until one day I caught myself doing the exact same thing. Complaining about my situation. Making excuses. Not changing.</p><p>The person I couldn’t stand was me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*-xezEq4ucn5cHpCk" /><figcaption>Photo by <a href="https://unsplash.com/@laurachouette?utm_source=medium&amp;utm_medium=referral">Laura Chouette</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>What Is Projection?</h4><p>There’s a name for this. It’s called projection, and psychology has known about it for over a century.</p><p>Here’s how it works: your mind has a garbage bin for the traits you don’t want to admit you have. Laziness. Jealousy. Vanity. Selfishness. Instead of looking at them, you subconsciously toss them over the fence and see them in someone else. I’m not lazy. You’re lazy. I’m not jealous. You’re the one who can’t celebrate others.</p><p>Carl Jung called this the shadow, the part of yourself you refuse to acknowledge. And the less you acknowledge it, the bigger it grows.</p><p><em>“Everyone carries a shadow, and the less it is embodied in the individual’s conscious life, the blacker and denser it is.” — Carl Jung</em></p><p>Jung believed that everything about ourselves that we find unacceptable, our anger, our envy, our fears, gets bundled into this shadow self. We don’t destroy it by ignoring it. We just make it stronger, and it leaks out sideways. The most common leak? Seeing it in other people.</p><p>This isn’t just old philosophy. Modern psychology has confirmed it. Studies show that when people suppress a trait, say competitiveness, they reliably see that trait as exaggerated in others. The mind doesn’t just hide the flaw. It projects it onto a screen and calls it someone else’s problem.</p><p>The painful irony? The people who annoy us most are often our best teachers. They’re holding up a mirror we refuse to look into.</p><p><em>“Everything that irritates us about others can lead us to an understanding of ourselves.” — Carl Jung</em></p><p>That’s the part nobody warns you about. That flash of irritation you feel when you see someone acting a certain way. It’s not random. It’s information. It’s your shadow knocking on the door.</p><h4>Everyday Examples</h4><p>You’ve seen this play out. I’ve caught myself in most of these. Maybe you have too.</p><p><strong>The person who can’t stand laziness.</strong></p><p>They’re the first to call someone out for slacking off. They take pride in being a hard worker. But watch closely. They’re often the ones who procrastinate the most when nobody’s watching. The anger at “lazy people” isn’t really about them. It’s about the part of themselves that wants to rest, the part they’ve declared unacceptable.</p><p><strong>The one obsessed with “fake people.”</strong></p><p>They see insincerity everywhere. Everyone’s fake, everyone’s putting on a show. And maybe they’re right about some of it. But the obsession often points inward. They’re deeply aware of the mask they themselves wear, and they hate it. So they project it onto everyone else.</p><p><strong>The person always accusing others of lying.</strong></p><p>They assume everyone has a hidden agenda. They read between every line. And often, they’re the ones hiding the most. It’s hard to trust others when you know what you’re capable of hiding yourself.</p><p><strong>The loudest critic of arrogance.</strong></p><p>Nothing makes them angrier than someone who thinks they’re better than others. But dig a little deeper. That fury often masks a quiet sense of inferiority. They’re fighting their own feelings of not being enough, so they attack anyone who seems too confident.</p><p><strong>The one who judges others for being “too emotional.”</strong></p><p>They pride themselves on being rational, logical, above all that messy feeling stuff. But emotions don’t disappear because you refuse to feel them. They just come out sideways, often as irritation at people who are openly emotional.</p><p>These patterns are everywhere. In your workplace. In your family. In the comment sections you scroll through. And in the mirror, if you’re brave enough to look.</p><p>The question isn’t whether you project. Everyone does. The question is whether you’re willing to see it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NmPF4LWcuJbSL7vu" /><figcaption>Photo by <a href="https://unsplash.com/@krowdeed?utm_source=medium&amp;utm_medium=referral">Lawrence Krowdeed</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Why It Hurts to Look</h4><p>So if projection is so common, why don’t we see it more often?</p><p>Because looking at your own shadow is uncomfortable. Deeply so.</p><p>There’s a line from Friedrich Nietzsche that nails why:</p><p><em>“He who fights with monsters should look to it that he himself does not become a monster. And if you gaze long into an abyss, the abyss also gazes into you.”</em></p><p>What that means is the things you fight against start to shape you. The more energy you put into opposing something, the more it lives inside you. Your enemy defines you. The thing you hate becomes part of your identity.</p><p>That’s a hard thing to accept. It means the person you dislike most might be showing you something you’re not ready to see in yourself. It’s humbling. It collapses the distance between “us” and “them.” And your ego will fight hard to keep that distance alive.</p><p>There’s a reason for that. Your brain treats this kind of self-recognition like physical pain. It literally hurts to see yourself clearly. No wonder we look away.</p><p><strong>What Happens When You Don’t Check It</strong></p><p>The consequences aren’t abstract. They show up in real life.</p><p><strong>Damaged relationships</strong>. You’re not really arguing with the person in front of you. You’re arguing with a mirror. You attack traits in others that remind you of yourself, and the real issue never gets addressed.</p><p><strong>You become what you fight</strong>. The person obsessed with calling out gossip becomes the biggest gossiper. The one always talking about “toxic people” becomes the toxic one in the room. That warning plays out slowly, quietly, until one day you realize you’ve turned into the thing you spent years opposing.</p><p><strong>Stagnation</strong>. You can’t fix what you won’t see. The part of yourself you project onto others stays hidden. It never gets healed. It just sits there, growing, leaking out in ways you don’t control.</p><p><strong>False superiority</strong>. Projection gives you a temporary high. “At least I’m not like them.” But it’s built on a lie. And lies like that have a way of catching up with you.</p><p>Jung said that the beginning of maturity is the ability to carry your own shadow rather than projecting it onto others. Maturity, then, is the willingness to sit with discomfort instead of tossing it over the fence.</p><p><strong>How to Spot It</strong></p><p>The good news is projection leaves clues. Once you know what to look for, it becomes hard to miss.</p><p><strong>Signs you might be projecting:</strong></p><p>The reaction feels too big for the situation. Someone does something small, and you have an emotional explosion. That’s not about them. That’s about you.</p><p>You notice the same flaw in multiple different people. If everyone around you seems to have the same problem, the common denominator is you.</p><p>You feel morally superior about something repeatedly. That itch to lecture, to correct, to judge from above. It’s a signal.</p><p>Someone has gently pointed it out before, and you got defensive. That flash of anger when someone suggests you might be the thing you criticize. It’s a tell.</p><p>You can’t stop thinking about someone else’s “bad trait.” Obsession is rarely about the other person.</p><p>Ask yourself a simple question: Have I ever done this? Am I capable of this? What am I afraid this says about me?</p><p>If the answer makes you uncomfortable, sit with it. That discomfort is the doorway.</p><p>We all project. I do. You do. The people you admire most do. It’s not a flaw to be eliminated. It’s a signal to be listened to.</p><p>The point isn’t to never judge or never feel irritated. The point is to pause when you do and ask: What is this really about?</p><p>The man you hate. The woman who annoys you. The trait that makes your blood boil. Look at it closely. Because if you’re brave enough to look, you might just recognize them.</p><p>They look a lot like you.</p><p>And that’s not a weakness. That’s the beginning of real self-awareness.</p><p>So who have you been hating lately? And what might they be showing you about yourself?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nB3KQl0-gjwrXnNp" /><figcaption>Photo by <a href="https://unsplash.com/@santesson89?utm_source=medium&amp;utm_medium=referral">Andrea De Santis</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba0a209ee99c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Stoicism Works, and When It Doesn’t]]></title>
            <link>https://medium.com/@quincycudjoe1/when-stoicism-works-and-when-it-doesnt-caf5c90d09d9?source=rss-c9db860075c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/caf5c90d09d9</guid>
            <category><![CDATA[self]]></category>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[stoicism]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Quincy-Cudjoe]]></dc:creator>
            <pubDate>Sun, 05 Apr 2026 19:13:07 GMT</pubDate>
            <atom:updated>2026-04-05T19:13:07.187Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been practicing stoicism for about a year, maybe two. I’m not new to it, and I’m not approaching it from a place of hostility. Stoicism has helped me regulate my emotions, think more clearly under pressure, and not be thrown off balance by every minor setback.</p><p>So when I criticize stoicism, I’m not rejecting it. I’m questioning how, when, and where it’s being used.</p><figure><img alt="child-looks-out-window" src="https://cdn-images-1.medium.com/max/388/1*RA4071wVjSy3XfapwNMIHQ.jpeg" /></figure><p>Today, stoicism is often presented as a universal solution, something you should apply to everything, all the time. But historically, that was never the case. Stoicism emerged in harsh conditions: war, political instability, exile, disease, and a near-total lack of personal security. In that world, stoicism wasn’t about self-optimization. It was about psychological survival.</p><p>When the external world was brutal and largely uncontrollable, stoicism taught people how to maintain inner order. Even today, stoicism is incredibly useful in moments of loss, grief, uncertainty, and unavoidable hardship. It steadies the mind and prevents emotional collapse when there is genuinely little you can change.</p><h4>The Limits of Stoicism</h4><p>The problem begins when stoicism stops being a situational tool and becomes a default worldview.</p><p>Even historically, Stoics struggled with this. Cicero, for instance, understood the Stoic advice about grief but, when he lost his daughter, he allowed himself to grieve fully. He didn’t see this as failure. The point is that stoicism is valuable in correcting shallow attachments, excessive ambition, and over-attachment to status, but it has limits.</p><p>Philosopher Martha Nussbaum, particularly in <em>Upheavals of Thought</em>, makes a similar point. Stoicism can help us correct inappropriate attachments, but it becomes morally questionable when it asks us to detach from the things we truly love. About those things, she suggests, we shouldn’t be stoic.</p><h4>The Human Side of Emotion</h4><p>There is something deeply human about being emotionally undone by loss, about caring so much that it disrupts your life. Suppressing that in the name of rational control isn’t strength, it’s emotional flattening.</p><p>Nussbaum also emphasizes compassion. Compassion requires vulnerability. It requires allowing yourself to be affected by the suffering of others. A philosophy that treats emotions primarily as errors to be corrected risks cutting us off from that.</p><p>Where I begin to hesitate is when stoicism is used as emotional therapy that discourages deep feeling altogether, especially for young people.</p><h4>What Stoicism Gets Right</h4><p>That said, there are parts of stoicism I strongly believe we should keep. One is its Socratic commitment to self-examination, the relentless questioning of values, assumptions, and inherited beliefs. Another valuable idea is the image of the world as concentric circles, from the self, to family, to community, to humanity. This encourages a widening sense of responsibility and global awareness.</p><h3>Stoicism in Context</h3><p>The universe is chaotic. We cannot tame it. Stoicism helps us accept that chaos internally, and that’s valuable. But acceptance should not turn into passivity. When applied too broadly, poorly applied stoicism can dampen drive and ambition. It can dull the restlessness that pushes people to struggle, build, and change their circumstances.</p><p>Not all discomfort is pathological. Some of it is necessary. This is where emotional granularity matters, the ability to distinguish emotions rather than suppress them all. Grief is not weakness. Desire is not greed. Frustration is not failure. Stoicism should help us respond wisely to emotions, not erase them.</p><p>So when I say stoicism is useful, but only in context, this is what I mean. It is powerful in moments of unavoidable hardship. But it should not be used to avoid loving deeply, caring fiercely, or wanting more from life.</p><p>Stoicism is a tool. Tools are meant to be picked up and put down, not worn as armor at all times.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=caf5c90d09d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sun’s Lament]]></title>
            <link>https://medium.com/@quincycudjoe1/the-suns-lament-f97a19031222?source=rss-c9db860075c0------2</link>
            <guid isPermaLink="false">https://medium.com/p/f97a19031222</guid>
            <category><![CDATA[melancholy]]></category>
            <category><![CDATA[poetry]]></category>
            <category><![CDATA[personification]]></category>
            <category><![CDATA[creative-writing]]></category>
            <dc:creator><![CDATA[Quincy-Cudjoe]]></dc:creator>
            <pubDate>Sun, 05 Oct 2025 18:32:24 GMT</pubDate>
            <atom:updated>2025-10-05T18:32:24.828Z</atom:updated>
            <content:encoded><![CDATA[<p>Where have you gone, my moon?</p><p>In your absence, my malady blooms – my boon.</p><p>Who has stolen you away from me?</p><p>Could it be these envious men below?</p><p>I have seen how they gaze at you, my beauty.</p><p>I will make their waters taste of salt until I see you again.</p><p>My bitterness will be theirs; my tears will become their sweat.</p><p>Let my anguish burn the flowers I cannot give to you.</p><p>And when I find you, when I embrace you –</p><p>let them gaze in awe at our beautiful love.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*tbhqnUOqLJpB9bNvnEgaHA@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f97a19031222" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>