<?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[CodeToDeploy - Medium]]></title>
        <description><![CDATA[Tech Insights | Careers | Jobs - Medium]]></description>
        <link>https://medium.com/codetodeploy?source=rss----c8b549b355f4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>CodeToDeploy - Medium</title>
            <link>https://medium.com/codetodeploy?source=rss----c8b549b355f4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:36:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/codetodeploy" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Stopped Memorizing Kubernetes RBAC YAML — Here’s the Mental Model That Finally Made It Click]]></title>
            <link>https://medium.com/codetodeploy/stopped-memorizing-kubernetes-rbac-yaml-heres-the-mental-model-that-finally-made-it-click-5deb94cfe1ef?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/5deb94cfe1ef</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[kubernetes-security]]></category>
            <category><![CDATA[k8s]]></category>
            <category><![CDATA[kubernetes-rbac]]></category>
            <dc:creator><![CDATA[Tahjib]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:41:07 GMT</pubDate>
            <atom:updated>2026-11-17T14:41:05.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*baLpTxjqpf9MRJyhmYIgRA.jpeg" /></figure><p>You understand Pods. You understand Deployments. You understand Services. Then someone says <em>“give the CI pipeline permission to deploy but not to read secrets”</em> — and suddenly you’re copy-pasting YAML from Stack Overflow and praying.</p><blockquote><em>💥 </em><strong><em>Master Coding, AI, AWS &amp; Data Science</em></strong><em><br>🚀 Build In-Demand Skills &amp; Crack Tech Interviews<br>🔥 Get Up to 6</em><strong><em>0% OFF</em></strong><em> — Limited-Time Offer</em></blockquote><blockquote><a href="https://www.educative.io/unlimited?aff=xkRD"><em>👉 </em><strong><em>Build Job-Ready Skills Today</em></strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ITogvtC6mF2BUF35Qsd9pg.png" /></figure><p>RBAC feels hard because most tutorials start with the YAML. That’s backwards. RBAC is not a YAML problem. It’s a <strong>sentence-parsing problem</strong>.</p><p>In this post I’ll walk you through the exact lab I built to learn it — a fake company called <strong>TechCorp</strong> with real people, real pipelines, and real permission boundaries. Everything runs on a local kind cluster, costs nothing, and takes about 30 minutes.</p><h3>The Mental Model: Five Questions, Every Time</h3><p>Before you write a single line of YAML, translate the requirement into five questions:</p><pre>WHO?        →  User / ServiceAccount<br>WHAT?       →  Resource (pods, deployments, secrets...)<br>DO WHAT?    →  Verb (get, list, create, delete...)<br>WHERE?      →  Namespace / Cluster<br>HOW?        →  Role + Binding</pre><p>That’s it. That’s the whole thing.</p><p>Take a real requirement:</p><blockquote><em>“Bob should be able to update Deployments in dev.”</em></blockquote><p>Parse it:</p><pre>WHO?      Bob<br>WHAT?     Deployments<br>DO WHAT?  update<br>WHERE?    dev<br>HOW?      Role + RoleBinding</pre><p>Now the YAML writes itself. The Role answers <strong>WHAT + DO WHAT + WHERE</strong>. The RoleBinding answers <strong>WHO</strong>.</p><p>Once you internalize this, RBAC stops being memorization and becomes translation.</p><h3>The Scenario: TechCorp Kubernetes Platform</h3><p>Here’s the access matrix we’re going to build:</p><p>User / ServiceAccountRoleWhat they should doaliceDeveloperManage Pods in devbobDeveloperManage Deployments/Services in devcharlieQARead resources in devdavidDevOpsManage everything in devmonitoring-saMonitoringRead Pods/Deploymentsdeploy-saCI/CDCreate/update Deployments — nothing else</p><p>Notice the pattern: <strong>humans get Users, applications get ServiceAccounts</strong>. That distinction matters more than people realize, and we’ll come back to it.</p><h3>Step 1: Spin Up the Lab</h3><pre>kind create cluster --name rbac-lab</pre><p>Verify:</p><pre>kubectl get nodes<br>kubectl config current-context</pre><p>You should see:</p><pre>kind-rbac-lab</pre><p>Create the namespaces — namespaces.yaml:</p><pre>apiVersion: v1<br>kind: Namespace<br>metadata:<br>  name: dev<br><br>---<br>apiVersion: v1<br>kind: Namespace<br>metadata:<br>  name: production</pre><pre>kubectl apply -f namespaces.yaml</pre><p>The production namespace exists for one reason: to prove that permissions <strong>don&#39;t leak</strong> across namespace boundaries. We&#39;ll test that later.</p><p>Now deploy something to actually permission against — applications.yaml:</p><pre>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: frontend<br>  namespace: dev<br>spec:<br>  replicas: 2<br>  selector:<br>    matchLabels:<br>      app: frontend<br>  template:<br>    metadata:<br>      labels:<br>        app: frontend<br>    spec:<br>      containers:<br>        - name: nginx<br>          image: nginx:1.27<br>---<br>apiVersion: apps/v1<br>kind: Deployment<br>metadata:<br>  name: backend<br>  namespace: dev<br>spec:<br>  replicas: 2<br>  selector:<br>    matchLabels:<br>      app: backend<br>  template:<br>    metadata:<br>      labels:<br>        app: backend<br>    spec:<br>      containers:<br>        - name: nginx<br>          image: nginx:1.27</pre><pre>kubectl apply -f applications.yaml<br>kubectl get deployments -n dev</pre><pre>NAME       READY   UP-TO-DATE   AVAILABLE   AGE<br>backend    2/2     2            2           27s<br>frontend   2/2     2            2           27s</pre><p>Lab is live.</p><h3>Step 2: Alice — The Pod Manager</h3><p><strong>Requirement:</strong> Alice is a developer. She can get, list, watch, create, and delete Pods — only in dev. She cannot touch Deployments. She cannot touch production.</p><p>Parse it: WHO = alice, WHAT = pods, DO WHAT = 5 verbs, WHERE = dev, HOW = Role + RoleBinding.</p><p>alice.yaml:</p><pre>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: pod-manager<br>  namespace: dev<br>rules:<br>  - apiGroups:<br>      - &quot;&quot;<br>    resources:<br>      - pods<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>      - create<br>      - delete<br><br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: alice-pod-manager<br>  namespace: dev<br>subjects:<br>  - kind: User<br>    name: alice<br>    apiGroup: rbac.authorization.k8s.io<br>roleRef:<br>  kind: Role<br>  name: pod-manager<br>  apiGroup: rbac.authorization.k8s.io</pre><pre>kubectl apply -f alice.yaml</pre><h3>The apiGroups: [&quot;&quot;] thing</h3><p>That empty string trips up everyone. It’s the <strong>core API group</strong> — Pods, Services, ConfigMaps, Secrets, PersistentVolumeClaims. Deployments, ReplicaSets, StatefulSets, and DaemonSets live in the apps group. Get the group wrong and your Role silently grants nothing.</p><p>Quick way to check any resource:</p><pre>kubectl api-resources | grep deployments</pre><h3>Test Alice</h3><p>This is the best part of RBAC. You don’t need to create a certificate, a kubeconfig, or a login. You just impersonate:</p><pre>kubectl auth can-i get pods --as=alice -n dev<br># yes</pre><pre>kubectl auth can-i create pods --as=alice -n dev<br># yes</pre><p>Now the boundaries:</p><pre>kubectl auth can-i get deployments --as=alice -n dev<br># no</pre><pre>kubectl auth can-i get pods --as=alice -n production<br># no</pre><p>Two different kinds of “no,” and both matter.</p><p>The first no is the <strong>resource boundary</strong> — her Role never mentioned Deployments. The second no is the <strong>namespace boundary</strong> — a Role and RoleBinding live inside a namespace, and their power stops at its walls. Even though Alice has pod-manager in dev, in production she is nobody.</p><blockquote><strong><em>Note on Users:</em></strong><em> Kubernetes has no </em><em>User object. You can&#39;t </em><em>kubectl create user alice. Users come from outside the cluster — certificates, OIDC, your cloud provider&#39;s IAM. RBAC just </em>references<em> the name. That&#39;s why </em><em>--as=alice works even though &quot;alice&quot; doesn&#39;t exist anywhere.</em></blockquote><h3>Step 3: Bob — The Developer</h3><p><strong>Requirement:</strong> Bob manages applications. Full lifecycle on Pods, Services, and Deployments. <strong>No access to Secrets.</strong></p><p>This one introduces multiple rules in a single Role — one per API group.</p><p>bob.yaml:</p><pre>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: developer<br>  namespace: dev<br>rules:<br>  - apiGroups:<br>      - &quot;&quot;<br>    resources:<br>      - pods<br>      - services<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>      - create<br>      - update<br>      - patch<br>      - delete<br>  - apiGroups:<br>      - apps<br>    resources:<br>      - deployments<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>      - create<br>      - update<br>      - patch<br>      - delete<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: bob-developer<br>  namespace: dev<br>subjects:<br>  - kind: User<br>    name: bob<br>    apiGroup: rbac.authorization.k8s.io<br>roleRef:<br>  kind: Role<br>  name: developer<br>  apiGroup: rbac.authorization.k8s.io</pre><pre>kubectl apply -f bob.yaml</pre><p>Test:</p><pre>kubectl auth can-i create deployments --as=bob -n dev<br># yes</pre><pre>kubectl auth can-i delete pods --as=bob -n dev<br># yes</pre><pre>kubectl auth can-i get secrets --as=bob -n dev<br># no</pre><h3>The rule that governs everything</h3><p>RBAC is <strong>purely additive</strong>. There is no deny. There is no ordering. There is no precedence.</p><p>Bob can’t read Secrets not because we blocked him — but because <strong>nothing ever allowed him</strong>. Every request starts at no and stays there unless some rule, in some Role bound to him, says yes.</p><p>This is why RBAC debugging is almost always the same question: <em>what does he have that I didn’t expect?</em> — never <em>what’s blocking him?</em></p><h3>Step 4: David — DevOps</h3><p><strong>Requirement:</strong> David runs the platform. Give him full control over common application resources in dev.</p><p>david.yaml:</p><pre>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: devops-admin<br>  namespace: dev<br>rules:<br>  - apiGroups:<br>      - &quot;&quot;<br>    resources:<br>      - pods<br>      - services<br>      - configmaps<br>      - secrets<br>      - persistentvolumeclaims<br>    verbs:<br>      - &quot;*&quot;<br>  - apiGroups:<br>      - apps<br>    resources:<br>      - deployments<br>      - replicasets<br>      - statefulsets<br>      - daemonsets<br>    verbs:<br>      - &quot;*&quot;<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: david-devops<br>  namespace: dev<br>subjects:<br>  - kind: User<br>    name: david<br>    apiGroup: rbac.authorization.k8s.io<br>roleRef:<br>  kind: Role<br>  name: devops-admin<br>  apiGroup: rbac.authorization.k8s.io</pre><pre>kubectl apply -f david.yaml</pre><p>Test:</p><pre>kubectl auth can-i delete pods --as=david -n dev<br># yes</pre><pre>kubectl auth can-i create deployments --as=david -n dev<br># yes</pre><pre>kubectl auth can-i delete pods --as=david -n production<br># no</pre><p>That last one is the lesson of this task.</p><p>David has verbs: [&quot;*&quot;]. Wildcard. Total power. And he still can&#39;t delete a single Pod in production — because a <strong>RoleBinding is namespaced</strong>, and dev is where his power lives.</p><p>If you actually wanted David to be cluster-wide, you’d need a <strong>ClusterRole + ClusterRoleBinding</strong>. Wildcards scale the <em>verbs</em>. Only cluster-scoped objects scale the <em>reach</em>.</p><blockquote><em>A note on </em><em>&quot;*&quot;: it&#39;s fine in a lab. In production, it&#39;s how you wake up to an incident. Wildcards silently absorb new resources and new verbs as Kubernetes evolves — you&#39;re granting permissions that don&#39;t exist yet.</em></blockquote><h3>Step 5: monitoring-sa — From Humans to Machines</h3><p>Everything so far has been a person. Now we switch to workloads.</p><p><strong>Requirement:</strong> A monitoring agent runs inside the cluster. It needs read-only access to Pods, Services, and Deployments. Nothing else. Ever.</p><p>monitoring.yaml:</p><pre>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br>  name: monitoring-sa<br>  namespace: dev<br><br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: monitoring-reader<br>  namespace: dev<br>rules:<br>  - apiGroups:<br>      - &quot;&quot;<br>    resources:<br>      - pods<br>      - services<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>  - apiGroups:<br>      - apps<br>    resources:<br>      - deployments<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: monitoring-reader<br>  namespace: dev<br>subjects:<br>  - kind: ServiceAccount<br>    name: monitoring-sa<br>    namespace: dev<br>roleRef:<br>  kind: Role<br>  name: monitoring-reader<br>  apiGroup: rbac.authorization.k8s.io</pre><pre>kubectl apply -f monitoring.yaml</pre><h3>Two things changed</h3><p><strong>1. The ServiceAccount is a real object.</strong> Unlike alice, we created it. It exists in etcd. kubectl get sa -n dev will show it. Kubernetes mounts its token into any Pod that references it.</p><p><strong>2. The subject dropped </strong><strong>apiGroup.</strong> Look closely at the RoleBinding — Users and Groups need apiGroup: rbac.authorization.k8s.io, but ServiceAccounts don&#39;t, because they belong to the core API group. Instead they need a namespace field. Getting this wrong is one of the most common RBAC mistakes.</p><h3>Test it</h3><p>ServiceAccounts impersonate with a fully-qualified name:</p><pre>system:serviceaccount:&lt;namespace&gt;:&lt;name&gt;</pre><pre>kubectl auth can-i get pods \<br>  --as=system:serviceaccount:dev:monitoring-sa \<br>  -n dev<br># yes</pre><pre>kubectl auth can-i delete pods \<br>  --as=system:serviceaccount:dev:monitoring-sa \<br>  -n dev<br># no</pre><p>Read-only means read-only. get, list, watch — and the moment you ask for delete, nothing in that Role has anything to say, so the answer is no.</p><h3>Step 6: deploy-sa — The CI/CD Pipeline</h3><p>This is the task that matters most in the real world, and the one people get wrong most often.</p><p><strong>Requirement:</strong></p><pre>deploy-sa</pre><pre>Can:<br>  get / list / watch / create / update / patch  deployments</pre><pre>Cannot:<br>  delete deployments<br>  access secrets<br>  create pods</pre><p>Read that “Cannot” list again. A CI pipeline needs to <em>ship</em>, not to <em>destroy</em>. A leaked pipeline token that can only roll Deployments forward is an incident. One that can delete Deployments and read Secrets is a breach.</p><p>cicd.yaml:</p><pre>apiVersion: v1<br>kind: ServiceAccount<br>metadata:<br>  name: deploy-sa<br>  namespace: dev<br><br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: Role<br>metadata:<br>  name: deployment-manager<br>  namespace: dev<br>rules:<br>  - apiGroups:<br>      - apps<br>    resources:<br>      - deployments<br>    verbs:<br>      - get<br>      - list<br>      - watch<br>      - create<br>      - update<br>      - patch<br>---<br>apiVersion: rbac.authorization.k8s.io/v1<br>kind: RoleBinding<br>metadata:<br>  name: deploy-sa-binding<br>  namespace: dev<br>subjects:<br>  - kind: ServiceAccount<br>    name: deploy-sa<br>    namespace: dev<br>roleRef:<br>  kind: Role<br>  name: deployment-manager<br>  apiGroup: rbac.authorization.k8s.io</pre><pre>kubectl apply -f cicd.yaml</pre><p>Test what it <strong>can</strong> do:</p><pre>kubectl auth can-i create deployments \<br>  --as=system:serviceaccount:dev:deploy-sa -n dev<br># yes</pre><pre>kubectl auth can-i update deployments \<br>  --as=system:serviceaccount:dev:deploy-sa -n dev<br># yes</pre><p>And — more importantly — what it <strong>cannot</strong>:</p><pre>kubectl auth can-i delete deployments \<br>  --as=system:serviceaccount:dev:deploy-sa -n dev<br># no</pre><pre>kubectl auth can-i get secrets \<br>  --as=system:serviceaccount:dev:deploy-sa -n dev<br># no</pre><h3>The detail worth pausing on</h3><p>update and patch are granted. delete is not.</p><p>That single omission is the difference between a pipeline that deploys and a pipeline that can wipe your environment. And notice how you express it: not by denying delete, but by <strong>simply not listing it</strong>. Least privilege in RBAC isn&#39;t something you enforce — it&#39;s something you get for free by writing down only what you actually need.</p><p>Also notice the Role has exactly one rule, one apiGroup, one resource. That’s what a well-scoped machine identity looks like.</p><h3>The Debugging Workflow</h3><p>When RBAC “doesn’t work,” run these four commands in order:</p><pre># 1. What can this identity actually do, everywhere?<br>kubectl auth can-i --list --as=alice -n dev</pre><pre># 2. Does the binding exist, and what does it point to?<br>kubectl get rolebindings -n dev<br>kubectl describe rolebinding alice-pod-manager -n dev</pre><pre># 3. What does the Role actually grant?<br>kubectl describe role pod-manager -n dev</pre><pre># 4. Is the resource in the API group you think it is?<br>kubectl api-resources | grep deployments</pre><p>In my experience, nine out of ten RBAC bugs are one of these four:</p><ol><li><strong>Wrong </strong><strong>apiGroups</strong> — you put deployments under &quot;&quot; instead of apps</li><li><strong>Wrong namespace</strong> — the Role is in dev, the RoleBinding is in default</li><li><strong>Malformed subject</strong> — apiGroup on a ServiceAccount, or missing namespace on one</li><li><strong>Missing verb</strong> — you granted get and list, but kubectl get on a watch-based client also wants watch</li></ol><p>None of them are hard. All of them are invisible, because RBAC fails silently — a Role that grants nothing is still a perfectly valid Role.</p><h3>Cheat Sheet</h3><p><strong>Scope:</strong></p><p>ObjectScopeUse whenRoleOne namespacePermissions inside a single namespaceClusterRoleWhole clusterCluster resources, or reusable permission setsRoleBindingOne namespaceGrant in a single namespaceClusterRoleBindingWhole clusterGrant everywhere</p><p><strong>API groups you’ll hit daily:</strong></p><p>ResourceapiGrouppods, services, configmaps, secrets, pvcs&quot;&quot;deployments, replicasets, statefulsets, daemonsetsappsroles, rolebindings, clusterrolesrbac.authorization.k8s.iojobs, cronjobsbatch</p><p><strong>Verbs:</strong></p><p>ReadWriteget, list, watchcreate, update, patch, delete, deletecollection</p><p><strong>Impersonation:</strong></p><pre>kubectl auth can-i &lt;verb&gt; &lt;resource&gt; --as=&lt;user&gt; -n &lt;ns&gt;<br>kubectl auth can-i &lt;verb&gt; &lt;resource&gt; --as=system:serviceaccount:&lt;ns&gt;:&lt;sa&gt; -n &lt;ns&gt;<br>kubectl auth can-i --list --as=&lt;user&gt; -n &lt;ns&gt;</pre><h3>Cleanup</h3><pre>kind delete cluster --name rbac-lab</pre><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9QTaaaxboQP_gKSLedW_w.png" /></figure><p>👉 Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></p><p>👉 Follow us: <a href="https://medium.com/codetodeploy"><strong>Medium</strong></a></p><p><strong>Disclosure:</strong> This post includes affiliate and partnership links.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5deb94cfe1ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codetodeploy/stopped-memorizing-kubernetes-rbac-yaml-heres-the-mental-model-that-finally-made-it-click-5deb94cfe1ef">Stopped Memorizing Kubernetes RBAC YAML — Here’s the Mental Model That Finally Made It Click</a> was originally published in <a href="https://medium.com/codetodeploy">CodeToDeploy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Claude Skills Explained: How to Turn AI Into Your Personal Specialist]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/claude-skills-explained-how-to-turn-ai-into-your-personal-specialist-d5a9ac9971fb?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/1400/0*ZnS4frMtgSFTcOnK" width="1400"></a></p><p class="medium-feed-snippet">Stop repeating the same instructions to AI. Learn how Claude Skills can turn your everyday tasks into reusable workflows.</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/claude-skills-explained-how-to-turn-ai-into-your-personal-specialist-d5a9ac9971fb?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/claude-skills-explained-how-to-turn-ai-into-your-personal-specialist-d5a9ac9971fb?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/d5a9ac9971fb</guid>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[skills]]></category>
            <dc:creator><![CDATA[The AI Coder]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:40:06 GMT</pubDate>
            <atom:updated>2026-11-17T14:40:05.677Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[9 Places Jev Could Replace an LLM Call in Your AI Application]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/9-places-jev-could-replace-an-llm-call-in-your-ai-application-e05bdea5079e?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/1672/1*dRbLToQhnJRQDDFP-Fo4Ow.png" width="1672"></a></p><p class="medium-feed-snippet">From model routing to guardrails and RAG, here are nine practical ways to use Jev where generating text might be unnecessary.</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/9-places-jev-could-replace-an-llm-call-in-your-ai-application-e05bdea5079e?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/9-places-jev-could-replace-an-llm-call-in-your-ai-application-e05bdea5079e?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/e05bdea5079e</guid>
            <category><![CDATA[agentic-ai]]></category>
            <category><![CDATA[jevs]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ai-agent]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Sachin Kasana]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:39:08 GMT</pubDate>
            <atom:updated>2026-11-17T14:39:07.080Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Is Redis Single-Threaded? Understanding Concurrency, Atomicity, I/O Threads, and Scaling]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/why-is-redis-single-threaded-understanding-concurrency-atomicity-i-o-threads-and-scaling-dad26c941a69?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/1672/1*_OkUgTXF1ejUSAZOlanuiQ.png" width="1672"></a></p><p class="medium-feed-snippet">Redis is known for its exceptional speed. It powers caching, session management, rate limiting, leaderboards, and real-time applications.</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/why-is-redis-single-threaded-understanding-concurrency-atomicity-i-o-threads-and-scaling-dad26c941a69?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/why-is-redis-single-threaded-understanding-concurrency-atomicity-i-o-threads-and-scaling-dad26c941a69?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/dad26c941a69</guid>
            <category><![CDATA[redis]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[backend-development]]></category>
            <dc:creator><![CDATA[The Turtle Code]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:38:08 GMT</pubDate>
            <atom:updated>2026-11-17T14:38:06.947Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Vision Beyond the Single Pass: How Recurrent Visual Loops Solve Spatial Reasoning Without Giant…]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/vision-beyond-the-single-pass-how-recurrent-visual-loops-solve-spatial-reasoning-without-giant-6a2f42b0f046?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/1466/1*rkXxJZKPXvV0w_SLOBWjxQ.png" width="1466"></a></p><p class="medium-feed-snippet">Why static feed-forward Vision-Language Models drown in multi-crop token explosions, and how Renmin University and ByteDance&#x2019;s LoopVL&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/vision-beyond-the-single-pass-how-recurrent-visual-loops-solve-spatial-reasoning-without-giant-6a2f42b0f046?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/vision-beyond-the-single-pass-how-recurrent-visual-loops-solve-spatial-reasoning-without-giant-6a2f42b0f046?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/6a2f42b0f046</guid>
            <category><![CDATA[large-language-models]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai-research]]></category>
            <category><![CDATA[deep-learning]]></category>
            <category><![CDATA[machine-learning]]></category>
            <dc:creator><![CDATA[ArXiv In-depth Analysis]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:33:52 GMT</pubDate>
            <atom:updated>2026-11-17T14:33:51.221Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Stop Using delay(). Your Arduino Deserves Better.]]></title>
            <link>https://medium.com/codetodeploy/stop-using-delay-your-arduino-deserves-better-4eb0f1b77448?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/4eb0f1b77448</guid>
            <category><![CDATA[arduino]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[c-programming]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[embedded-systems]]></category>
            <dc:creator><![CDATA[Aeon Flex, Elriel Assoc. 2133 [NEON MAXIMA]]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:32:56 GMT</pubDate>
            <atom:updated>2026-11-17T14:32:54.527Z</atom:updated>
            <content:encoded><![CDATA[<h4>And so does anyone who has to use what you build.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*npL6H6sUhqw0B3s_5xK9pg@2x.jpeg" /><figcaption>Photo by <a href="http://www.vishnumaiea.in">Vishnu Mohanan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s get one thing straight.</p><p>If your entire Arduino program is held together by delay(1000), you didn’t write firmware. You wrote a screensaver that occasionally does something useful.</p><blockquote><em>💥 </em><strong><em>Master Coding, AI, AWS &amp; Data Science</em></strong><em><br>🚀 Build In-Demand Skills &amp; Crack Tech Interviews<br>🔥 Get Up to 6</em><strong><em>0% OFF</em></strong><em> — Limited-Time Offer</em></blockquote><blockquote><a href="https://www.educative.io/unlimited?aff=xkRD"><em>👉 </em><strong><em>Build Job-Ready Skills Today</em></strong></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ITogvtC6mF2BUF35Qsd9pg.png" /></figure><p>We all started there. Blink.ino tells you to do it. The Arduino gods say delay(), and we obey. Then we add a second sensor. Then a button. Then we wonder why the button only works if we press it with the patience of a monk.</p><p>This is an intervention.</p><h3>The Comfortable Lie of delay()</h3><p>delay() feels so intuitive. So honest. You want to wait a second? You say wait a second.</p><pre>digitalWrite(LED, HIGH);<br>delay(1000);<br>digitalWrite(LED, LOW);<br>delay(1000);</pre><p>Perfect. Readable. Works. For exactly one LED and nothing else.</p><p>Here’s what delay() actually does: it grabs your poor little ATmega by the collar, slams it against the wall, and screams “DO NOTHING FOR 1000 MILLISECONDS.”</p><p>It’s not sleeping. It’s not idling efficiently. It’s busy-waiting. Spinning in a tight little loop, counting clock cycles, burning power, ignoring the entire outside world.</p><p>Your button press? Ignored.</p><p>Serial data coming in? Might get dropped.</p><p>That critical sensor reading? Nope, we’re busy doing nothing.</p><p>delay() is the programming equivalent of putting your fingers in your ears and going “LALALALA I CAN’T HEAR YOU.”</p><p>It’s blocking. And blocking code doesn’t scale.</p><h3>The Blink Trap: Where Projects Go to Die</h3><p>Every doomed project follows the same arc:</p><h4>Phase 1: Innocence</h4><p>You make an LED blink. You feel like Tony Stark.</p><h4>Phase 2: Ambition</h4><p>You add a second LED. You want them to blink at different rates.</p><pre>// The dream dies here<br>digitalWrite(LED1, HIGH);<br>delay(1000);<br>digitalWrite(LED2, HIGH);<br>delay(500);<br>digitalWrite(LED1, LOW);<br>// ... you already see where this is going</pre><p>Suddenly your timings are all linked. LED1 can’t blink without dragging LED2 along with it. Your code looks like you tried to choreograph a dance via text message.</p><h4>Phase 3: Desperation</h4><p>You add a button to turn it off. You press the button. Nothing happens. You press it harder, as if force will travel through the plastic into the microcontroller.</p><p>You add delay(10) to “debounce” it. Now everything is even more laggy. You Google “why my Arduino button doesn’t work” at 2 AM.</p><p>Welcome. You’ve hit the delay() wall. Every Arduino developer hits it. The good ones climb over it.</p><p><a href="https://numbpilled.gumroad.com/l/dualband-riccv-manual">ESP32-C5 FROM ZERO: The Dual-Band RISC-V Field Manual</a></p><h3>The Upgrade: Meet millis() — Time Without the Tantrum</h3><p>The grown-up way to handle time is to not stop time.</p><p>Instead of saying “wait here,” you say “remember what time it is, and check back later.”</p><p>That’s millis(). It returns the number of milliseconds since your Arduino woke up. It never stops. It never blocks. It just quietly counts, like a responsible adult.</p><p>Here’s the mindset shift:</p><p>delay() says: “I will wait.”</p><p>millis() says: “Has enough time passed yet?”</p><p>This is non-blocking timing. And it looks like this:</p><pre>unsigned long previousMillis = 0;<br>const long interval = 1000;<br>bool ledState = false;<br><br>void loop() {<br>  unsigned long currentMillis = millis();<br><br>  if (currentMillis - previousMillis &gt;= interval) {<br>    previousMillis = currentMillis;<br>    ledState = !ledState;<br>    digitalWrite(LED_PIN, ledState);<br>  }<br><br>  // Your button, your sensor, your serial, your dignity<br>  // can all live RIGHT HERE and still work.<br>  checkButton();<br>  readSensors();<br>}</pre><p>That subtraction currentMillis — previousMillis is not an accident. It handles the millis() overflow after ∼49 days correctly. If you use currentMillis &gt;= previousMillis + interval, you will have a very confusing bug in 49 days. Don’t be that person.</p><p>Now your loop() is free. It’s spinning fast, hundreds of thousands of times per second, checking: Is it time? Is it time? Is it time? No? Cool, I’ll go do other useful things.</p><p>This is what we call cooperative multitasking. You aren’t using an RTOS. You’re just not being rude to the rest of your code.</p><h3>Pattern 1: The Two LEDs That Finally Got Divorced</h3><p>This is the classic interview question. Two LEDs, independent blink rates. With delay(), impossible. With millis(), trivial.</p><pre>unsigned long prev1 = 0, prev2 = 0;<br>const long int1 = 300;<br>const long int2 = 800;<br><br>void loop() {<br>  unsigned long now = millis();<br><br>  if (now - prev1 &gt;= int1) {<br>    prev1 = now;<br>    digitalWrite(LED1, !digitalRead(LED1));<br>  }<br>  <br>  if (now - prev2 &gt;= int2) {<br>    prev2 = now;<br>    digitalWrite(LED2, !digitalRead(LED2));<br>  }<br>}</pre><p>Two timers. No drama. They don’t even know each other exists. This is healthy boundaries in code form.</p><h3>Pattern 2: The Button That Actually Works</h3><p>Your button problem was never the button. It was you abandoning it for a full second every loop.</p><p>Here’s a non-blocking button with debouncing that doesn’t suck:</p><pre>const int BUTTON_PIN = 2;<br>int lastButtonState = HIGH;<br>int buttonState = HIGH;<br>unsigned long lastDebounceTime = 0;<br>const long debounceDelay = 50;<br><br>void loop() {<br>  int reading = digitalRead(BUTTON_PIN);<br><br>  if (reading != lastButtonState) {<br>    lastDebounceTime = millis();<br>  }<br><br>  if ((millis() - lastDebounceTime) &gt; debounceDelay) {<br>    if (reading != buttonState) {<br>      buttonState = reading;<br>      if (buttonState == LOW) {<br>        // Actually does something, every single time<br>        Serial.println(&quot;I was pressed! Finally! Acknowledged!&quot;);<br>      }<br>    }<br>  }<br>  lastButtonState = reading;<br>}</pre><p>No delay(50) to “fix” bouncing. We timestamp the chaos and ignore it until it settles. Elegant. Responsive.</p><h3>Pattern 3: You Need a State Machine (Yes, You)</h3><p>Once you have more than two timings, a pile of previousMillis variables turns into spaghetti. Time to level up.</p><p>Stop thinking in linear steps. Start thinking in states.</p><p>Your project isn’t a script. It’s a mood ring.</p><p>Example: You want a traffic light that can be interrupted by a pedestrian button.</p><p>Linear thinking: GREEN delay RED delay GREEN… panic when button is pressed.</p><p>State machine thinking:</p><pre>enum State { GREEN, YELLOW, RED, WALK };<br>State currentState = GREEN;<br>unsigned long stateStartTime = 0;<br><br>void loop() {<br>  unsigned long now = millis();<br>  <br>  switch (currentState) {<br>    case GREEN:<br>      if (now - stateStartTime &gt;= 5000) {<br>        currentState = YELLOW;<br>        stateStartTime = now;<br>        // switch lights<br>      }<br>      if (pedestrianRequested()) {<br>        currentState = YELLOW; // early exit<br>        stateStartTime = now;<br>      }<br>      break;<br>      <br>    case YELLOW:<br>      if (now - stateStartTime &gt;= 2000) {<br>        currentState = RED;<br>        stateStartTime = now;<br>      }<br>      break;<br>    // ... you get it. Clean. Testable. Extendable.<br>  }<br>}</pre><p>Each state knows what it should do, how long it should last, and where to go next. Your loop() stays fast. Your logic stays readable. You can add 20 more states without breaking everything.</p><p>This is how real embedded systems work. From your microwave to a Mars rover. Not a single delay() in sight.</p><p>But What About…?</p><p>“But delay() is easier to read!”</p><p>For a 5-line example, yes. For a 500-line project, it’s unreadable because it doesn’t work. Readability that hides broken behavior isn’t readability. It’s a lie.</p><p>“But I need precise timing!”</p><p>Then delay() is even worse. delay(1000) is not exactly 1000ms. It’s 1000ms plus however long all the other code in your loop took. Your timing drifts. With millis(), your interval is fixed.</p><p>If you need really precise timing — like microsecond-level, bit-banging, driving NeoPixels — you shouldn’t be using either. You should be using hardware timers, micros(), or interrupts. But that’s a Medium article for when you’re ready to lose your weekends.</p><p>“But what about delayMicroseconds()?”</p><p>Same sin, smaller scale. Still blocking.</p><p><a href="https://numbpilled.gumroad.com/l/deaddrops">Signals Bundle - Dead Drops &amp; Mesh Ops</a></p><h3>The Official Cheat Sheet to Replace Every delay()</h3><p>Let’s make this actionable. Pin this to your wall.</p><ol><li><strong>If you’re doing this:</strong></li></ol><p>delay(1000) to blink an LED</p><p><strong>Do this instead:</strong></p><p>millis() interval check. Remember the time, don’t waste it.</p><p>if (millis() — previous &gt;= 1000) { toggle(); }</p><p><strong>2. If you’re doing this:</strong></p><p>delay(50) to debounce a button</p><p>Do this instead:</p><p>Timestamp debounce. Let the chaos settle.</p><p>Save lastBounce = millis() when it changes, only act after 50ms of calm.</p><p><strong>3. If you’re doing this:</strong></p><p>delay() to wait for a sensor to be ready</p><p>Do this instead:</p><p>Poll, don’t block. Check isReady() in your loop every cycle. Go do other work in the meantime.</p><p><strong>4. If you’re doing this:</strong></p><p>Three delay()s in a row to make a sequence (move servo -&gt; wait -&gt; beep -&gt; wait)</p><p><strong>Do this instead:</strong></p><p>State machine. Your project has moods.</p><p>enum { MOVE, BEEP, IDLE } + switch case + millis() for each state.</p><p><strong>5. If you’re doing this:</strong></p><p>delay() to make a buzzer beep for a bit</p><p><strong>Do this instead:</strong></p><p>tone(pin, freq, duration) and leave, or tone() + millis() to turn it off yourself. Don’t stand there holding the buzzer.</p><p><a href="https://numbpilled.gumroad.com/l/hardware-signal-fieldpack">Hardware Signals Field Pack - ESP32 &amp; Sub-GHz RF Research Lab</a></p><h3>Final Thought: Your Arduino Is Better Than You Think</h3><p>The Arduino Uno is a 16MHz computer with 2KB of RAM. It’s not powerful. But it’s infinitely more capable than delay() lets it be.</p><p>When you stop using delay(), you stop treating your microcontroller like a kitchen timer and start treating it like what it is: a real-time processor that can juggle.</p><p>Your code gets faster. More responsive. More professional. You can finally add that second, third, tenth feature without everything collapsing.</p><p>So open your last project. Search for delay. Look at each one. Ask it: “Do you really need to freeze the entire universe, or are you just lazy?”</p><p>99% of the time, it’s lazy.</p><p>Kill it. Replace it with millis(). Give your Arduino its life back.</p><p>Your button will thank you.</p><p><em>Got a horror story about delay() ruining your project? I know you do. Drop it in the comments. Let’s heal together.</em></p><p><em>If this saved you a debugging night, give it a clap. Or 50. I don’t use delay() to count.</em></p><h3>Thank you for being a part of the community</h3><p><em>Before you go:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9QTaaaxboQP_gKSLedW_w.png" /></figure><p>👉 Be sure to <strong>clap</strong> and <strong>follow</strong> the writer ️👏<strong>️️</strong></p><p>👉 Follow us: <a href="https://medium.com/codetodeploy"><strong>Medium</strong></a></p><p><strong>Disclosure:</strong> This post includes affiliate and partnership links.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4eb0f1b77448" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codetodeploy/stop-using-delay-your-arduino-deserves-better-4eb0f1b77448">Stop Using delay(). Your Arduino Deserves Better.</a> was originally published in <a href="https://medium.com/codetodeploy">CodeToDeploy</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[9 Angular API Integration Mistakes That Break Real Applications]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/9-angular-api-integration-mistakes-that-break-real-applications-710e1bcb4734?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/1672/1*B6wa-eHuQ53BGAL9KHU4rw.png" width="1672"></a></p><p class="medium-feed-snippet">Your API call works perfectly in development. Then the backend returns an unexpected response, the network fails, or a request takes too&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/9-angular-api-integration-mistakes-that-break-real-applications-710e1bcb4734?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/9-angular-api-integration-mistakes-that-break-real-applications-710e1bcb4734?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/710e1bcb4734</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[api-integration]]></category>
            <dc:creator><![CDATA[Coding Mentor]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:31:41 GMT</pubDate>
            <atom:updated>2026-11-17T14:31:39.947Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[10 Claude Code Tricks That Made Me Rethink How I Program]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/10-claude-code-tricks-that-made-me-rethink-how-i-program-2ed0ca323c6b?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/2600/0*KbbjgJ6bE04bPXiv" width="3995"></a></p><p class="medium-feed-snippet">I used to think AI coding tools were mainly about generating code faster. Then I started noticing how much of programming happens outside&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/10-claude-code-tricks-that-made-me-rethink-how-i-program-2ed0ca323c6b?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/10-claude-code-tricks-that-made-me-rethink-how-i-program-2ed0ca323c6b?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/2ed0ca323c6b</guid>
            <category><![CDATA[climate-change]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[learn with her]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:30:35 GMT</pubDate>
            <atom:updated>2026-11-17T14:30:34.541Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I Learned More Python From Breaking Code Than Watching Tutorials]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/i-learned-more-python-from-breaking-code-than-watching-tutorials-33ad48d7da1a?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/2600/0*2P4RpLAH3G0se7gA" width="5507"></a></p><p class="medium-feed-snippet">For a long time, I thought learning Python meant watching tutorials, taking notes, and trying to remember what the instructor had just&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/i-learned-more-python-from-breaking-code-than-watching-tutorials-33ad48d7da1a?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/i-learned-more-python-from-breaking-code-than-watching-tutorials-33ad48d7da1a?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/33ad48d7da1a</guid>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[python-programming]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Maria Ali]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:29:25 GMT</pubDate>
            <atom:updated>2026-11-17T14:29:24.563Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The More You Explain Yourself, the More You Lose Yourself]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/codetodeploy/the-more-you-explain-yourself-the-more-you-lose-yourself-36c71203e512?source=rss----c8b549b355f4---4"><img src="https://cdn-images-1.medium.com/max/735/1*Zf4CwA6IFXXNXqoULdkUfQ.jpeg" width="735"></a></p><p class="medium-feed-snippet">Sometimes, the need to be understood becomes the reason we stop listening to ourselves.</p><p class="medium-feed-link"><a href="https://medium.com/codetodeploy/the-more-you-explain-yourself-the-more-you-lose-yourself-36c71203e512?source=rss----c8b549b355f4---4">Continue reading on CodeToDeploy »</a></p></div>]]></description>
            <link>https://medium.com/codetodeploy/the-more-you-explain-yourself-the-more-you-lose-yourself-36c71203e512?source=rss----c8b549b355f4---4</link>
            <guid isPermaLink="false">https://medium.com/p/36c71203e512</guid>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[human-nature]]></category>
            <dc:creator><![CDATA[Fozia Saleem]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:28:16 GMT</pubDate>
            <atom:updated>2026-11-17T14:28:15.078Z</atom:updated>
        </item>
    </channel>
</rss>